Re: CYGWIN=codepage? Or LC_CTYPE=foo?

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Apr  7 07:15, Kazuhiro Fujieda wrote:
> >>> 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.

After a night's sleep... am I right that GetLocaleInfo is just half the
job?  Unfortunately, there's no function to get the LCID from a ISO639
Language/ISO3166 Country pair.  The matching functions only exist since
Vista, AFAICS.  But a corresponding table isn't that big.  I don't see a
problem to include it in Cygwin.

> > 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, interesting.  This combination doesn't seem to exist in Windows.

> > 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.

Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat