The following reviews are available:
The reviews have been collected from previous reviews of the I18N Core WG and updated to the current Working Draft of CSS 2.1 by Felix Sasaki.
These comments have been endorsed by the I18N Core WG.
| ID | Location | Comment | Mail thread | Accepted |
|---|---|---|---|---|
| 1 | Sec. 15 |
css21 doesn't have the examples of i18n fonts anymore. Could they be added again? |
thread | unclear (see previous review) |
| 2 | Sec. 4 and general | Section on URIs doesn't mention IRI. Please add a normative reference to IRI. | thread, comment 4, thread | not accepted (see previous review) |
| 3 | Sec. 5.11.4 | CSS :lang should be defined in terms of the document language and not in terms of RFC 3066. | thread, thread, thread | partially accepted: There is nothing written about the empty tag (see previous review) |
| 4 | Sec. 16.5 | Conforming user agents may consider the value of 'text-transform' to be 'none' for scripts for which there is no transform. Please change "See RFC 3066 ([RFC3066]) for ways ..." to "See RFC 3066 ([RFC3066]) or its successor for ways ..." | thread | not accepted (see previous review) |
| 5 | Sec. 9.10 | If you implement bidi then you must use the Unicode Bidirectional Algorithm. | thread, thread | not accepted (see previous review) |
| 6 | Appendix B bibliography | Update of references: Unicode, removal of comment on bidi in the corrigenda, ISO 10646 update, renewal of associated roadmap links, CHARSETS IANA registry should refer to the IANA web site, Reference to RFC 3066, Reference to IRI should also be added. | thread | Unicode: updated. ISO 10646: not updated. Roadmap links: updated. No ref. to IRI. Ref. to RFC 3066 only informative. Ref. to IANA web site exists. (see previous review) |
| 7 | Sec. 15 | Should @font-face be removed? Please not! | thread | not accepted (see previous review) |
| 8 | General? | Character encoding should be aligned with XML. | thread begin and consensus | partially accepted, only utf-8 is mandatory, not utf-16. (see previous review) |
| 9 | Sec. on list-style-type | We are aware that there is a lack of implementations for the international styles. We are unhappy with the situation, but we will not continue this comment. | thread, thread | partially accepted: not restored are hebrew , cjk-ideographic, hiragana, katakana, hiragana-iroha, katakana-iroha (see previous review) |
| 10 | General | Editorial: The specification is encoded as iso-8859-1. The server serves it as utf-8. Please encode the document as utf-8 and change the <meta> tags accordingly. | - | - |
The reviews have been collected from previous reviews of the I18N Core WG by Felix Sasaki.
-
| ID | Location | Comment | Mail thread | Accepted |
|---|---|---|---|---|
| 1 | Sec. 15 |
css21 doesn't have the examples of i18n fonts anymore. Could they be added again? |
thread | - |
| 2 | Sec. 4.1.3 |
In section 4.1.3, in the third type of escape it says that if a character in the range [0-9a-zA-Z] follows a hexadecimal number, the end of the number needs to be made clear. The range should be [0-9a-fA-F], since characters g-zG-Z are clearly beyond the hexadecimal number. | thread, comment 1 | accepted |
| 3 | Sec. 4.4 | Mention should be made of the Unicode BOM and its relationship to the encoding of the file. Is BOM allowed? | thread, comment 2, thread | accepted |
| 4 | General | Character numbering is confusing. Please use the Unicode notation for character codes. | thread, comment 3 | accepted, e.g. sec. 4.1. |
| 5 | Sec. 4 and general | Section on URIs doesn't mention IRI. Please add a normative reference to IRI. | thread, comment 4, thread | not accepted. |
| 6 | Sec. 4.3.7 | The section doesn't describe how the user can get a linefeed. Please add one. | thread, comment 5 | accepted |
| 7 | Sec. 5.11.4 | CSS :lang should address rfc 3066 and the empty tag as well. | thread, thread, thread | partially accepted: There is nothing written about the empty tag. |
| 8 | Sec. 16.5 | Some browsers do not apply text-transform properly if it is used to change case and the text is copied to the clipboard. copying to the clipboard should copy text as rendered, taking case into account. | thread,thread | not accepted, see thread |
| 9 | Sec. 16.5 | "...consider the value of 'text-transform' to be 'none' for characters that are not from the Latin-1 repertoire and for elements in languages for which the transformation is different from that specified by the case-conversion tables of ISO 10646 ([ISO10646]). ". "and" should be replaced by EITHER / OR. Instead of mentioning Latin-1, please have support for the Unicode case conversion table. The reference to 2070 should be upgraded to rfc 3066. | thread | not accepted |
| 10 | Sec. 16.5 | The reference to 2070 should be upgraded to rfc 3066. | thread | accepted |
| 11 | Sec. 9.10 | "If a document contains right-to-left characters, and if the user agent displays these characters in right-to-left order, the user agent must apply the bidirectional algorithm." should be changed to "If the user agent displays right-to-left characters in right-to-left order, and if a document contains right-to-left characters or has any right-to-left direction settings (in Markup or via CSS), the user agent must apply the bidirectional algorithm to the document.". | thread, thread | not accepted |
| 12 | Appendix B bibliography | Update of references: Unicode, removal of comment on bidi in the corrigenda, ISO 10646 update, renewal of associated roadmap links, CHARSETS IANA registry should refer to the IANA web site, Reference to RFC 3066, Reference to IRI should also be added. | thread | Unicode: updated. ISO 10646: not updated. Roadmap links: updated. No ref. to IRI. Ref. to RFC 3066 only informative. Ref. to IANA web site exists. |
| 13 | Sec. 15 | Should @font-face be removed? Please not! | thread | not accepted |
| 14 | General? | Character encoding should be aligned with XML. | thread begin and consensus | partially accepted, only utf-8 is mandatory, not utf-16. |
| 15 | Sec. 16.6.2 | Bidirectionality with Whitespace Collapsing | thread | explained in the thread, spec not changed |
| 16 | Sec. on list-style-type | Please restore the international styles. They have been implemented by some browsers. | thread, thread | partially accepted: not restored are lower-alpha, upper-alpha, hebrew , cjk-ideographic, hiragana, katakana, hiragana-iroha, katakana-iroha |
| 17 | General | Please follow the i18n recommendations wrt css encoding declarations | thread | partially accepted: No error is raised if the @charset declaration and the BOM contradict. |
Version: $Id: css2-1-review.html,v 1.10 2005/07/27 05:55:32 fsasaki Exp $