- From: Björn Höhrmann <bjoern@hoehrmann.de>
- Date: Tue, 13 Apr 2004 13:43:18 +0900
- To: www-i18n-comments@w3.org
- Cc: bjoern@hoehrmann.de (Björn Höhrmann)
This is a last call comment from Björn Höhrmann (bjoern@hoehrmann.de) 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: Björn Höhrmann (bjoern@hoehrmann.de)
Submitted on behalf of (maybe empty):
Comment type: editorial
Chapter/section the comment applies to: Overall
The comment will be visible to: public
Comment title: Avoid inline conformance criteria
Comment:
For example in section 4.6, Character Escaping, conformance criteria are inside a list, one list item for each item, while in e.g. section 4.4.2, Character encoding identification, these stick all together in one overly long paragraph. This makes it difficult to scan
http://www.useit.com/alertbox/whyscanning.html
the text, please don't combine more than two (or one?) conformance criteria in one paragraph and use lists instead.
Structured version of the comment:
<lc-comment
visibility="public" status="pending"
decision="pending" impact="editorial" id="LC-">
<originator email="bjoern@hoehrmann.de"
>Björn Höhrmann</originator>
<represents email=""
>-</represents>
<charmod-section href='http://www.w3.org/TR/2004/WD-charmod-20040225/'
>Overall</charmod-section>
<title>Avoid inline conformance criteria</title>
<description>
<comment>
<dated-link date="2004-04-13"
href="http://www.w3.org/mid/222534239.20040413044318@toro.w3.mag.keio.ac.jp"
>Avoid inline conformance criteria</dated-link>
<para>For example in section 4.6, Character Escaping, conformance criteria are inside a list, one list item for each item, while in e.g. section 4.4.2, Character encoding identification, these stick all together in one overly long paragraph. This makes it difficult to scan
http://www.useit.com/alertbox/whyscanning.html
the text, please don't combine more than two (or one?) conformance criteria in one paragraph and use lists instead.</para>
</comment>
</description>
</lc-comment>
Received on Tuesday, 13 April 2004 00:43:20 UTC