This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
While uploading this page for validation using Opera browser's Frame=>Validate Source function - all is ok. But while trying to validate using URL and 'detect encoding automatically', the following error is displayed: Sorry! A fatal error occurred when attempting to transcode the character encoding of the document. Either we do not support this character encoding yet, or you have specified a non-existent character encoding (often a misspelling). The detected character encoding was "win1251". The error was "". If you believe the character encoding to be valid you can submit a request for that character encoding (see the feedback page for details) and we will look into supporting it in the future. here is my encoding meta tag: <meta http-equiv="Content-Type" content="text/html; charset=windows-1251"> what is wrong?
Most likely your server is sending a charset parameter with the Content-Type header specifying "win1251" instead of "windows-1251". The character encoding given in a <meta> element does not override the data provided directly in the HTTP transaction. In other words, this is most likely a configuration issue with your web server. I can't seem to reach http://neon2.neon.net.ua/ at the moment so I can't verify that this is the issue. Please investigate the issue on your end and let us know the result. PS. You should consider using UNICODE (UTF-8) instead of a proprietary encoding such as windows -1251.
issue was resolved by setting in .htaccess AddDefaultCharset windows-1251 but Apache 2.0 seem to have default charset 'win1251' for that encoding, not 'windows-1251'. http://neon2.neon.net.ua/ not works for now due to hosting problems, but http://neon2.becor.org.ua/ (with same content) works.