Re: Establishing a team for Taiwanese

Kisaragi Hiu <[email protected]> Tue, 05 May 2026 00:04:49 +0900
Newsgroups gmane.comp.kde.devel.internationalization-and-documentation
Message-ID <[email protected]>
> Before contacting the Qt people, I recommend you fix the glibc and cldr, =
because they are going to use those sources as input for their decision=2E

Without fixing ISO 639-3 I also have no hope for fixing glibc and CLDR=2E =
There is a pending  ISO 639-3 Change Request, 2021-044 to assign `ftg` to T=
aigi / Taiwanese and make this happen, but it has been pending for 5 years =
and appears stalled=2E (It is the oldest pending Change Request=2E)

Would I be able to establish this language team without waiting indefinite=
ly for ISO 639-3, CLDR, or glibc if I concede with the name "Min Nan Chines=
e (Taiwan)" (exactly consistent with the current language code `nan_TW`) an=
d a QLocale of `QLocale::MinNanChinese` (consistent with `QLocale::Literary=
Chinese`) for now?

This would mean:
- To accomodate the two writing systems it would actually have to be calle=
d "Min Nan Chinese (Taiwan)" and "Min Nan Chinese (Taiwan, Latin)"=2E This =
is not ideal but acceptable if the alternative is being stalled indefinitel=
y=2E
- And, if `ftg` is approved and adopted, work would be needed to migrate n=
an_TW and nan_TW@latin over to ftg and ftg@latin=2E But this would be the c=
ase anyways even if I got my original wishes granted=2E

Right now, my best case for fixing standards to recognize Taiwanese or Tai=
gi as the name is that ISO 639-3 decides to adopt `ftg`, which would finall=
y make "Taigi" standard and kick off work to support the new code and name =
in glibc, CLDR, Qt, and other places=2E The fastest this could happen is in=
 July, 3 months after the previous Change Request results were posted=2E Bu=
t this appears to be taking an indeterminate amount of time, and I didn't w=
ant to keep waiting for indeterminate amounts of time before translation wo=
rk can even begin, which is why I started this translation work now without=
 waiting for ISO 639-3=2E

(Also, sorry about my two previous emails being HTML-only, which I only no=
ticed after checking the archives=2E Hopefully this email, now sent from Th=
underbird and not the Gmail client, will be appropriately plain text=2E)

Best regards,
Kisaragi Hiu