After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 757896 - Unnecessary zh_hant/hans selection in Site Language
Unnecessary zh_hant/hans selection in Site Language
Status: RESOLVED FIXED
Product: damned-lies
Classification: Infrastructure
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: damned-lies Maintainer(s)
damned-lies Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-11-10 15:51 UTC by Mingye Wang
Modified: 2018-03-26 10:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mingye Wang 2015-11-10 15:51:34 UTC
I assume this bug applies to all Damned-Lies releases, so I am reporting this bug seen on l10n.gnome.org as general.

In the user page, one can see two 简体中文 and two 繁体中文 selections. A quick dig on the webpage source shows those 4 selections:

        <option value="zh-hant">繁體中文</option>
        <option value="zh-tw">繁體中文</option>
        <option value="zh-cn">简体中文</option>
        <option value="zh-hans">简体中文</option>

However, it's almost clear that nobody is translating the zh_Hans/Hant locale for damned lies, and those two selections only confuses the users (and give a barely translated website). I think it's time to get those removed.

If we take a reasonable approximation that zh_Hant is almost zh_TW, and zh_Hans is almost zh_CN, symlinks can be used for compatibility for users who chose zh_Hans/hant at first. This is basically acceptable since the two zh_Hant locales are quite close to each other in wording, and few people use zh_SG (the other locale using zh_Hans script) compared to the enormous number of zh_CN users.
Comment 1 Mingye Wang 2016-01-15 16:13:33 UTC
See https://bugzilla.gnome.org/show_bug.cgi?id=757867#c2 for some extended info on the script-vs-locale issue.
Comment 2 Claude Paroz 2018-03-26 10:36:13 UTC
Apparently, this is fixed due to usage of recent version of the Django framework.