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: Fri, 24 Mar 2006 23:46:31 +0900
Message-ID: <44240647.8040608@w3.org>
To: Yves Savourel <yves@opentag.com>
Cc: public-i18n-its@w3.org
Hi Yves, all,

Yves Savourel wrote:
> Hi Felix, all,
>> So how about just having "mapping" just on this level, 
>> i.e. of names:
>> <its:documentRules>
>>  <its:mapMarkup sourceAttribute="its:translate" 
>> targetAttribute="trans"/> 
>> <its:mapMarkup sourceElement="its:ruby"
>> targetElement="odf:ruby"/> ...
>> <its:translateRule .../>
>> </its:documentRules>
>> the <mapMarkup> element then would have a clearly 
>> separated purpose then the global rules: mapping of 
>> names of elements and attributes, to allow their 
>> usage with the identical semantics as local ITS markup.
> I don't think this solve our problem (at least not completely), again because the native markup that would correspond to the ITS
> markup is not necessarily the same, while its behavior is.
> For example instead of using something like <span trans='false'> or <span direction='ltr'> the native markup may use things like
> <notrans> or <ltr> which cannot be mapped that way. I think this requires an XPath expression just like the one in its:selector.
> It seems that the only difference between our current rules and the ones we need for solve the problem has to do with overwriting
> behavior.

I'd see two points: overriding and precedence order. I.e. the DITA folks
want to be able to use @dita:translate in exact the same way as

Of course <mapMarkup> does not solve all problems, but only the ones of
DITA. For the other ones, we need the "normal" global rules, and have to
say: for cases like trans='false' you are not able to use that markup in
the same way as ITS local markup.

Again the question is just if we need this functionality. If not, I'd be
fine to give up my proposal :)

Btw., XBL, to which Richard pointed me a while ago, does the same thing
as mapMarkup for SVG: elements from other namespaces can be used with
SVG semantics. That is: *only* elements, not XPath, to be able to
provide 100% reliable "mapping", see



> Cheers,
> -yves

Received on Friday, 24 March 2006 14:46:50 UTC

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