Asmus Freytag <firstname.lastname@example.org> wrote:
> Unlike Plane 14, SCSU is not necessarily intended for unfettered
> public interchange as if it was YAUTF (yet another utf). Yes, it can
> be nice and small, but it assumes that the recipient have a conformant
> decoder and can reliably detect when to invoke it.
Isn't this true for UTF-8, UTF-16, and any other encoding form or TES
of Unicode? Receivers of data in these formats also must be able to
detect them and interpret them. How does SCSU differ in this regard?
The SCSU technical report defines clearly what a conformant decoder must
be able to do, and suggests a header sequence which would make auto-
detection a relatively simple and accurate job (not many files start
with the bytes 0E FE FF).
Writing a conformant SCSU decoder turns out to be a rather straight-
forward job, not that much more work than writing a *good* UTF-8 decoder
(with checking for illegal and irregular sequences).
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:05 EDT