W3C home > Mailing lists > Public > www-validator-css@w3.org > June 2007

RE: BOM

From: Jan Eliasen <jan@eliasen.dk>
Date: Tue, 26 Jun 2007 19:38:28 +0200
To: <www-validator-css@w3.org>
Message-ID: <002601c7b818$ce60e150$0300000a@eliasen>
Hi

Thanks for the replies.

When you say that I should define the charset for my css files, you are
tallking about doing it in the html, right? Like this:
<link href="eliasen.eu.css" rel="stylesheet" type="text/css" charset="utf-8"
/>

Why not use a BOM with utf-8? It is perfectly legal, as I understand it, and
it even helps the programs that must read the data to know it is utf-8
encoded.

And I agree ASCII should be just fine - and in my case, it is. Only problem
is that it is automatically saved by VS.NET as utf-8 with a BOM :-/

-- 
eliasen

-----Original Message-----
From: Andreas Prilop [mailto:AndreasPrilop2007@trashmail.net] 
Sent: 26. juni 2007 17:46
To: www-validator-css@w3.org
Cc: Jan Eliasen
Subject: Re: BOM

On Mon, 25 Jun 2007, Jan Eliasen wrote:

> Can it be true that the online css validator can not accept the BOM 
> that appears first in unicode encoded files?

Here is an example with BOM:
http://www.unics.uni-hannover.de/nhtcapri/temp/dir-ltr.css

1) *Always* define an encoding (charset) for your files.
   This includes CSS files.

2) Never use a BOM with UTF-8.

3) In almost all cases, US-ASCII is sufficient for CSS files.

--
In memoriam Alan J. Flavell
http://groups.google.com/groups/search?q=author:Alan.J.Flavell

Received on Tuesday, 26 June 2007 20:16:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 June 2012 00:14:19 GMT