W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2006

Re: Possible wording for acknowledged but yet uncovered requirement related to non-textual content

From: Felix Sasaki <fsasaki@w3.org>
Date: Thu, 27 Apr 2006 15:12:13 +0900
Message-ID: <445060BD.1030909@w3.org>
To: Yves Savourel <yves@opentag.com>
Cc: public-i18n-its@w3.org
Hi Yves, all,


Yves Savourel wrote:
> Hi all,
> 
> I've added (and slightly adapted) Christian's text in the Requirements document:
> 
> I was not sure if we want to make this a new requirement or to simply modify the "Indicator of translatability" requirement. So I
> added text for both cases:
> 
> http://www.w3.org/International/its/requirements/Overview.html#transinfo
> 
> http://www.w3.org/International/its/requirements/Overview.html#objects
> 
> Let me know whether which addition we should keep.
> 
> Personally I'm not quite sure. But if nobody answers, I would probably keep the added R026 and remove the added text in the
> "Indicator of translatability", since a new req make this more generic.

I would do the same.

- Felix

> 
> -ys
> 
> -----Original Message-----
> From: public-i18n-its-request@w3.org [mailto:public-i18n-its-request@w3.org] On Behalf Of Felix Sasaki
> Sent: Thursday, April 27, 2006 3:05 AM
> To: Sebastian Rahtz
> Cc: Lieske, Christian; public-i18n-its@w3.org
> Subject: Re: Possible wording for acknowledged but yet uncovered requirement related to non-textual content
> 
> I like this. Christians text sounds like a requirement, which fits good into the requirements document. Sebastians text is a
> clarification about what we can't achieve in the moment, which fits in the tagset document.
> 
> There is only one drawback about the example:
> 
> <p xmlns:its="http://www.w3.org/2005/11/its">As you can see in
>     <img src="instructions.jpg" its:translate="yes"/>,
>     the truth is not always out there.</p>
> 
> The default selection says that local its:translate attributes talk about "Textual content of element, including content of child
> elements, but excluding attributes", see http://www.w3.org/TR/its/#selection-defaults-etc
> So the its:translate attribute in the example doesn't attach ITS translatability information to the @src attribute.
> 
> An solution would be a global rule:
> 
> <its:rules><its:translateRule translate="yes"
> selector="//p/img/@src"/></its:rules> ...
> <p xmlns:its="http://www.w3.org/2005/11/its">As you can see in
>     <img src="instructions.jpg" its:translate="yes"/>,
>     the truth is not always out there.</p>
> 
> Everybody fine with that? If nobody disagrees, I would change the example.
> 
> - Felix
> 
> 



Received on Thursday, 27 April 2006 06:12:27 UTC

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