W3C home > Mailing lists > Public > www-svg@w3.org > January 2005

Re: SVG12: Script Encoding

From: Robin Berjon <robin.berjon@expway.fr>
Date: Mon, 17 Jan 2005 17:45:32 +0100
Message-ID: <41EBEBAC.9020604@expway.fr>
To: Ian Hickson <ian@hixie.ch>
Cc: www-svg@w3.org

Ian Hickson wrote:
> On Sat, 15 Jan 2005, Bjoern Hoehrmann wrote:
>>Various document formats either provide or propose means to specify the 
>>character encoding of external scripts if there is no reliable way to 
>>determine the character encoding e.g. when loading the scripts from the 
>>local disk if the file system does not support such meta data. Among 
>>these formats are HTML 4.01 (<link rel=script charset=...>), VoiceXML 
>>2.0 (<script charset=...>), XHTML 2.0 (<script charset=...>) and various 
>>derived formats. Please change SVG 1.2 to provide similar means to 
>>ensure interoperable encoding detection for external scripts.
> 
> Personally I consider those attributes to be a huge pain in the neck. They 
> have caused any number of problems on the Web (e.g. the same resource 
> being treated in two totally different ways purely due to the linking 
> mechanism). Please rely only on the resource's own metadata to make this
> kind of determination.

I agree, charset attributes must die. If you've written your script in 
some baroque legacy encoding and stored it on the file system you've 
screwed yourself and deservedly so.

-- 
Robin Berjon
   Research Scientist
   Expway, http://expway.com/
Received on Monday, 17 January 2005 16:45:57 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:29 GMT