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 118960 - gnome-pim msgid includes non-ASCII character breaking gettext
gnome-pim msgid includes non-ASCII character breaking gettext
Status: RESOLVED FIXED
Product: gnome-pim
Classification: Deprecated
Component: general
1.9x.y
Other All
: Normal major
: 2.0.x
Assigned To: gnome-pim Maintainers
gnome-pim Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-08-03 00:09 UTC by Christian Rose
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Rose 2003-08-03 00:09:07 UTC
The file gncal/calendar-week.c contains a non-ascii character that
causes many warnings from xgettext when I update the sv.po (which is in
UTF-8) with "intltool-update sv":

xgettext: 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.
                   %s ‒ %s
xgettext: invalid multibyte sequence
xgettext: invalid multibyte sequence
xgettext: invalid multibyte sequence
xgettext: invalid multibyte sequence
xgettext: invalid multibyte sequence
xgettext: invalid multibyte sequence

Also, the character will not be displayed in the msgid in the po file,
it will simply be an extra space. Thus, this message cannot be translated
correctly as it is.
Comment 1 Christian Rose 2003-08-03 00:10:18 UTC
msgids always have to be proper ASCII. For further reference, see
http://developer.gnome.org/doc/tutorials/gnome-i18n/developer.html#use-ascii.