On Oct 4 08:45, Charles Wilson wrote:
> On 10/4/2011 8:28 AM, Corinna Vinschen wrote:
> > On Sep 13 09:45, Eric Blake wrote:
> >> 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.
>
> IIRC, that discussion occurred before the 'locale' application (was
> written|got smarter). Sure, I think C.UTF-8 should be the "default
> default" but the arguments in favor of respecting the users' own Windows
> i18n settings make sense.
Does it? Even if I'm running a german OS, I absolutely hate to see
german diagnostic output from gcc, and I absolutely hate certain
programs using non-ASCII chars in output. (In)famous examples are
Unicode quoting chars rather than ' or ", or using the Unicode hyphen
character rather than -. But that's just me.
> However, one issue is that windows basically will always have SOME
> setting -- even if just "English". Which would cause locale to report
> 'en_US' or something. So you'd never actually SEE the "default default"
> of C.UTF-8 take effect. Also, would locale append '.UTF-8' (or would
> lang.{sh,csh} do so?).
That's what the -U option is for. See `locale --help'.
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
