Skip to content

fix nan-tw not listed in SUPPORTED_LOCALES#37721

Open
Yoxem wants to merge 4 commits intomastodon:mainfrom
Yoxem:main
Open

fix nan-tw not listed in SUPPORTED_LOCALES#37721
Yoxem wants to merge 4 commits intomastodon:mainfrom
Yoxem:main

Conversation

@Yoxem
Copy link
Contributor

@Yoxem Yoxem commented Feb 3, 2026

Even though #34923 is merged, the nan-tw (Taigi/Taiwanese Hokkien) is still not able to be chosen to be the interface language. I think that it's attributed to the lacking of ISO 639-3 (in the case, nan) is not in the ISO_639_3 list due to the lacking translation for the language (or language set). However, the ISO 639 code (Min Nan) is not translated, and because of the language separatism of Taigi and Taiwanese Nationalism, many Taigi-speaking people are opposed to using "Min Nan" (which means Southern Fujian Province of China) as the language they use, so I suggest to create another hash (like the dict data-structure in Python) named NAN_TW_CODE, and append it to variable SUPPORTED_LOCALES and variable REGIONAL_LOCALE_NAMES .

(cc @gunchleoc )

@renchap renchap requested a review from ClearlyClaire February 9, 2026 18:14
@renchap renchap added the i18n Internationalization and localization label Feb 9, 2026
@ClearlyClaire
Copy link
Contributor

Hi! Thank you for your contribution!

Your change would not actually add it to the available interface languages, I opened #37822 for that.

Your change is still needed to add it to the supported posting languages, and seems overall ok, although I would avoid adding a hash just for one language. It seems to me this could fit into a ISO_639_3_REGIONAL though.

@ClearlyClaire
Copy link
Contributor

That being said, I'm no expert in language codes, and if you think nan-TW should be changed to something else, now would probably be the time, before it gets usable in Mastodon.

@Yoxem
Copy link
Contributor Author

Yoxem commented Feb 12, 2026

I think that the language code for Taiwanese Hokkien/Taigi is nan-TW currently, I think that once #37822 is merged, and the interface shows correctly, this #33721 PR can be closed directly. If not, I suggest that this PR can be marged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

i18n Internationalization and localization

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants