Unicode version

[GoogleCodeExporter]

Reference version 6 rather than 5.  Ver 6 allows 
variation selectors, which are strongly required in 
Japan.

Original issue reported on code.google.com by eb2m...@gmail.com on 11 Dec 2013 at 7:17

[GoogleCodeExporter]

Emoji is also strongly required.  I heard that many Asian languages also 
strongly require Unicode 6.  The latest version is 6.3.  See 
http://www.unicode.org/versions/

Original comment by eb2m...@gmail.com on 12 Dec 2013 at 1:07

[GoogleCodeExporter]

Makoto, the reason the specs reference Unicode 5.0.0 is that we inherit that 
from XML1.0 5ed. How can we reference Unicode 6.3 without breaking XML1.0 5ed 
compatibility?

Original comment by markus.g...@gmail.com on 13 Jan 2014 at 9:16

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The titles of the two normative references in W3C XML are "ISO/IEC 10646" and 
"Unicode".  These are meant to reference the latest versions of 10646  and 
Unicode, respectively.  The phrase "as, from time to time, amended, replaced by 
a new edition or expanded by the addition of new parts. [Geneva]: International 
Organization for Standardization. (See http://www.iso.org/iso/home.htm for the 
latest version.)" makes clear that these are undated references.  It is true 
that the Unicode entry has a version number, but I was a member of the W3C XML 
WG, and am very sure that XML was intended to use the latest versions of 
Unicode and 10646.

After the publication of XML 1.0, the Unicode consortium has made a 
recommendation.  An undated reference should be referenced as "The Unicode 
Consortium. The Unicode Standard.  http://www.unicode.org/versions/latest/", as 
recommended in 
http://www.unicode.org/versions/Unicode6.3.0/#Version_Information.  We should 
follow this recommendation.  Also, see 
http://www.w3.org/TR/charmod/#sec-RefUnicode.

Original comment by eb2m...@gmail.com on 14 Jan 2014 at 7:03

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

After discussion with Makoto, proposed resolution is: 
* In OCF, change [TR15] to the undated "http://www.unicode.org/reports/tr15/" 
* Globally, change our [Unicode] reference to "The Unicode Consortium. The 
Unicode Standard.  http://www.unicode.org/versions/latest/". This way of 
referencing is as pointed out in #4 the recommended way. 

Original comment by markus.g...@gmail.com on 30 Jan 2014 at 11:08

[GoogleCodeExporter]

References have been updated:

https://code.google.com/p/epub-revision/source/detail?r=4895

Original comment by mgarrish on 25 Feb 2014 at 5:23

• Changed state: FinalReview

[GoogleCodeExporter]

Original comment by markus.g...@gmail.com on 27 Feb 2014 at 10:06

• Changed state: Fixed