- From: Cliff Schmidt <cschmidt@microsoft.com>
- Date: Fri, 7 Jun 2002 01:28 +0900
- To: www-i18n-comments@w3.org
- Cc: cschmidt@microsoft.com (Cliff Schmidt)
This is a last call comment from Cliff Schmidt (cschmidt@microsoft.com) on the Character Model for the World Wide Web 1.0 (http://www.w3.org/TR/2002/WD-charmod-20020430/). Semi-structured version of the comment: Submitted by: Cliff Schmidt (cschmidt@microsoft.com) Submitted on behalf of (maybe empty): Microsoft Comment type: editorial Chapter/section the comment applies to: 4.2.3 Fully-normalized text The comment will be visible to: public Comment title: Definition of "Fully-Normalized" Comment: -------------------------------------------------------------------------- "Text is fully-normalized if: 1. the text is in a Unicode encoding form, is include-normalized and none of the constructs comprising the text begin with a composing character or a character escape representing a composing character; or 2. the text is in a legacy encoding and, if it were transcoded to a Unicode encoding form by a normalizing transcoder, the resulting text would satisfy clause 1 above." -------------------------------------------------------------------------- CONCERN: Based on previous definitions, "Unicode-normalized" may be a more precise term than "Unicode encoding form" (if the implication is that full normalization requires include-normalization, which requires Unicode normalization as defined in 4.2.1 (http://www.w3.org/TR/2002/WD-charmod-20020430/#sec-UnicodeNormalized). RECOMMENDATION: Refer to text that is "Unicode-normalized" (possibly linked to the definition at http://www.w3.org/TR/2002/WD-charmod-20020430/#sec-UnicodeNormalized), instead of "Unicode encoding form". Structured version of the comment: <lc-comment visibility="public" status="pending" decision="pending" impact="editorial"> <originator email="cschmidt@microsoft.com" represents="Microsoft" >Cliff Schmidt</originator> <charmod-section href='http://www.w3.org/TR/2002/WD-charmod-20020430/#sec-FullyNormalized' >4.2.3</charmod-section> <title>Definition of "Fully-Normalized"</title> <description> <comment> <dated-link date="2002-06-06" >Definition of "Fully-Normalized"</dated-link> <para>-------------------------------------------------------------------------- "Text is fully-normalized if: 1. the text is in a Unicode encoding form, is include-normalized and none of the constructs comprising the text begin with a composing character or a character escape representing a composing character; or 2. the text is in a legacy encoding and, if it were transcoded to a Unicode encoding form by a normalizing transcoder, the resulting text would satisfy clause 1 above." -------------------------------------------------------------------------- CONCERN: Based on previous definitions, "Unicode-normalized" may be a more precise term than "Unicode encoding form" (if the implication is that full normalization requires include-normalization, which requires Unicode normalization as defined in 4.2.1 (http://www.w3.org/TR/2002/WD-charmod-20020430/#sec-UnicodeNormalized). RECOMMENDATION: Refer to text that is "Unicode-normalized" (possibly linked to the definition at http://www.w3.org/TR/2002/WD-charmod-20020430/#sec-UnicodeNormalized), instead of "Unicode encoding form". </para> </comment> </description> </lc-comment>
Received on Thursday, 6 June 2002 12:28:24 UTC