- From: Susan Lesch <lesch@w3.org>
- Date: Tue, 4 Mar 2003 22:40:44 -0800
- To: www-style@w3.org
These are mostly minor editorial comments for your "CSS3 module: text" Last Call Working Draft [1]. For use in prose and headlines it would help if the title was capitalized: CSS3 Module: Text. I also had a comment on one property: Line feed is two words [2] (reported and not fixed in XSL [3,4]). The 'linefeed-treatment' property should be 'line-feed-treatment' and globally in the prose (which switches back and forth now), s/linefeed/line feed/. I would say so somehow if you absolutely have to match XSL. Images like this one [5] that are black on transparent need a background color for people using a light on dark user style sheet otherwise they can be invisible. The white tables could use cellpadding="3" or so. s/working draft/Working Draft/ s/working group/Working Group/ s/Style activity/Style Activity/ s/members of the XSL Working Group (members only)/participants in the XSL Working Group (Members only) s/membership/Membership/ s/White-space control/White space control/ s/bidi/Bidi/ (one way or the other or BIDI) s/Unicode Bidirectional algorithm/Unicode bidirectional algorithm/ (one way or the other) s/Unicode technical report/Unicode Technical Report/ (one way or the other) s/for compatibility reason/for compatibility/ (or, for compatibility reasons) s/The following section frequently use/The following sections frequently use/ (or, uses) s/line-feed/line feed/ s/linefeed characters that immediately follows/linefeed characters that immediately follow/ s/non empty/non-empty/ s/uri/URI/ s/The visual hint after the element box only appear/The visual hint after the element box only appears/ s/is not very effective at small font size/is not very effective at small font sizes/ (or, font-size) s/These property specifies/These properties specify/ s/between each grapheme clusters/between each grapheme cluster/ s/The strip are arranged/The strips are arranged/ s/Strip corresponding to non-breakable objects and strip corresponding to/Strips corresponding to non-breakable objects and strips corresponding to/ s/mono-spaced/monospaced/ (I think) s/in both progression/in both progressions/ s/web site/Web site/ s/my interpret/may interpret/ s/algorthim/algorithm/ s/riht-to-left/right-to-left/ s/grapheme clustes/grapheme clusters/ s/[[HTML4.01]/[HTML4.01]/ s/This is one of the main reason/This is one of the main reasons/ UAX #9 can be a normative reference. It's a free resource of interest that doesn't appear to be superseded: http://www.unicode.org/reports/tr9/ s/Unicode Standard ([UNICODE] bidirectional algorithm/Unicode Standard ([UNICODE]) bidirectional (Bidi) algorithm ([UAX-9])/ and then in later instances, "Unicode Bidi algorithm" and "Bidi algorithm" can stand alone when you need them to. In the first occurrence, s/user agent/user agent (UA)/ and then you can use "UA" standalone when you need to. For RFC 2119 key words, "For legibility these keywords are used in lowercase form." Markup suggestion here: http://www.w3.org/2001/06/manual/#RFCs The titles of references should be links to dated versions. Suggestions here: http://www.w3.org/2001/06/manual/#References [1] http://www.w3.org/TR/2003/WD-css3-text-20030226/ [2] http://www.unicode.org/charts/PDF/U0000.pdf [3] http://lists.w3.org/Archives/Public/xsl-editors/2001JanMar/0109.html [4] http://lists.w3.org/Archives/Public/xsl-editors/2001JulSep/0061.html [5] http://www.w3.org/TR/css3-text/tj-iw-ex.gif Best wishes for your project, -- Susan Lesch http://www.w3.org/People/Lesch/ mailto:lesch@w3.org tel:+1.858.483.4819 World Wide Web Consortium (W3C) http://www.w3.org/
Received on Tuesday, 4 March 2003 22:40:07 UTC