Handle nasty charset polymorphism

Question

Handle nasty charset polymorphism

Yomguithereal opened this issue 9 years ago · comments

Guillaume Plique commented 9 years ago

@boogheta: do you know this way of indicating the charset?

en_US.iso885915

Benjamin Ooghe-Tabanou · Answer 1 · Tue Apr 14 2015 02:02:16 GMT+0800 (China Standard Time)

mmm it's a mix of locale and encoding I guess?

Guillaume Plique · Answer 2 · Tue Apr 14 2015 02:05:01 GMT+0800 (China Standard Time)

I guess so, but I didn't even know this was standard.

Eric Bréchemier · Answer 3 · Mon Jul 13 2015 16:14:08 GMT+0800 (China Standard Time)

This format is described in POSIX Base Definitions, 8.2 Internationalization Variables:

If the locale value has the form:

language[_territory][.codeset]

it refers to an implementation-provided locale, where settings of language, territory, and codeset are implementation-defined.

LC_COLLATE, LC_CTYPE, LC_MESSAGES, LC_MONETARY, LC_NUMERIC, and LC_TIME are defined to accept an additional field @ modifier, which allows the user to select a specific instance of localization data within a single category (for example, for selecting the dictionary as opposed to the character ordering of data). The syntax for these environment variables is thus defined as:

[language[_territory][.codeset][@modifier]]

Guillaume Plique · Answer 4 · Mon Jul 13 2015 20:51:45 GMT+0800 (China Standard Time)

Thanks @eric-brechemier. I guess we'll have to fix the parser's implementation to make this work.