This is the mail archive of the
mailing list for the Cygwin project.
RE: OT: RE: filesystem encoding
- From: "Gary R. Van Sickle" <g dot r dot vansickle at worldnet dot att dot net>
- To: "'Colin JN Breame'" <colinb at chameleonnet dot co dot uk>, <cygwin at cygwin dot com>
- Date: Fri, 10 Sep 2004 22:36:16 -0500
- Subject: RE: OT: RE: filesystem encoding
> Gary R. Van Sickle wrote:
> >Welcome to the 21st century, where computers can't even
> >represent written text.
> Isn't this something unicode was meant to solve?
Yes, and if implemented properly, it mostly does.
> or does
> unicode still need a codepage to map to glyphs?
No, not a system-wide one anyway. IIRC (and I'm no Unicode expert), the
verbage in the specs talk about "codepages" (or something like that) a lot,
but it's a few bits in each character that specify something similar to the
ASCII/ISO-style codepages, the end result being that each individual Unicode
character is unambiguously represented.
Gary R. Van Sickle
 Gross oversimplification alert. Some of the Asian languages have
characters who's precise glyph depends on the previous character, and I
think that introduces some context sensitivity. Ah well, we have to leave
*something* for the 31st century folks to fix. :-(.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html