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

RE: BOM

From: Douglas Perreault <doug@perreault.us>
Date: Wed, 27 Jun 2007 12:39:44 -0400
To: "'Sierk Bornemann'" <sierkb@gmx.de>
Cc: "'olivier Thereaux'" <ot@w3.org>, "'Jan Eliasen'" <jan@eliasen.dk>, <www-validator-css@w3.org>
Message-ID: <018d01c7b8d9$c564cc80$502e6580$@us>

Sierk,

Thank you for your replies. I am glad there is someone there actually trying
to help.

I do not use .Net, so the machine.config and web.config files don't apply.

It may be that the web server is sending ISO-8859-1 as the file type and
that would be absolutely fine with me if I could keep the BOM out of the
file. I can't seem to do that. I don't use any special characters in these
files, so I'd love to get rid of the whole issue if I could. There appears
to be no mechanism in a CSS file to state that it is UTF-8 / ISO-8859-1 /
etc. I can do this in an HTML file if necessary, but it does not appear
possible in a CSS file.



I usually transfer the files using Microsoft Expression Web (and previously
FrontPage) as it's the easiest. I don't use Dreamweaver as I never liked
it's heavy dependence on tables. 

However, in testing the problem I tried using FTP through Internet Explorer
and then using WS-FTP and even using FTP from the command line. I also tried
using web folders and Terminal Services. Regardless of the approach, the
plain ASCII file without a BOM on my side ended up with the BOM once it was
saved on the server.

The only way I could get rid of that BOM was to then log in to the server,
open the file, and then save it without the BOM using a text editor that
would allow me to do it (Notepad will, but it took me a while to figure out
how).

As Jan notes, nearly no one can do this in the real world as most people are
not able to actually log in to the server. If I weren't able to do that, I
would not have been able to correct the files.

The links you sent deal with the proper display of .Net pages. I'm not using
.Net. In addition, the characters I use are found in standard ASCII. I would
just as soon not have to deal with UTF-8, but I have no choice because of
the server.

--Doug
Received on Wednesday, 27 June 2007 16:40:33 GMT

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