This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 823 - encoding troubles
Summary: encoding troubles
Alias: None
Product: Validator
Classification: Unclassified
Component: Website (show other bugs)
Version: 0.6.6
Hardware: Other Windows 98
: P2 normal
Target Milestone: ---
Assignee: Olivier Thereaux
QA Contact: qa-dev tracking
Depends on:
Reported: 2004-07-09 09:36 UTC by Alex Shuman
Modified: 2004-08-05 23:47 UTC (History)
0 users

See Also:


Description Alex Shuman 2004-07-09 09:36:29 UTC
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?
Comment 1 Terje Bless 2004-08-05 08:22:11 UTC
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 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
Comment 2 Alex Shuman 2004-08-05 19:47:05 UTC
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'. not works for now due to hosting 
problems, but (with same content) works.