W3C home > Mailing lists > Public > www-svg@w3.org > February 2004

Re: SVG 1.2 and parseXML

From: Jim Ley <jim@jibbering.com>
Date: Tue, 17 Feb 2004 10:08:05 +0000 (UTC)
To: www-svg@w3.org
Message-ID: <loom.20040217T105942-980@post.gmane.org>

Chris Peto <CPeto <at> resource-solutions.de> writes:

| Problems:
| 1. I have many CAD plans or Templates, in svg, that have gone through
| CAD2SVG, Adobe, Corel or other svg editors.  These plans or templates always
| have chracter set information plus some have DTD with ENTITIES.  I always
| use getURL and parseXML to load these plans.  As of 1.2, I can no longer use
| any of these files.

parseXML takes a string, in javascript (which I assume you're using here) 
strings are defined to be of a certain type (16 bit integers normally 
representing UTF-16) so you couldn't realistically put other charsets in there, 
getURL would need to return something other than a string, which will cause 
problems for people not wanting to use XML.  I would imagine other languages 
have similar issues, with the internal representation of a string.

Character set handling can be done at the http level, or the javascript source 
level, there's problems bubbling it down to the script level.

| 2. I live in Europe and we have German, French, Spanish, etc, characters
| sets that will also not make it through parseXML because character set xml
| processor commands are also not allowed.

That's a complete irrelevance, it just limits you to the character sets you can 
use, it does not prevent you using any (and there are other sensible reasons 
for avoiding Latin-1, and IMO few good reasons for)

Received on Tuesday, 17 February 2004 05:08:10 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:46:58 UTC