GNU gettext - Bugs: bug #20923, xgettext generates .pot files with...
You are not allowed to post comments on this tracker with your current authentication level.
bug #20923: xgettext generates .pot files with charset set to CHARSET
Submitter: | None | ||
Submitted: | Tue 28 Aug 2007 05:42:36 PM UTC | ||
Category: | Programmer tools | Severity: | 3 - Normal |
Item Group: | None | Status: | Confirmed |
Privacy: | Public | Assigned to: | haible |
Open/Closed: | Open |
Spam posted by arsen | |
Spam posted by anonymous | |
Wed 29 Aug 2007 10:10:59 PM UTC, comment #1: |
Bruno Haible <haible>![]() ![]() |
Tue 28 Aug 2007 05:42:36 PM UTC, original submission:
This makes it hard to process the .pot file with the other gettext tools:
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Indeed there is a problem:
$ cat > x.c
gettext ("hallo world");
$ xgettext -o foo.pot x.c
$ msgen foo.pot > en.po
$ msgcat en.po
en.po: warning: Charset "CHARSET" is not a portable encoding name.
Message conversion to user's charset might not work.
msgcat: present charset "CHARSET" is not a portable encoding name
I eee it more as a bug in 'msgen'.