> It opens URLs, CSS files, and HTML files. Most people open URLs.
Well, a URL is only a resource handle that defines the transmission protocol too. What you receive depends on the file that is referenced by the URL.
What I was trying to say was: The workflow in Stylizer dictates to open/load a HTML file. You cannot open CSS files from disk or by URL (and edit them). Because Stylizer always loads a HTML file first you could read the proper encoding from the HTML file.
> I think the solution here is to send the correct encoding in the HTTP header
AFAIK there is no way to configure Apache to read the encoding from a plain text file. This is why browsers apply the encoding of the HTML to the encoding of Javascript and CSS files.
> If you open http://test.juergenhoermann.de/test.css, you'll see that it's coming through as ISO-8859-1
You are wrong here, it comes through as UTF-8. But because Apache does not add the encoding value to the Content-Type: HTTP header your browser defaults to whatever you have set as the default encoding in your browser settings. As you can see this assumption your browser makes is only wrong if you load the css file directly.
Open http://test.juergenhoermann.de/test.html display the source and klick the link to the CSS. You will see this time the encoding is ok. This is because the Browser will use the encoding the HTML document specified.
What Stylizer needs to do is load the HTML file. Get the encoding from the HTML and save the value. When loading the CSS apply the encoding saved before to the CSS files.
