RE: More about SCSU (was: Re: A UTF-8 based News Service)
> > SCSU doesn't look very nice for me. The idea is OK but it's just > > too complicated. Various proposals of encodings differences or xors > > between consecutive characters are IMHO technically better: much > > simpler to implement and work as well. > > These differential schemes seem to be the way IDN > (internationalized domain > names) are headed. They are intended for the limited scope > of domain names > that have already passed through nameprep, which performs > normalization and > further limits the range of allowable characters. I'm not > sure how well the > ACEs would perform with arbitrary Unicode text. I suppose > only testing would > answer that question. Also don't forget they're likely to add some code point reordering. Do we want that too in an alternate scheme? Then is it really that much simpler than SCSU? (Probably; tables for code point reordering are not complex to build. But they may take some effort to optimize, so my guess is the implementation effort may be roughly the same.) YA
Re: More about SCSU (was: Re: A UTF-8 based News Service)
From: <[EMAIL PROTECTED]> > None as far as I know, which sort of destroys the whole plan. It would sure > be nice if MSIE and Navigator started "quietly" supporting SCSU, in the same > way that they "quietly" (to the average user) began supporting UTF-8. If you want the code in Navigator, write it up for Mozilla and properly submit it, at which point Mozilla will "quietly" start supporting SCSU, and Navigator will follow suit in a couple releases. -- David Starner - [EMAIL PROTECTED]
Re: More about SCSU (was: Re: A UTF-8 based News Service)
> Unfortunately, you don't hear much about SCSU, and in particular the Unicode > Consortium doesn't really seem to promote it much (although they may be > trying to avoid the "too many UTF's" syndrome). Probably that's one point. But also, SCSU is something that's a little more complicated to use, and needs to be pretty well negotiated between sender and receiver. It's much less suitable for general-purpose interchange. Rick
Re: More about SCSU (was: Re: A UTF-8 based News Service)
In a message dated 2001-07-13 4:07:35 Pacific Daylight Time, [EMAIL PROTECTED] writes: > SCSU doesn't look very nice for me. The idea is OK but it's just > too complicated. Various proposals of encodings differences or xors > between consecutive characters are IMHO technically better: much > simpler to implement and work as well. These differential schemes seem to be the way IDN (internationalized domain names) are headed. They are intended for the limited scope of domain names that have already passed through nameprep, which performs normalization and further limits the range of allowable characters. I'm not sure how well the ACEs would perform with arbitrary Unicode text. I suppose only testing would answer that question. -Doug Ewell Fullerton, California
Re: More about SCSU (was: Re: A UTF-8 based News Service)
Fri, 13 Jul 2001 03:01:10 EDT, [EMAIL PROTECTED] <[EMAIL PROTECTED]> pisze:
> Unfortunately, you don't hear much about SCSU, and in particular
> the Unicode Consortium doesn't really seem to promote it much
> (although they may be trying to avoid the "too many UTF's" syndrome).
SCSU doesn't look very nice for me. The idea is OK but it's just
too complicated. Various proposals of encodings differences or xors
between consecutive characters are IMHO technically better: much
simpler to implement and work as well.
--
__("< Marcin Kowalczyk * [EMAIL PROTECTED] http://qrczak.ids.net.pl/
\__/
^^ SYGNATURA ZASTĘPCZA
QRCZAK
Re: More about SCSU (was: Re: A UTF-8 based News Service)
In a message dated 2001-07-12 22:55:09 Pacific Daylight Time, [EMAIL PROTECTED] writes: >> SCSU is also registered as an IANA charset, although you are >> unlikely to find >> raw SCSU text on the Internet, due to its use of control >> characters (bytes below 0x20). > > And what browser supports SCSU, and what it that browser's reach in term of > population? Because that's usually what matters to people that publish on > the Internet. None as far as I know, which sort of destroys the whole plan. It would sure be nice if MSIE and Navigator started "quietly" supporting SCSU, in the same way that they "quietly" (to the average user) began supporting UTF-8. Unfortunately, you don't hear much about SCSU, and in particular the Unicode Consortium doesn't really seem to promote it much (although they may be trying to avoid the "too many UTF's" syndrome). -Doug Ewell Fullerton, California
RE: More about SCSU (was: Re: A UTF-8 based News Service)
> SCSU is also registered as an IANA charset, although you are > unlikely to find > raw SCSU text on the Internet, due to its use of control > characters (bytes > below 0x20). And what browser supports SCSU, and what it that browser's reach in term of population? Because that's usually what matters to people that publish on the Internet. YA
