[bug-gettext] Please do not set charset=GB2312 when using msginit --locale=zh_CN

[Boyuan Yang]

Dear gettext developers,

I am the team leader of TranslationProject (TP) Chinese (Simplified)
translation team [1]. When working to convert POT files to PO files
using msginit in order to initialise translation, I noticed that it
will set the output PO file to be encoded using GB2312 [2].

Example:

1. $  wget https://translationproject.org/POT-files/direvent-5.1.pot
2. $ msginit -l zh_CN -i direvent-5.1.pot -o a.po
The new message catalog should contain your email address, so that users can
give you feedback about the translations, and so that maintainers can contact
you in case of unexpected technical problems.

Which is your email address?

Please choose the number, or enter your email address.
address@hidden
Retrieving http://translationproject.org/team/index.html... done.
A translation team for your language (zh) does not exist yet.
If you want to create a new translation team for zh or zh_CN, please visit
  http://www.iro.umontreal.ca/contrib/po/HTML/teams.html
  http://www.iro.umontreal.ca/contrib/po/HTML/leaders.html
  http://www.iro.umontreal.ca/contrib/po/HTML/index.html

Created a.po.
3. $ file a.po
a.po: GNU gettext message catalogue, ISO-8859 text

The "ISO-8859" above was an incorrect recognition of GB2312-encoded texts.

If I do not explicitly specify "--locale=zh_CN", the generated file
will be encoded in UTF-8.

In fact, non-UTF-8 environment for zh_CN system has been deprecated
for decades on Linux systems and almost no one is currently using
them. Windows nowadays is also providing perfect support for UTF-8
texts. As a result, I consider such behaviour a bug.

Could you please update the source code and do not explicitly set
encoding for output PO file to be GB2312?

Thank you very much and looking forward to your reply.

--
Regards,
Boyuan Yang

[1] https://translationproject.org/team/zh_CN.html
[2] https://en.wikipedia.org/wiki/GB_2312