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 981 - Character encoding "latin-1" yields useless error
Summary: Character encoding "latin-1" yields useless error
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.6.7
Hardware: PC Windows XP
: P2 normal
Target Milestone: 0.7.0
Assignee: Terje Bless
QA Contact: qa-dev tracking
Depends on:
Reported: 2005-01-08 16:57 UTC by Thijs Kinkhorst
Modified: 2005-10-19 06:28 UTC (History)
0 users

See Also:


Description Thijs Kinkhorst 2005-01-08 16:57:42 UTC
When trying to validate a website at the mentioned URL, I get the following message:

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 "latin-1".

The error was "".

Of course this is a useless error, empty string. It provides no clue whatsoever
as to what I'm doing wrong, I believe that "latin-1" is a valid charset
(overriding it with its equivalent "iso-8859-1" works just fine).
Comment 1 Ville Skyttä 2005-01-09 11:26:47 UTC
I have fixed the "" part of the error message in CVS, this will be included in
the next release.

However, the part of the current validator's error message which you did not
quote here contains links to resources that help you to choose a correct
character encoding:

 | 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.
 | IANA maintains the list of official names for character sets and the WDG has
 | some information to help you correctly specify the character encoding.
"latin-1" is not an official IANA encoding or alias.  ("latin1" is a valid alias
for "iso-8859-1", but we don't currently support it; that's another issue).

To fix the problem with your page, just use the official preferred MIME name