This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 19939 - JIS X 0212 missing from the ISO-2022-JP encoder?
Summary: JIS X 0212 missing from the ISO-2022-JP encoder?
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Encoding (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+encodingspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-11 22:08 UTC by pub-w3
Modified: 2012-11-16 12:50 UTC (History)
2 users (show)

See Also:

Attachments

Description pub-w3 2012-11-11 22:08:46 UTC 
There is a note saying that current EUC-JP encoders do not encode JIS X 0212.

Is that the case for ISO-2022-JP encoders as well?  If so, a note to that effect should probably be added to the specification.  Otherwise, the algorithm needs to be modified.
Comment 1 Masatoshi Kimura 2012-11-12 15:36:16 UTC 
ISO-2022-JP doesn't contain JIS X 0212 from the start. (But ISO-2022-JP-1 and ISO-2022-JP-2 do.)
Comment 2 pub-w3 2012-11-12 20:18:33 UTC 
Indeed, I was using the term ‘ISO-2022-JP’ improperly to refer to a series of related encodings including JIS (the predecessor of ISO-2022-JP), ISO-2022-JP, ISO-2022-JP-1, ISO-2022-JP-2, ISO-2022-JP-3 and ISO-2022-JP-2004, as well as hybrids and variants.

The issue I was trying to raise is that the encoder does not mirror the decoder, and that this asymmetry is not mentioned.
Comment 3 pub-w3 2012-11-12 23:31:30 UTC 
As you were probably alluding to, the various versions are not necessarily handled identically.

Safari and Opera both distinguish between at least two variants:

If the MIME charset is ISO-2022-JP-2, JIS X 0212 is decoded and encoded.
For ISO-2022-JP, on the other hand, JIS X 0212 characters are encoded as deciamal character references, and Safari does not decode JIS X 0212 data either.
Comment 4 Masatoshi Kimura 2012-11-13 12:21:01 UTC 
I don't see the point of differentiating ISO-2022-JP variants. We already treat some ISO encodings as just aliases of Windows encodings.

Regarding the asymmetry, I agree to add some explanations.
Comment 5 pub-w3 2012-11-14 23:05:00 UTC 
It looks like I misinterpreted your comment twice.  Sorry about that.  I think we are in agreement.

Given that IE has never supported JIS X 0212 (not sure about recent versions), it probably makes sense to use it only for the decoder.  Only a note acknowledging the asymmetry is missing.