Corinna Vinschen wrote:
> On Jun 22 16:48, Thomas Wolff wrote:
> > Since the latest locale-related changes, the default codepage after
> > starting cygwin _without_ explicit setting (of a locale variable)
> > seems to have changed from CP1252 ("Windows ANSI") to ISO 8859-1 ("Latin
> > 1").
> > Was this change on purpose?
>
> There was no such change at all. The default codepage is still the
> default ANSI codepage on your system. The internal conversion from
> Windows functions to the POSIX multibyte environment and vice versa
> uses UTF-8, though, so that all existing filenames have a valid
> representation even when using characters not available in your
> current codepage.
If I do the following:
* Open cmd console window.
* Go into cygwin 1.7 directory.
* Call cygwin.bat.
* In cygwin, "cat" a file with all 8 bit characters from U+20 to U+FF.
Then there are no printable characters in the range U+80...U+9F
(the difference between ISO 8859-1 and Windows "Western" CP1252).
If I set LC_CTYPE=en_US.CP1252 before invoking cygwin.bat, I get
full CP1252.
The script calls bash --login. If I start only bash (without --login
and without LC_CTYPE), I get CP1252 as well, which appears somehow
inconsistent to me.
[I'll attach screen shots and the test file to a copy of this mail only
sent to Corinna, as I seem to remember attachments are not desired on
this mailing list.]
Thomas
--
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
