-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 11/9/2008 12:26 PM: > >> I finally noticed it today when I nearly converted it back to Latin-1 >> (cygwin UTF- 8 support is less than stellar). > > Oh. Is that a problem for you?
No, I don't have any technical problem using UTF-8. I had already converted THANKS to UTF-8 in an earlier patch, using iconv on cygwin to do the conversion. And cygwin emacs does a decent job with UTF-8, provided that it is given the hint that a file is encoded. But so far, cygwin doesn't have any UTF-8 capable console, so viewing the patch with 'git log' displays two bytes in Latin-1 rather than one character from a Unicode font; but not a show-stopper from using UTF-8 on platforms that are better set up for i18n. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkXWYoACgkQ84KuGfSFAYCuMACgtnhWA6x0+ymlWBfQjjSnkKsw hskAoNHkHm5iT+Dj5qxbUdByWLRdNLND =b08p -----END PGP SIGNATURE-----
