[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] What's wrong with skwan-utf8?
- To: idn@ops.ietf.org
- Subject: Re: [idn] What's wrong with skwan-utf8?
- From: "J. William Semich" <bill@mail.nic.nu>
- Date: Wed, 03 Jan 2001 12:55:24 -0500
- Delivery-date: Wed, 03 Jan 2001 09:57:34 -0800
- Envelope-to: idn-data@psg.com
Try "Plan 9." <grin>
See:
http://www.cs.bell-labs.com/magic/man2html/6/utf
"The Plan 9 character set and representation are based on the Unicode
Standard and on the ISO multibyte UTF-8 encoding (Universal Character Set
Transformation Format, 8 bits wide). The Unicode Standard represents its
characters in 16 bits; UTF-8 represents such values in an 8-bit byte
stream. Throughout this manual, UTF-8 is shortened to UTF."
Available at http://www.cs.bell-labs.com/plan9dist/
Bill
At 05:31 PM 1/3/01 +0000, Brian W. Spolarich wrote:
>On Wed, 3 Jan 2001, J. William Semich wrote:
>
>| Yes. Windows 2000 Professional - Multililanguage version.
>
> I'm using Win2K right now. :-) The Character Map tool (and the
>underlying support behind it) is one of the nicest things that Microsoft
>has done. Unfortunately lots of applications can't deal with the data, so
>you get lots of '???' sequences when you pass data around between
>applications. This is actually a good example of the kind of boundary
>problem that IDN poses.
>
> Windows-based OSes have very different semantics from POSIX-like and
>other Unix-y systems.
>
> My implied question really was really about the POSIX/*nix stuff.
>
> -bws
>
>