Re: Establishing a team for Taiwanese

Apologies for the late answer.

El dilluns, 4 de maig del 2026, a les 17:04:49 (Hora d=E2=80=99estiu d=E2=
=80=99Europa central), Kisaragi Hiu va escriure:
> > 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.
> Without fixing ISO 639-3 I also have no hope for fixing glibc and CLDR.
> There is a pending  ISO 639-3 Change Request, 2021-044 to assign `ftg` to
> Taigi / Taiwanese and make this happen, but it has been pending for 5 yea=
rs
> and appears stalled. (It is the oldest pending Change Request.)

That's unfortunate :(

> Would I be able to establish this language team without waiting indefinit=
ely
> for ISO 639-3, CLDR, or glibc if I concede with the name "Min Nan Chinese
> (Taiwan)" (exactly consistent with the current language code `nan_TW`) and
> a QLocale of `QLocale::MinNanChinese` (consistent with
> `QLocale::LiteraryChinese`) for now?

Yes, if you do not mind=20
nan_TW =09
Min Nan Chinese
as name we can create the teams without problems from my side.

Let me copy the instructions for new teams

The first thing we ask people that want to create/revive a team is to=20
translate kcoreaddons, kio and kxmlgui as close to 100% as possible and sen=
d=20
them to me in private (no need to bother the rest of the people in the mail=
ing=20
list with those files).

You can find the templates at=20

https://invent.kde.org/localization/l10n-templates/-/tree/master/trunk6/mes=
sages/kcoreaddons
https://invent.kde.org/localization/l10n-templates/-/tree/master/trunk6/mes=
sages/kxmlgui=20
https://invent.kde.org/localization/l10n-templates/-/tree/master/trunk6/mes=
sages/kio

So your first task to become "new team coordinator"=20
would be to get those files as close to 100% as possible and send=20
them to me.

Do you need help with how the translation workflow works?=20

>=20
> This would mean:
> - To accomodate the two writing systems it would actually have to be call=
ed
> "Min Nan Chinese (Taiwan)" and "Min Nan Chinese (Taiwan, Latin)". This is
> not ideal but acceptable if the alternative is being stalled indefinitely.
> - And, if `ftg` is approved and adopted, work would be needed to migrate
> nan_TW and nan_TW@latin over to ftg and ftg@latin. But this would be the
> case anyways even if I got my original wishes granted.

Moving files should be trivial.

Best Regards,
  Albert

Apologies again for the late answer

> Right now, my best case for fixing standards to recognize Taiwanese or Ta=
igi
> as the name is that ISO 639-3 decides to adopt `ftg`, which would finally
> make "Taigi" standard and kick off work to support the new code and name =
in
> glibc, CLDR, Qt, and other places. The fastest this could happen is in
> July, 3 months after the previous Change Request results were posted. But
> this appears to be taking an indeterminate amount of time, and I didn't
> want to keep waiting for indeterminate amounts of time before translation
> work can even begin, which is why I started this translation work now
> without waiting for ISO 639-3.
>=20
> (Also, sorry about my two previous emails being HTML-only, which I only
> noticed after checking the archives. Hopefully this email, now sent from
> Thunderbird and not the Gmail client, will be appropriately plain text.)
>=20
> Best regards,
> Kisaragi Hiu