Re: POSIX msgfmt: effect of LC_CTYPE on PO file parsing

[shwaresyst]

This is for files that do not specify a separate codeset at all, and for interpreting a file that does specify one before it gets to the line with the codeset directive, is my understanding, so needs to be there (for now, maybe not in future). It maybe should be more explicit codeset changes start with the next directive, not applies to a rewind/reread of the whole file.

On Wed, May 11, 2022 at 7:30 PM, Bruno Haible via austin-group-l at The Open Group

<austin-group-l@opengroup.org> wrote:

https://posix.rhansen.org/p/gettext_draft

Line 960

"Do we need to say this isn't used for message strings, only for parsing

the .po file?"

The .po file format has a mechanism for specifying the codeset of the

PO file. See line 1009. Therefore LC_CTYPE is *not used* for the

interpretation of the input .po file, only for producing diagnostics

(in combination with the LC_MESSAGES category).