And why not:?
2c) If the declared encoding was ISO-8859-2, replace that
character with the character that you get by casting the code point
into a byte and decoding it as Windows-1250.
Am I missing something?
Chris
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Henri Sivonen
Sent: Tuesday, June 05, 2007 9:19 AM
To: WHATWG List
Subject: Re: [whatwg] ISO-8859-* and the C1 control range
On May 29, 2007, at 13:13, Henri Sivonen wrote:
Based on the behavior of Minefield and Opera 9.20, the following
seems to be the least Charmod violating and least quirky approach
that could possibly work:
1) Decode the byte stream using a decoder for whatever encoding was
declared, even ISO-8859-1 or ISO-8859-11, according to ftp://
ftp.unicode.org/Public/MAPPINGS/.
2) If a character in the decoded character stream is in the C1 code
point range, this is a document conformance violation.
2a) If the declared encoding was ISO-8859-1, replace that
character with the character that you get by casting the code point
into a byte and decoding it as Windows-1252.
2b) If the declared encoding was ISO-8859-11, replace that
character with the character that you get by casting the code point
into a byte and decoding it as Windows-874.
