On 2/8/2020 10:48 pm, Jean-Baptiste Holcroft wrote:
Can't we simply forbid "zh_CN" and "zh_TW" on
fedora website or making
it an alias so either code leads to the same content?
Currently website team has already done similar work. The translation
can be shown in the webpage without problem.
I am sorry that I didn't make you fully understand why do I want that move.
I'm not a fan of using old code "not to confuse new
Because in fact, most of the world is using the new one an we - the
Linux community - are using the old one because of glibc not handling it
or not seeing the value of this. If my memory is good, I think it was
related to the number of characters a language code can have.
In fact, I don't really care about the use of the new or the old code name.
When I talked about the "confuse new contributors" in my previous
messages, it is because the projects are not in the same language team
like other languages' are. Most of the projects are in zh_CN/TW, except
that website project is in zh_Hans/zh_Hant. This is my concern, and this
*may* cause the possiblity of unnecessary new translation of the website
project in zh_CN language code team, this is the *confusion* I want to
talk about. Furthermore, the projects should be in the same language
team, like they are in other language teams, like they were in old
Whoever in your language community will always have to face this
challenge until Linux ecosystem fix this bug (the bug is: chineese based
languages uses obsolete codes).
As a user, I've never met such challenge or haven't noticed it. As a
translator, all I hope is what I said above.
I don't have deep understanding of the bug you mentioned, but we'd
better discuss about it in another post if you like.
I suggest to consume energy to make the i18n and glibc people to act
So you want the projects in Chinese languages keep their current
one in new language code, and rest of them in old language code.
When upstream fix the bug someday, you will finally move all of the
projects to the new language code(zh_Hans/Hant). Am I right?
Last time I tried I failed, but you may find the words I couldn't
advocate the matter.
Do you mean i18n and glibc won't fix it?
I'm sure other languages with less visibility will benefit this.
Sorry, I don't understand this.
Fedora Project Contributor