[Bug 323232] UTF-8 arrows mangled (fwd)

[Reinout van Schouwen]

Dear gettext maintainers,

Could you please take a look at the bug report below and confirm if it 
is indeed a gettext bug? Thanks very much.


---------- Forwarded message ----------
Date: Thu,  8 Dec 2005 08:42:40 -0500 (EST)
From: "deskbar-applet (bugzilla.gnome.org)" <address@hidden>
To: address@hidden
Subject: [Bug 323232] UTF-8 arrows mangled

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=323232
 deskbar-applet | general | Ver: CVS HEAD





------- Additional Comments From Tommi Vainikainen  2005-12-08 13:42 -------
Mentioned manual/tutorial is about translators PoV (ie. msgstrs), not msgids
gathered from the source files.

A line "[encoding: UTF-8]" in POTFILES.in forces UTF-8 encoding for the source
files, and should be added, but does not fix the problem.

However Python sources have encoding in the files, and xgettext (which intltool
internally uses) mentions about command line switch
"""
Input file interpretation:
       --from-code=NAME  encoding of input files (except for Python, Tcl, Glade)
       By default the input files are assumed to be in ASCII.
"""

In gettext 14.5 gettext-tools/src/x-python.c says at line 213
 /* We assume the program source is in ISO-8859-1 (for consistency with
     Python's \ooo and \xnn syntax inside strings), but we produce a POT
     file in UTF-8 encoding.  */

This is plainly wrong, and the bug is in xgettext program with Python source
code.  Can someone reassign this bug from here to gettext maintainers?

------- You are receiving this mail because: -------
You reported the bug.