Bug 237786 - xgettext doesn't handle non-ASCII source strings correctly
Summary: xgettext doesn't handle non-ASCII source strings correctly
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gettext
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-04-25 13:41 UTC by Nils Philippsen
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-07-19 05:22:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Nils Philippsen 2007-04-25 13:41:30 UTC
Description of problem:

When getting messages from one of my UTF-8 python files, xgettext apparently
doesn't use UTF-8, but some ISO encoding when dealing with a copyright sign:

This is the msgid as put into system-config-services.pot by xgettext:

msgid ""
"System Services Configuration Tool VERSION\n"
" Copyright © 2002-2006 Red Hat, Inc.\n"
[...]

This is how it should be:

msgid ""
"System Services Configuration Tool VERSION\n"
" Copyright © 2002-2006 Red Hat, Inc.\n"
[...]


Version-Release number of selected component (if applicable):
gettext-0.14.6-4.fc6

How reproducible:
Easily

Steps to Reproduce:
1. Check out system-config-services from elvis
2. cd po/
3. make update-po

or:

1. create small python file (marked with "coding: utf-8") with a translatable
copyright sign
2. run "xgettext --default-domain=system-config-services --add-comments
--from-code=utf-8 --keyword=_ --keyword=N_ ..." on that file
  
Actual results:
See above ex.1

Expected results:
See above ex.2

Additional info:
I just made a test build of 0.16.1 from Rawhide and with its xgettext the UTF-8
copyright sign was left intact.

Comment 1 Nils Philippsen 2007-04-25 14:14:14 UTC
See bug #232809 for background.

Comment 2 Jens Petersen 2007-04-30 08:09:39 UTC
Hmm I see: guess it is necessary to track down in which version of gettext
this was fixed.

Comment 3 Jens Petersen 2007-07-19 05:22:17 UTC
I doubt there will be a chance to fix this before fc7 moves to EOL,
unless someone comes with a patch.  So closing for now.

Comment 4 Jens Petersen 2007-07-19 05:23:23 UTC
(Just for the record, F7 already ships with the newer 0.16.1.)


Note You need to log in before you can comment on or make changes to this bug.