Re: [bug-gettext] xgettext --from-code does not work

[Didier Spaier]

On 30/03/2014 11:55, address@hidden wrote:
> Dears,
>
> the message "please specify the source encoding through --from-code" is totally
> frustrating, because the valid codepage is specified and it does not work.
>
> ================================================================
> xgettext -k_ "--from-code=WINDOWS-1250" -o ref.po ../sources.cc/*.cc ./dump.c
> ../sources.cc/igettext.cc:155: warning: Empty msgid.  It is reserved by GNU 
> gettext:
>                                          gettext("") returns the header entry 
> with
>                                          meta information, not the empty string.
> xgettext: Non-ASCII string at ../sources.cc/wp2latex.cc:438.
>            Please specify the source encoding through --from-code.
> make: *** [ref.po] Error 1
>
> ================================================================
> bash-4.2# xgettext -V
> xgettext (GNU gettext-tools) 0.18.2
> Copyright (C) 1995-1998, 2000-2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://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.
>
> ================================================================
> bash-4.2# iconv -l
> The following list contain all the coded character sets known.  This does
> not necessarily mean that all combinations of these names can be used for
> the FROM and TO command line parameters.  One coded character set can be
> listed with several different names (aliases).
>
>    437, 500, 500V1, 850, 851, 852, 855, 856, 857, 860, 861, 862, 863, 864, 865,
>    866, 866NAV, 869, 874, 904, 1026, 1046, 1047, 8859_1, 8859_2, 8859_3, 8859_4,
>    8859_5, 8859_6, 8859_7, 8859_8, 8859_9, 10646-1:1993, 10646-1:1993/UCS4,
>    ANSI_X3.4-1968, ANSI_X3.4-1986, ANSI_X3.4, ANSI_X3.110-1983, ANSI_X3.110,
>    ARABIC, ARABIC7, ARMSCII-8, ASCII, ASMO-708, ASMO_449, BALTIC, BIG-5,
>    BIG-FIVE, BIG5-HKSCS, BIG5, BIG5HKSCS, BIGFIVE, BRF, BS_4730, CA, CN-BIG5,
>    CN-GB, CN, CP-AR, CP-GR, CP-HU, CP037, CP038, CP273, CP274, CP275, CP278,
>    CP280, CP281, CP282, CP284, CP285, CP290, CP297, CP367, CP420, CP423, CP424,
>    CP437, CP500, CP737, CP770, CP771, CP772, CP773, CP774, CP775, CP803, CP813,
>
>    .................
>
>    UTF-16BE, UTF-16LE, UTF-32, UTF-32BE, UTF-32LE, UTF7, UTF8, UTF16, UTF16BE,
>    UTF16LE, UTF32, UTF32BE, UTF32LE, VISCII, WCHAR_T, WIN-SAMI-2, WINBALTRIM,
>    WINDOWS-31J, WINDOWS-874, WINDOWS-936, WINDOWS-1250, WINDOWS-1251,
>    WINDOWS-1252, WINDOWS-1253, WINDOWS-1254, WINDOWS-1255, WINDOWS-1256,
>    WINDOWS-1257, WINDOWS-1258, WINSAMI2, WS2, YU
> bash-4.2#

I never used gettext for perl scripts, but in
http://www.gnu.org/software/gettext/manual/gettext.html#Perl I see:
Another caveat of the current version is its rudimentary support for non-ASCII 
characters in identifiers. You may encounter serious problems if you use 
identifiers with characters outside the range of 'A'-'Z', 'a'-'z', '0'-'9' and 
the underscore '_'.

This is only a blind guess, of course.

Didier

PS for Jaroslav: sorry for the duplicate answer, I first dit hit the bad button.