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

RE: Directionality Scope/inheritance issue (same as translatability)

From: Yves Savourel <yves@opentag.com>
Date: Sun, 26 Mar 2006 21:53:08 -0700
To: <public-i18n-its@w3.org>
Message-ID: <003001c6515a$58724c70$0300a8c0@Breizh>

Hi felix, all,

> I think there is a way to achieve what you want, just 
> by going for 2) and by saying:
> <its:documentRules xmlns:its="http://www.w3.org/2005/11/its">
> 1 <its:translateRule its:translate="yes" its:selector="//textInCode"/>
> 2 <its:translateRule its:translate="no" its:selector="//code"/>
> 3 <its:translateRule its:translate="yes"
> its:selector="//*[@trans='true']/descendant-or-self::*"/>
> 4 <its:translateRule its:translate="no"
> its:selector="//*[@trans='false']/descendant-or-self::*"/>
> </its:documentRules>

My understanding is (was) that when we apply the its:selector expression of a rule, it selects a node, and from that node we apply
the data category information to the same scope described for the equivalent locale rule.

In http://lists.w3.org/Archives/Public/public-i18n-its/2006JanMar/0290.html you said:

> ...In my XQuery implementation, XPath expressions like "//text[@localize='no']"
> are interpreted as "//text[@localize='no']/descendant-or-self::*".

To me that means its:selector="//code" is really its:selector="//code/descendant-or-self::*", so why would we need to specify it?

Received on Monday, 27 March 2006 04:53:24 UTC

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