Re: Seeming hostility to conlang scripts?

--000000000000a089e30652fbb887
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Are there any conlang scripts, other than Sitelen Pona, that *do* get used?

On Thu, May 28, 2026 at 3:16=E2=80=AFPM Michael De Roover <unicode@nixmagic=
.com>
wrote:

> On Thursday, 28 May 2026 20:35:45 Central European Summer Time Gabriel
> Tellez
> via Unicode wrote:
> > Sure but Teyvat Script is, as you seem to have said, is 1 to 1 with
> latin.
> > So it has no need to be encoded in the first place. These other scripts
> > (pIqaD, Tengwar, Cirth, Sarati) don't have that.
>
> Admittedly, I am not familiar with these franchises or their scripts.
> Uncultured as I am however, the legality and usage issues do still stand.
>
> I do think it is worth considering them in context of Esperanto, which
> despite
> being a conlang did manage to secure itself a critical base of primary
> speakers, and Unicode support. These languages could become like that too=
,
> but
> their communities will have to put in the work first to prove usefulness.
>
> From my developer standpoint, I don't mind certain ignorable parts of a
> spec
> existing, provided that I don't need to add those to my implementations.
> By
> that I mean that I don't mind inclusion of *some* aspects that I may
> consider
> to be cruft for my own implementation, provided that ignoring them is
> allowed
> by the spec.
>
> The other day I was working on an SMTP receiver, which will implement HEL=
O/
> EHLO, MAIL, RCPT, DATA, QUIT, and RSET commands. There do exist other
> commands
> in the SMTP specs, which I will not implement and only gracefully refuse.
> But
> that graceful refusal does take decision on my end, as to how much I need
> to
> implement of those, and what I consider to be sufficiently cruft to ignor=
e
> while
> remaining in spec.
>
> That decision-making on an individual implementer's part is my concern
> here. I
> believe that this is primarily a given standard's job. Any deviation
> thereof,
> even when it remains in spec, introduces uncertainty. And while I do
> acknowledge each of these fandoms, including my own, I would not be
> willing to
> implement any of them unless required by my employer (which will
> contractually
> take the legal burden). While the fandoms of each of these franchises are
> enormous, their conlangs' usefulness does not currently extend beyond
> those
> fandoms. And I would definitely not want to be sued by their rights
> holders
> over it, no matter how boneheaded the fandoms may be about it (and
> Genshin's
> is no different). Nor do I want Unicode to be exposed to that either.
>
> --
> [Met vriendelijke groet] [Best regards]
> [Michael De Roover]
> ---      ---      ---      ---
> [Mail] [*@nixmagic.com] [michael@[email protected]]
> [Web] [https://michael.de.roover.eu.org]
> [Forge] [https://git.nixmagic.com]
> [Weather] [Antwerpen] [20:00] [24.5=C2=B0C]
> ---      ---      ---      ---
> [0] [2026-05-28 20:50 CEST]
> [~] [[email protected]]
> [$] [/usr/bin/sign-mail] [>_]
> ---      ---      ---      ---
>
>
>
>

--000000000000a089e30652fbb887
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Are there any conlang scripts, other than Sitelen Pona, th=
at *do* get used?</div><br><div class=3D"gmail_quote gmail_quote_container"=
><div dir=3D"ltr" class=3D"gmail_attr">On Thu, May 28, 2026 at 3:16=E2=80=
=AFPM Michael De Roover &lt;<a href=3D"mailto:[email protected]">unicode=
@nixmagic.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">On Thursday, 28 May 2026 20:35:45 Central European Summer Time=
 Gabriel Tellez <br>
via Unicode wrote:<br>
&gt; Sure but Teyvat Script is, as you seem to have said, is 1 to 1 with la=
tin.<br>
&gt; So it has no need to be encoded in the first place. These other script=
s<br>
&gt; (pIqaD, Tengwar, Cirth, Sarati) don&#39;t have that.<br>
<br>
Admittedly, I am not familiar with these franchises or their scripts. <br>
Uncultured as I am however, the legality and usage issues do still stand.<b=
r>
<br>
I do think it is worth considering them in context of Esperanto, which desp=
ite <br>
being a conlang did manage to secure itself a critical base of primary <br>
speakers, and Unicode support. These languages could become like that too, =
but <br>
their communities will have to put in the work first to prove usefulness.<b=
r>
<br>
From my developer standpoint, I don&#39;t mind certain ignorable parts of a=
 spec <br>
existing, provided that I don&#39;t need to add those to my implementations=
. By <br>
that I mean that I don&#39;t mind inclusion of *some* aspects that I may co=
nsider <br>
to be cruft for my own implementation, provided that ignoring them is allow=
ed <br>
by the spec.<br>
<br>
The other day I was working on an SMTP receiver, which will implement HELO/=
<br>
EHLO, MAIL, RCPT, DATA, QUIT, and RSET commands. There do exist other comma=
nds <br>
in the SMTP specs, which I will not implement and only gracefully refuse. B=
ut <br>
that graceful refusal does take decision on my end, as to how much I need t=
o <br>
implement of those, and what I consider to be sufficiently cruft to ignore =
while <br>
remaining in spec.<br>
<br>
That decision-making on an individual implementer&#39;s part is my concern =
here. I <br>
believe that this is primarily a given standard&#39;s job. Any deviation th=
ereof, <br>
even when it remains in spec, introduces uncertainty. And while I do <br>
acknowledge each of these fandoms, including my own, I would not be willing=
 to <br>
implement any of them unless required by my employer (which will contractua=
lly <br>
take the legal burden). While the fandoms of each of these franchises are <=
br>
enormous, their conlangs&#39; usefulness does not currently extend beyond t=
hose <br>
fandoms. And I would definitely not want to be sued by their rights holders=
 <br>
over it, no matter how boneheaded the fandoms may be about it (and Genshin&=
#39;s <br>
is no different). Nor do I want Unicode to be exposed to that either.<br>
<br>
-- <br>
[Met vriendelijke groet] [Best regards]<br>
[Michael De Roover]<br>
---=C2=A0 =C2=A0 =C2=A0 ---=C2=A0 =C2=A0 =C2=A0 ---=C2=A0 =C2=A0 =C2=A0 ---=
=C2=A0 =C2=A0 =C2=A0 <br>
[Mail] [*@<a href=3D"http://nixmagic.com" rel=3D"noreferrer" target=3D"_bla=
nk">nixmagic.com</a>] [michael@at@<a href=3D"http://de.roover.eu.org" rel=
=3D"noreferrer" target=3D"_blank">de.roover.eu.org</a>]<br>
[Web] [<a href=3D"https://michael.de.roover.eu.org" rel=3D"noreferrer" targ=
et=3D"_blank">https://michael.de.roover.eu.org</a>]<br>
[Forge] [<a href=3D"https://git.nixmagic.com" rel=3D"noreferrer" target=3D"=
_blank">https://git.nixmagic.com</a>]<br>
[Weather] [Antwerpen] [20:00] [24.5=C2=B0C]<br>
---=C2=A0 =C2=A0 =C2=A0 ---=C2=A0 =C2=A0 =C2=A0 ---=C2=A0 =C2=A0 =C2=A0 ---=
=C2=A0 =C2=A0 =C2=A0 <br>
[0] [2026-05-28 20:50 CEST]<br>
[~] [[email protected]]<br>
[$] [/usr/bin/sign-mail] [&gt;_] <br>
---=C2=A0 =C2=A0 =C2=A0 ---=C2=A0 =C2=A0 =C2=A0 ---=C2=A0 =C2=A0 =C2=A0 ---=
=C2=A0 =C2=A0 =C2=A0 <br>
<br>
<br>
<br>
</blockquote></div>

--000000000000a089e30652fbb887--