Your message dated Mon, 23 Aug 2010 14:27:09 +0200 (CEST)
with message-id <[email protected]>
has caused the report #594059,
regarding gettext: xgettext should not complain about UTF-8
to be marked as having been forwarded to the upstream software
author(s) [email protected]
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
594059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594059
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Hello.
I received this report from the Debian bug system.
Thanks.
---------- Forwarded message ----------
From: W. Martin Borgert <[email protected]>
To: [email protected]
Date: Mon, 23 Aug 2010 13:56:57 +0200
Subject: Bug#594059: gettext: xgettext should not complain about UTF-8
Package: gettext
Version: 0.18.1.1-1
Severity: minor
Using this "extract" from /usr/share/xml/iso-codes/iso_3166.xml
# -*- coding: utf-8 -*-
name=_("Åland Islands")
name=_("Côte d'Ivoire")
and the command line
$ xgettext --language=Python --omit-header --output=/dev/null utf8.py
leads to the following warnings:
utf8.py:2: warning: The following msgid contains non-ASCII characters.
This will cause problems to translators who use a character
encoding
different from yours. Consider using a pure ASCII msgid
instead.
Åland Islands
utf8.py:2: invalid multibyte sequence
utf8.py:2: invalid multibyte sequence
utf8.py:2: invalid multibyte sequence
utf8.py:2: invalid multibyte sequence
utf8.py:3: warning: The following msgid contains non-ASCII characters.
This will cause problems to translators who use a character
encoding
different from yours. Consider using a pure ASCII msgid
instead.
Côte d'Ivoire
utf8.py:3: invalid multibyte sequence
utf8.py:3: invalid multibyte sequence
utf8.py:3: invalid multibyte sequence
utf8.py:3: invalid multibyte sequence
Because UTF-8 is the default and recommended encoding in
Debian (and, as far as I know, in PO files), it would be
nice to accept it without warning.
Btw. there is a similar bug report at
http://code.djangoproject.com/ticket/4734
--- End Message ---
