[bug #20923] xgettext generates .pot files with charset set to CHARSET

[Arsen Arsenović]

Follow-up Comment #3, bug #20923 (project gettext):

as of gettext-0.22 this is preventing rebuilding .pot files in
binutils-gdb.git.  for some reason, however, this doesn't seem to apply to
0.21.1:

/tmp/foo$ xgettext --version
xgettext (GNU gettext-tools) 0.22
Copyright (C) 1995-2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Ulrich Drepper.
/tmp/foo$ echo 'void f () { gettext ("foobar"); }' > a.c
/tmp/foo$ echo 'void f () { gettext ("barfoo"); }' > b.c
/tmp/foo$ /usr/bin/xgettext --default-domain=bfd --directory=. --add-comments
--keyword=_ --msgid-bugs-address=https://sourceware.org/bugzilla/
--files-from=/dev/stdin <<< a.c
/tmp/foo$ /usr/bin/xgettext --join-existing --default-domain=bfd --directory=.
--add-comments --keyword=_
--msgid-bugs-address=https://sourceware.org/bugzilla/ --files-from=/dev/stdin
<<< b.c
bfd.po: warning: Charset "CHARSET" is not a portable encoding name.
                 Message conversion to user's charset might not work.
/usr/bin/xgettext: present charset "CHARSET" is not a portable encoding name
/tmp/foo 1 $ sudo emerge =gettext-0.21.1
...
/tmp/foo$ rm *
/tmp/foo$ echo 'void f () { gettext ("foobar"); }' > a.c
/tmp/foo$ echo 'void f () { gettext ("barfoo"); }' > b.c
/tmp/foo$ xgettext --default-domain=foo --directory=. --add-comments
--keyword=_ --files-from=/dev/stdin <<< a.c
/tmp/foo$ xgettext --join-existing --default-domain=foo --directory=.
--add-comments --keyword=_ --f
iles-from=/dev/stdin <<< b.c
foo.po: warning: Charset "CHARSET" is not a portable encoding name.
                 Message conversion to user's charset might not work.
/tmp/foo$ 

it seems sensible to record (and recover) the running systems' charset when
generating a pot file


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?20923>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/