🚀 go-pugleaf

Submitted-by: david@mks.com (David Rowley)

In article <16p6bmINNs1l@ftp.UU.NET> mskuhn@immd4.informatik.uni-erlangen.de (Markus Kuhn) writes:
>But how may UCS-4 files be identified? Do they always begin with 0000feff
>and are converted if they begin with fffe0000 or other permutations?
>Does ISO 10646 say anything about this or will any future POSIX extension do?

Being relatively new to ISO 10646, I believe the intent is to
use the UCS Transformation Format (Annex F of 10646) as the
standard external representation format (such as file contents,
etc.).  This multibyte encoding supports both the UCS2 and UCS4
codeplanes.

Note that UTF and 8-bit Latin 1 (ISO 8859-1) are identical for
characters 0x00 to 0x9f.  Codepoints above 0x9f are used to
introduce the multibyte sequences.

One problem, though, is that the UTF description in ISO 10646 is
informative, rather than normative.  With this being the case
can implementors safely point to UTF as a standard encoding?

-- 
David Rowley
Mortice Kern Systems Inc.
35 King Street North, Waterloo, ON, Canada N2J 2W9
519/884-2251, FAX 519/884-8861, david@mks.com


Volume-Number: Volume 29, Number 3