RE: For review: Character encodings in HTML and CSS

That sentence has gone, since the example definitely needed more
explanation.  See the new set of examples.

RI

============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)

http://www.w3.org/International/
http://rishida.net/




> -----Original Message-----
> From: Leif Halvard Silli [mailto:xn--mlform-iua@målform.no]
> Sent: 11 February 2010 07:18
> To: Richard Ishida
> Cc: www-international@w3.org
> Subject: Re: For review: Character encodings in HTML and CSS
> 
> Richard Ishida, Tue, 9 Feb 2010 13:20:29 -0000:
> >> Comments are being sought on this article prior to final release.
> >> Please send any comments to this list (www-international@w3.org). We
> >> expect to publish a final version in one to two weeks.
> >>
> >> See http://www.w3.org/International/tutorials/tutorial-char-enc/temp
> 
> Leif Halvard Silli, Wed, 10 Feb 2010 07:09:09 +0100:
> 
> > (2) The document appears thin when it comes to CSS escapes.
>   [ ... ]
> >   * (One of the) CSS examples could e.g. show what it means in practise
> > that the space character terminates the CSS escape, as this can be
> > highly confusing for authors. [...]
> 
> In that regard, your text currently says:
> 
>    "The CSS escape for a no-break space is <code>\A0</code>."
> 
> So why did you not include the "semicolon" here? Like this:
> 
>    "The CSS escape for a no-break space is <code>\A0 </code>."
> 
> You should perhaps also use a background or border or another stylish
> effect (that also works for CSS escapes ...) to make the different
> escapes you demonstrate throughout the text distinguishable for the
> readers.
> --
> leif halvard silli
> 
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.733 / Virus Database: 271.1.1/2680 - Release Date: 02/10/10
> 19:38:00

Received on Thursday, 18 February 2010 21:48:00 UTC