-----BEGIN PGP SIGNED MESSAGE-----
Doug Ewell wrote:
> Martin Kochanski <unicode at cardbox dot net> wrote:
> > To look at it another way, virtually the only action that the Unicode
> > Consortium needs to take to define UNRENDERED CHARACTER is to promise
> > never to define a character at that code point.
> I think this is exactly what they have done by creating the
> "noncharacters" from U+FDD0 through U+FDEF. These code points are
> guaranteed never to be assigned to real characters.
See conformance clause C5 (as modified by UAX #27 / Unicode 3.1):
# C5 A process shall not interpret a noncharacter code point as an
# abstract character.
# - The code points may be used internally, such as for sentinel values
# or delimiters, but should not be exchanged publicly.
So using those code points to represent an unrenderable character in
data that is exchanged publicly, is not conformant.
> My recommendation: Use the noncharacters. That's what they're there
No, they're for internal use.
David Hopwood <firstname.lastname@example.org>
Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5 0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2.1.2 : Thu Aug 01 2002 - 17:46:34 EDT