W3C home > Mailing lists > Public > public-i18n-its@w3.org > January to March 2008

RE: Proposal for comments on SVG Tiny 1.2

From: Yves Savourel <yves@opentag.com>
Date: Sun, 24 Feb 2008 18:52:38 -0700
To: "'Felix Sasaki'" <fsasaki@w3.org>
Cc: <public-i18n-its@w3.org>
Message-ID: <000101c87751$1a79def0$0400a8c0@BREIZH>

I see, but if the SVG part has no non-SVG elements in it, maybe we can do selector="//svg:svg" instead of "//svg:*" ?

Otherwise the rest of the email looks fine to me.

-ys

-----Original Message-----
From: Felix Sasaki [mailto:fsasaki@w3.org] 
Sent: Sunday, February 24, 2008 3:24 PM
To: Yves Savourel
Cc: public-i18n-its@w3.org
Subject: Re: Proposal for comments on SVG Tiny 1.2

Hi Yves,

Yves Savourel wrote:
> Hi Felix,
>
>   
>> 2) We would like you to provide the following ITS global rules file 
>> for SVG Tiny 1.2:
>>
>> <its:rules xmlns:its="http://www.w3.org/2005/11/its"
>>  version="1.0" xmlns:svg="http://www.w3.org/2000/svg">
>>  <its:translateRule selector="//svg:*" translate="no"/>  
>> <its:translateRule selector="//svg:metadata | //svg:text | //svg:desc 
>> | //svg:title | //svg:tspan" translate="yes"/> </its:rules>
>>     
>
> Would it be easier to use the root <svg> to set the default to 'do-not-translate', rather than svg:* ?
>
> This would make the processing lighter since much less nodes would have to be set. Or am I missing something?
>   

 From my understanding SVG can be mixed with other vocabularies, and 
does not necessarily appear on the root of the document. That would make 
the explicit XPath expression //svg::* necessary, in contrast to 
/svg:svg . But if we agree on the rest of the comment, we can ask the 
question about the appropriate XPath expression also in our mail to the 
SVG folks.

Felix
Received on Monday, 25 February 2008 01:52:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:09 UTC