Re: For review: 6 new and 2 updated articles about character encoding

Gunnar Bittersmann, Mon, 16 Aug 2010 16:06:43 +0200:
> Picking some more nits in “Using character escapes in markup and CSS”:
> 
>> 3) http://www.w3.org/International/questions/qa-escapes.en.php#cssescapes

>> 
>> Proposal: Add the advice to always close NCRs in CSS with a trailing space.
> 
> If so, make '.\E9 motion' the first example, followed by '.\E9motion' 
> and '.\0000E9motion'.

You don't say why one should advice to always close CSS character 
escapes with a space. I like the advice as it is - the reader can 
understand and choose his/her preferred solution. To advice authors to 
always use a space is to beg them to make their code difficult to parse 
for the human eye.

Though there is one minor detail - in this quote:

]]
Because any white-space following the hexadecimal number is swallowed 
up as part of the escape, if you actually want a space to appear after 
the escaped character you will need to add two spaces (even if you have 
used a 6-digit hexadecimal number).
]]
 
Comment: The above quote may sound as if the two spaces problem is 
linked to the use of 6-digit escapes - partly because the way it is 
written and partly because it looks as a caption to the graphic above - 
which again is about 6-digit escapes. The only thing which hints that 
this is _always_ a problem, is the word "even" in the parenthesis: 
"(even if you have used a 6-digit hexadecimal number)". 

It would be better remove the parenthesis and instead say: You must use 
two spaces regardless of whether you use 6-digit escape or not." Or 
something like that.

> Stick to the same word, either "émotion" or "édition".

+1 to this.
-- 
leif halvard silli