GNU gettext 0.22 broke non-Unicode msgids

[Robert Clausecker]

Greetings,

I am maintaining a project that uses msgids in ISO-8859-1 encoding.
To build the message catalogues for the project, I previously used

    ${SETENV} LC_ALL=de_DE.ISO8859-1 msgfmt -o ${WRKDIR}/SCHILY_utils.mo 
${WRKSRC}/SCHILY_utils.po

However, since the update to gettext 0.22, this command fails to
produce a correct message catalogue.  As the msgids are transcoded
to Unicode, gettext() no longer finds messages corresponding to our
msgids.

As a workaround, I have now applied the new --no-convert option, but
this is not a good solution as your tool broke compatibility.

Please restore the previous behaviour and do not transliterate msgids.
It seems like it's fine if you transliterate the messages the msgids
refer to, but the msgids themselves should stay as is so they match
the strings used in the source code of the program that uses the
message catalogues.

Yours,
Robert Clausecker

-- 
()  ascii ribbon campaign - for an 8-bit clean world 
/\  - against html email  - against proprietary attachments