<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>19939</bug_id>
          
          <creation_ts>2012-11-11 22:08:46 +0000</creation_ts>
          <short_desc>JIS X 0212 missing from the ISO-2022-JP encoder?</short_desc>
          <delta_ts>2012-11-16 12:50:17 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WHATWG</product>
          <component>Encoding</component>
          <version>unspecified</version>
          <rep_platform>PC</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>Unsorted</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>pub-w3</reporter>
          <assigned_to name="Anne">annevk</assigned_to>
          <cc>mike</cc>
    
    <cc>VYV03354</cc>
          
          <qa_contact>sideshowbarker+encodingspec</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>78207</commentid>
    <comment_count>0</comment_count>
    <who name="">pub-w3</who>
    <bug_when>2012-11-11 22:08:46 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>78223</commentid>
    <comment_count>1</comment_count>
    <who name="Masatoshi Kimura">VYV03354</who>
    <bug_when>2012-11-12 15:36:16 +0000</bug_when>
    <thetext>ISO-2022-JP doesn&apos;t contain JIS X 0212 from the start. (But ISO-2022-JP-1 and ISO-2022-JP-2 do.)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>78232</commentid>
    <comment_count>2</comment_count>
    <who name="">pub-w3</who>
    <bug_when>2012-11-12 20:18:33 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>78250</commentid>
    <comment_count>3</comment_count>
    <who name="">pub-w3</who>
    <bug_when>2012-11-12 23:31:30 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>78264</commentid>
    <comment_count>4</comment_count>
    <who name="Masatoshi Kimura">VYV03354</who>
    <bug_when>2012-11-13 12:21:01 +0000</bug_when>
    <thetext>I don&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>78327</commentid>
    <comment_count>5</comment_count>
    <who name="">pub-w3</who>
    <bug_when>2012-11-14 23:05:00 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>78405</commentid>
    <comment_count>6</comment_count>
    <who name="Anne">annevk</who>
    <bug_when>2012-11-16 12:50:17 +0000</bug_when>
    <thetext>https://github.com/whatwg/encoding/commit/04d78180f9dc07f471ae432cebe34915c03412de</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>