Update of bug #50357 (project gettext): Status: None => Not a Bug Assigned to: None => haible Open/Closed: Open => Closed
_______________________________________________________ Follow-up Comment #1: Thanks for the report. > xgettext should support, for Python code, the same set of aliases as Python does. I disagree. The set of recognised encoding names is defined by standards, in particular by IANA. The standards define one name for this encoding, namely "UTF-8". No alias. Why it is not a good idea to invent new aliases for new encodings: because then one program after the other gets requests for supporting this aliases. And then the next program, for interoperability reasons, and so on. So the effect of such requests is to create interoperability problems for several years. Btw, the web page you cited http://www.python.org/peps/pep-0263.html contains 10 mentions of "UTF-8" and 0 mentions of "UTF8". Finally, your argument "should support ... the same set of aliases as Python does" talks about an implementation of the Python language. But there are several Python implementations (see https://en.wikipedia.org/wiki/List_of_Python_software#Python_implementations ), and I bet they don't support the exact same set of encodings on all platforms. That's why you need standards. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?50357> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/