- From: A. Vine <andrea.vine@sun.com>
- Date: Mon, 13 Dec 2004 16:41:23 -0800
- To: www-i18n-comments@w3.org
All, Some comments on: "Authoring Techniques for XHTML & HTML Internationalization: Characters and Encodings 1.0" Regards, Andrea Edits: ------ 1.2 "summarises" => "summarizes" (The rest of the doc is written in Am. English, so this is for consistency. It is disturbing to keep switching back and forth.) 2.0 under "Check that user agents ...", 3rd paragraph "a user agents" => "a user agent" 3.1 "ie." => "i.e." (ref. http://m-w.com/cgi-bin/dictionary?book=Dictionary&va=i.e.&x=0&y=0 ) under " If declaring the character encoding in the HTTP header, ensure ..." 1st paragraph, remove the "or" in front of the last long clause or remove the "etc." at the end. Pick one. "For XHTML served as text/html, where practical use an XML declaration with an encoding attribute." => "For XHTML served as text/html, where practical, use an XML declaration with an encoding attribute." 4.0 "If you use escapes, to represent characters in a style attribute consider using CSS escapes, rather than NCRs or entities." => "If you use escapes to represent characters in a style attribute, consider using CSS escapes, rather than NCRs or entities." Semantics: ---------- Calling both a "<META />statement and a <?xml ?> statement "meta statements" becomes _really_ confusing in 3.2 under "For XHTML served as text/html ..." Suggest calling them 2 different things, such as HTML meta statement and XML meta statement to avoid confusing the poor folks trying to read this. 3.4 "Use the preferred names from IANA's charset registry." Go ahead and put MIME in the title line, since you've already got IANA and charset in there, e.g. "Use the preferred MIME names from IANA's charset registry." Heck, if they know what IANA is and understand what a charset name is, the acronym MIME won't frighten them.
Received on Tuesday, 14 December 2004 00:36:46 UTC