2617 2005-12-26 03:06:35 +0000 ISO-8859-3 no longer supported 2007-01-15 05:59:41 +0000 1 1 1 Unclassified Validator check 0.7.1 PC Windows XP RESOLVED FIXED http://www.gtalbot.org/FirefoxSection/Maltese_characters_testing.html P2 normal 0.7.2 1 info link www-validator-cvs oldest_to_newest 7543 0 info 2005-12-26 03:06:44 +0000 Back 2 years ago (or so), I created a webpage in Maltese for someone in need of support in a newsgroup. Now, I just updated the page and validated and I got this error message: " A fatal error occurred when attempting to transcode the character encoding of the document. Either we do not support this character encoding ('iso-8859-3') yet, or you have specified a non-existent character encoding (often a misspelling). 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. " I'm sure iso-8859-3 as charset used to be supported by W3C validator. I can make the webpage at the provided URL leaner, reduced. 7717 1 info 2006-01-09 03:17:27 +0000 For whatever it's worth, there is no problem with the v 0.8-dev : http://qa-dev.w3.org/wmvs/HEAD/check?uri=http%3A%2F%2Fwww.gtalbot.org%2FNetscape7Section%2FMaltese_characters_testing.html 7718 2 bjoern 2006-01-09 03:25:22 +0000 That means I fixed it; as far as I am concerned at least... 8323 3 ville.skytta 2006-02-18 20:48:06 +0000 Now fixed in the 0.7 branch too, it was a config file bug. http://qa-dev.w3.org/wmvs/0.7/check?uri=http%3A%2F%2Fwww.gtalbot.org%2FNetscape7Section%2FMaltese_characters_testing.html 8329 4 ot 2006-02-19 22:07:54 +0000 good catch, thanks Ville. Will go into 0.7.2 today. 13527 5 info 2007-01-15 05:59:41 +0000 The url has changed, has been updated. The validation link for v 0.8-dev should now be: http://qa-dev.w3.org/wmvs/HEAD/check?uri=http%3A%2F%2Fwww.gtalbot.org%2FFirefoxSection%2FMaltese_characters_testing.html I'm updating the info of this bug just in case someone needs to visit the page or needs to verify that this bug has still been fixed. Cheers, Gérard