On Wednesday, November 24, 2004, 3:36:29 PM, Bjoern wrote:
BH> * Robin Berjon wrote:
>>Those are the precise people we do *not* want to put the burden of
>>resolving this on. They will have to deal with uncooperative server
>>administrators that'll refuse to let them control the character encoding
>>because all they (think they) know about character encodings is that you
>>have to provide one to avoid certain XSS attacks.
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?
--
Chris Lilley mailto:chris@w3.org
Chair, W3C SVG Working Group
Member, W3C Technical Architecture Group