Wait, Sitelen Pona gets used?
(Of course it does, or it might, but I wouldn't know. Nor do you seem
to consider that scripts you aren't familiar with get used.) Tengwar and
Cirth are popular, and see
https://www.unicode.org/L2/L2016/16329-piqad-returns.pdf for examples of
Klingon pIqaD usage.
~mark
On 5/29/26 5:41 PM, Gabriel Tellez via Unicode wrote:
Are there any conlang scripts, other than Sitelen Pona, that *do* get
used?
On Thu, May 28, 2026 at 3:16 PM Michael De Roover
<[email protected]> 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 HELO/
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 ignore 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 <http://nixmagic.com>]
[michael@[email protected] <http://de.roover.eu.org>]
[Web] [https://michael.de.roover.eu.org]
[Forge] [https://git.nixmagic.com]
[Weather] [Antwerpen] [20:00] [24.5°C]
--- --- --- ---
[0] [2026-05-28 20:50 CEST]
[~] [[email protected]]
[$] [/usr/bin/sign-mail] [>_]
--- --- --- ---
