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

Re: Directionality Scope/inheritence issue (same as translatability)

From: Felix Sasaki <fsasaki@w3.org>
Date: Thu, 23 Mar 2006 10:09:13 +0900
Message-ID: <4421F539.8000708@w3.org>
To: Yves Savourel <ysavourel@translate.com>
Cc: public-i18n-its@w3.org
Hi Yves,

Yves Savourel wrote:
> Hi Felix,
> 
> 
>> In addition to the problems you mentioned in your mails 
>> about directionality and translatability, there is another 
>> one: the global rules don't take the default selections in 
>> the instance into account.
> 
> I'm not sure if I understand the paragraph above. What are the "default selections in the instance"?
> 
> I'm guessing it would (for translatability for example): "element content is translatable, attribute values are not". But the global
> rules take that into account... (so I probably don't understand).

at http://www.w3.org/TR/its/#selection-defaults-etc , we define
"default" selections. I think for translatability this means if the have
<p its:translate="..">...</p>
the value of the translate attribute is related to "Textual content of
element, including content of child elements, but excluding attributes",
no matter what the value is.

for directionality it means if we have
<p its:dir="rtl">..</p>
it means "Textual content of element, including attributes and child
elements"

Now, a global rule like
<its:dirRule select="//p" its:dir="rtl"/>
selects only the <p> elements, not their attributes. The same is true
for a global rule like
<its:translateRule select="//p" its:translate="..."/>
this rule does not say "attributes are not translatable": it just does
not talk about attributes.


the problem with the global rules which select s.t like
"//p[trans='yes']" is that you have to add all kinds of "implicit"
interpretations of XPath, to achieve the interpretation at
http://www.w3.org/TR/its/#selection-defaults-etc . The other problem is
inheritance, which you mentioned before.

The third problem is that people probably want to be able to use e.g.
@trans attributes like local its:translate attributes: to describe
translatability for some specific cases. The global cases should be
described with normal global rules, e.g. as you did for XHTML. However,
if we use global rules for interpreting @trans, @trans will have the
same precedence position as other global rules. I guess user want it in
the precedence position of its:translate (which would be possible with a
pre-processing step which transforms @trans to its:translate).

However, my impression was if we have in the XML document s.t. like
<p trans="..">...</p>
we want to be able to say "trans has the same meaning like *local*
translatability", that is, like
<p its:translate="...">...</p>

I am not sure yet about the syntax for s.t. like that. Maybe
<its:translateRule its:translate="yes" realized-as="//@trans['yes']"/>

or for directionality
<its:translateRule its:dir="rtl" realized-as="//@dir['rtl']"/>

Does this make sense?

- Felix

> 
> Can you elaborate?
> 
> Thanks
> -yves
> 
> 



Received on Thursday, 23 March 2006 01:09:26 UTC

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