This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Amaya 11.3.1 (Dec 9 2009) Mac OS X 10.6.3 (10D573) I've been able to reliably reproduce the bug following these steps: 1. Create a new style sheet in Amaya, selecting utf-8 as the charset. If you then navigate to Views>Document Info the MIME type should read text/css and the Charset utf-8. Now on my computer this doesn't yet create a file at the save destination. 2. File>Save As... MIME type and Charset should be filled correctly. If I then close the document and reopen it using File>Open and then view the document information the MIME type has been retained yet the Charset has changed to iso-8859-1. If the CSS document is linked externally in a X/HTML document and I open it using Format>Style Sheets>Open... and select it in the pop-up box and then view the document information the MIME type now reads "Unknown" and the Charset "utf-8" - even though I can repeatedly save the document as text/css and UTF-8. Including an @charset rule at the beginning of the document has no effect.
Correction: after opening the externally linked style sheet via Format>Style Sheets>Open... the MIME type reads "Unknown" *and* and the Charset "iso-8859-1." So it's lost type and mixed the encoding. Apologies. I'd typed charset and utf-8 several times already and didn't notice the difference before submitting.