CYGWIN=codepage? Or LC_CTYPE=foo?
Kazuhiro Fujieda
fujieda@jaist.ac.jp
Sun Apr 6 22:16:00 GMT 2008
>>> On Sun, 06 Apr 2008 21:26:18 +0200
>>> Corinna Vinschen said:
> I checked the return values from GetLocaleInfo. Apparently the strings
> returned by GetLocaleInfo(LOCALE_SISO639LANGNAME) and
> GetLocaleInfo(LOCALE_SISO3166LANGNAME) match what you would expect.
I can use these strings to check locale names in setlocale
without any additional table.
> I don't know if gsw-FR is correct though. That's apparently an ISO639-2
> code. But it looks like there is no ISO639 code covering that. What
> would POSIX do?
de_FR would be used instead of it.
> Oh, btw., from what I read in SUSv3, the "C" locale is actually just
> the old name for what's today called "POSIX" locale. They are both
> equivalent, but POSIX requires that a POSIX conformant system
> understands both. I guess that's no big problem.
I forgot it. Yes, this is a trivial problem.
____
| AIST Kazuhiro Fujieda <fujieda@jaist.ac.jp>
| HOKURIKU School of Information Science
o_/ 1990 Japan Advanced Institute of Science and Technology
More information about the Cygwin-developers
mailing list