Console codepage setting via chcp?

Andy Koppe
Sat Sep 26 19:59:00 GMT 2009

2009/9/26 Corinna Vinschen:
> Do you propose to change __utf8_mbtowc/__utf8_wctomb to allow UCS-2
> encoding as well?

No. Gotta draw the line somewhere.

> The only other alternative would be to revert all the surrogate pair
> handling changes and to allow only UCS-2 again, thus giving up to
> support Unicode values >= U+10000.

Even more of a no then.

(A modified pair of UTF-8 conversion functions for filenames&co might
be another alternative, but no, I do not believe this is worth the
effort, certainly not at this point.)

>> I vote for the proposal here, with added fence-sitting in the form of
>> a CYGWIN option called 'filename_charset' (or some such) taking
>> precedence over LC_ALL/LC_CTYPE/LANG.
>> With that, setting 'CYGWIN=fncset:UTF-8' would yield
> No, please.  I was glad getting rid of CYGWIN=codepage:[ansi|oem].
> The simple workaround is not to set LC_ALL/LC_CTYPE/LANG at all,
> or to set it to "xx_XX.UTF-8".

Fair point.


More information about the Cygwin-developers mailing list