- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Wed, 24 Nov 2004 17:23:20 +0100
- To: Chris Lilley <chris@w3.org>
- Cc: www-svg@w3.org
* Chris Lilley wrote: >BH> Are you saying that the proposed registration would avoid that, i.e., >BH> that http://www.bjoernsworld.de/temp/utf8-or-iso-8859-1.svg must be >BH> considered UTF-8 encoded by all implementations? > >Tell, me, what happens if you read that file from local disk on your >server, or run xslt on it? How do you tell the implementations to ignore >the well formedness error? XML 1.0 defines no constraint (neither wf-constraint nor fatal errors) that would consider the document in this state non-compliant, the doc is both legal UTF-8 and legal ISO-8859-1. Regarding the other questions, I would not do that, but if I did I would tell the relevant tool of the higher-level encoding information just like I do when processing HTML documents, e.g. when using HTML Tidy on a UTF-8 encoded document I use the -utf8 command line switch as I have not yet implemented something else. For other tools, I've implemented encoding detection for HTML/XML documents in the HTML::Encoding Perl module (which, btw, would consider the document cited above ISO-8859-1, honoring the charset parameter).
Received on Wednesday, 24 November 2004 16:23:49 UTC