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

> 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 @its:translate.
>
> 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.

I don't think we can say that. We must find a way to support the <notrans> or trans='false' cases. And I'm guessing that that
solution (whatever it will be) will be applicable to solve both dita:translate and <notrans>. I'd rather see both aspects resolved
with a single solution, if it's possible.

At least we have reach one conclusion for now: something like <mapMarkup> can't be that solution.

Cheers,
-yves

Received on Friday, 24 March 2006 16:50:33 UTC