Re: Updated article: Handling character encodings in HTML and CSS

> “You can use @charset or HTTP headers to declare the encoding of your
> style sheet, but you only need to do so if your style sheet contains
> non-ASCII characters and, for some reason, you can’t rely on the
> encoding of the HTML and the associated style sheet to be the same.”

In German, this would be:

Man kann @charset oder HTTP-Header zur Angabe der Zeichencodierung 
seines Stylesheets verwenden, muss das aber nur tun, wenn 
Nicht-ASCII-Zeichen darin vorkommen (bspw. in Namen von Schriftarten, 
ID- oder Klassenbezeichnern usw.) und nicht sichergestellt ist, dass 
HTML und zugehöriges Stylesheet dieselbe Zeichencodierung verwenden.


The former version read “non-ASCII content, such as font names, ids or 
class names, etc.” I think the explanation is helpful to the reader. Why 
not keep it, maybe in parentheses:

…if your style sheet contains non-ASCII characters (such as font names, 
ids or class names, etc.) and, for some reason…

I have kept it in my translation.


Also, the paragraph “The articles pointed to describe the latest 
thinking with respect to the HTML5 specification. It is important to 
note, however, that the HTML5 specification is still not stable, so you 
should approach that information with care.”

seems to be outdated now that HTML5 has become a W3C recommendation.

Cheers,
Gunnar

Received on Tuesday, 2 June 2015 12:23:04 UTC