Re: windows 1250 - another update to review :)

[Ned Freed <ned.freed@mrochek.com>]

> I assume these comments are all just out-of-sync with my previous suggestion?

> > How's this correction?

> > >   The graphic (non-control) characters of Windows-1250 have a supported
> > >   set of characters similar to the ISO-8859-2 charset. There are
> > >   differences in the range from 80 to FF (hex).

I think it is useful to say that every graphics character in iso-8859-2
is also in windows-1250. That's why I suggested the wording I did.

				Ned

> - Shawn

> -----Original Message-----
> From: Ned Freed [mailto:ned.freed@mrochek.com]
> Sent: Wednesday 13 June 2007 13:38
> To: Erik van der Poel
> Cc: Shawn Steele; ietf-charsets@mail.apps.ietf.org
> Subject: Re: ietf-charsets@mail.apps.ietf.org windows 1250 - another update to review :)

> > Perhaps this is a misunderstanding due to the word "superset" (my
> > mistake). What I meant was an upward compatible character encoding, if
> > you disregard the control characters. Clearly, iso-8859-2 and
> > windows-1250 are different in the range 0xA0 to 0xFF:

> Well, I guess it's a question of whether you're talking about a superset of the
> underlying set of characters (CCS) or a superset of the mapping of the
> characters to integers (CES). So perhaps it is best to simply avoid the word
> superset entirely and say "all of the characters in iso-8859-2 are present in
> windows-1250 but some are in different positions" or something along these
> lines.

> 				Ned