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

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

From: Yves Savourel <yves@opentag.com>
Date: Fri, 24 Mar 2006 06:30:15 -0700
To: <public-i18n-its@w3.org>
Message-ID: <003901c64f47$16c6fdd0$0300a8c0@Breizh>

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.

Cheers,
-yves
Received on Friday, 24 March 2006 13:30:30 UTC

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