Ben Collins-Sussman wrote:
>For a couple of weeks now, every time I compile my /trunk working copy,
>it always ends with these warnings:
>
>
>sed '/^"Content-Type: text\/plain; charset=UTF-8\\n"$/d'
>subversion/po/de.po > subversion/po/de.spo
>/usr/local/bin/msgfmt -o subversion/po/de.mo subversion/po/de.spo
>/usr/local/bin/msgfmt: subversion/po/de.spo: warning: Charset missing in
>header. Message
>conversion to user's charset will not work.
>sed '/^"Content-Type: text\/plain; charset=UTF-8\\n"$/d'
>subversion/po/nb.po > subversion/po/nb.spo
>/usr/local/bin/msgfmt -o subversion/po/nb.mo subversion/po/nb.spo
>/usr/local/bin/msgfmt: subversion/po/nb.spo: warning: Charset missing in
>header. Message
>conversion to user's charset will not work.
>rm subversion/po/de.spo subversion/po/nb.spo
>
>
>I'm running RH9, using GNU gettext 0.13. What's all this about "missing
>charsets" in the header? (FWIW, the default terminal locale on RH9 is
>en_US.UTF-8, if that's relevant.)
>
>
You're a bit behind the times, arean't you? :-)
These warnings are expected, and are the result of our stripping the
Content-Type header from the .po files. And we strip that to make sure
some gettext doesn't try to convert the messages to some local encoding,
because we need them in UTF-8. We can't use bind_textdomain_codeset,
because that's GNU-gettext-specific. This was all discussed on the list
a while ago.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 24 16:34:20 2004