https://bugzilla.novell.com/show_bug.cgi?id=627139
https://bugzilla.novell.com/show_bug.cgi?id=627139#c1 Atsushi Enomoto <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Minor |Enhancement --- Comment #1 from Atsushi Enomoto <[email protected]> 2011-01-20 06:41:39 UTC --- The XML 1.0 specification section 4.3.3 says that such an encoding name "UTF8" SHOULD be prefixed "x-" as explained below (excerpt from http://www.w3.org/TR/REC-xml/#charencoding ): In an encoding declaration, the values " UTF-8 ", " UTF-16 ", " ISO-10646-UCS-2 ", and " ISO-10646-UCS-4 " SHOULD be used for the various encodings and transformations of Unicode / ISO/IEC 10646, the values " ISO-8859-1 ", " ISO-8859-2 ", ... " ISO-8859- n " (where n is the part number) SHOULD be used for the parts of ISO 8859, and the values " ISO-2022-JP ", " Shift_JIS ", and " EUC-JP " SHOULD be used for the various encoded forms of JIS X-0208-1997. It is RECOMMENDED that character encodings registered (as charsets) with the Internet Assigned Numbers Authority [IANA-CHARSETS], other than those just listed, be referred to using their registered names; other encodings SHOULD use names starting with an "x-" prefix. XML processors SHOULD match character encoding names in a case-insensitive way and SHOULD either interpret an IANA-registered name as the encoding registered at IANA for that name or treat it as unknown (processors are, of course, not required to support all IANA-registered encodings). So your report requests one kind of specification-violating behavior which harms XML 1.0 interoperability. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
