On Sep 13 09:45, Eric Blake wrote: > On 09/09/2011 08:59 AM, Corinna Vinschen wrote: > >On Sep 9 13:33, Andy Koppe wrote: > >>The 'C.UTF-8' default locale is not a bug, it was a deliberate design > >>decision. > > > >Exactly. And it has been discussed a lot on the cygwin-apps mailing > >list. > > > >And above all, there *is* an official way for the user to align the > >Cygwin locale with the Windows locale, see the -s and -u options > >of the locale(1) command: > > > > http://cygwin.com/cygwin-ug-net/using-utils.html#locale > > On 09/09/2011 09:09 AM, Corinna Vinschen wrote: > >> OK, then the following four facilities are needed in Cygwin. > >> > >> 1) We need the name of the locale which is in effect when the user has > >> not specified environment variables. > > > > In Fedora, for instance, the fallback is what is set as system default > > in /etc/sysconfig/i18n. > > > > In Cygwin the fallback is the system default set in > /etc/profile.d/lang.sh > > or /etc/profile.d/lang.csh. > > > > Why should libintl use anything else on Cygwin, but not on Linux? > > > > Given this, I think the bug is in cygwin for having base files > /etc/profile.d/lang.{sh,csh} which hardcode LANG to C.UTF-8 instead > of using locale -s -u to default LANG to the preferred Windows > settings.
Bug? Didn't we choose C.UTF-8 after a long discussion? Are the points raised in this discussion invalid or outdated now? Why? I don't object against using `locale -sU' in lang.sh/lang.csh, but we should not do this without a discussion of the pros and cons. > Libintl should NOT be second-guessing an explicit setting > of LANG, ACK. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
