This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: cyg1.7 - DOS character remapping: change request.
- From: Eric Blake <ebb9 at byu dot net>
- To: cygwin at cygwin dot com
- Date: Mon, 23 Nov 2009 20:34:11 -0700
- Subject: Re: cyg1.7 - DOS character remapping: change request.
- References: <4B0B21E0.3050909@tlinx.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Linda Walsh on 11/23/2009 4:59 PM:
> Instead of using random characters out of the 'random free area' --
> which could display as anything if you aren't in cygwin, depending
> on what charset you have loaded, why not use 'dedicated' unicode
> characters that map to the signs for those characters? They aren't
> exactly equivalent, as they include some built-in display spacing,
> BUT, they would display a colon as a colon, "*" as a asterisk, etc.
But then, how would you distinguish between the valid UTF-16 replacement
used to represent an invalid character, and a valid UTF-16 character
representing itself? I'm sorry, but the value of a 1-to-1 round trip
mapping outweighs the convenience of displaying a glyph that looks the
same but causes ambiguous round trip conversions.
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@byu.net
-----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/
iEYEARECAAYFAksLVDIACgkQ84KuGfSFAYCAMACgqj76FkhwHf6jLa2lG7ohZind
iB8AoLWCl5VNJXmQ6MNOybP0LCXqZ4qT
=icUw
-----END PGP SIGNATURE-----
--
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