RE: [ACTION-230] ITS 2.0 Test suite on github

Hi Pablo,

> I have a doubt regarding the output files, I noticed that for 
> instance using translate, when an element is not included 
> in the rules the output is like this:
> path=/html        its:translate="yes"
> If it’s not in the rules or is local the notation is like this:
> path=/html/body[1]/span[1]    translate="yes"               
> But in the example 4 (see file attached) there is the line
> path=/html/head[1]      translate="no"
> But according to the rules it should have been 
> path=/html/head[1]      its:translate="no"
> shouldn’t it? Is this a mistake? Or am missing something?

Fredrik noted that too. Yes, there is simply some inconsistancies in the way the translate infor is output it should be all its:translate or all translate.


> Besides in terms of inheritance and overriding I 
> have a couple of doubts too:
> ...
> In the example 4 attached, according to the rules
> <its:translateRule selector="//h:html" translate="no"/>
> <its:translateRule selector="//h:p" translate="yes"/>
> The local title element ends up not translatable
> /html/head[1]/title[1] translate="no" and the children
> “span” of “p” ends up translatable.
> But in example 3, the rules
> <its:translateRule selector="//h:*" translate="no"/>
> <its:translateRule selector="//h:p" translate="yes"/> 
> shouldn’t have the same effect?
> The output file says that the children “span” of “p” 
> ends up not translatable, is that correct?

Yes, it looks correct (just looking at your description above)
The difference is that in example 4 the span elements are never selected, only h:html and h:p are, so the h:span elements inherits from the parent h:p.
In the example 3 the //h:* selector applies translate='no' to the h:span elements. Their parent h:p are then set to translate='yes', but nothing overwrites the first rule, so the children h:span are still set as translate='no'

Hope this helps,
-yves

Received on Tuesday, 23 October 2012 11:41:10 UTC