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

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

From: Yves Savourel <yves@opentag.com>
Date: Sun, 26 Mar 2006 16:21:27 -0700
To: "'Sebastian Rahtz'" <Sebastian.Rahtz@oucs.ox.ac.uk>, "'Yves Savourel'" <yves@opentag.com>
Cc: <public-i18n-its@w3.org>
Message-ID: <000601c6512c$031b4ed0$0300a8c0@Breizh>

Hi Sebastian,

> Now (sorry, I am being slow here!), where do I worry 
> about ambiguity? the results are correct, yes?

In the second paragraph:

<p trans="false">some text <code>code <textInCode>text in code</textInCode>code</code>.</p>

The content of <textInCode> should be not translatable because trans='true' in the <p> element.

That is assuming trans='true|false' has the same behaviour as its:translate, (like a dita:translate).

In other words, we have cases of native markup like <code> and <textinCode> (case 1) that are not directly related to
translatability but need to be specified in our rules (simply because the nature of their content make them translatable or not),
and we have cases like trans='true|false' (case 2) that should mimic its:translate. The rules of case 2 should overwrite rules of
case 1, but sometimes rules of case 1 should not overwrite other rules of case 1 (for example when <code> can be within <textInCode>
and <textInCode> can be within ,code>) because re-ordering the rules can't work for them. 

...I think.

Received on Sunday, 26 March 2006 23:21:44 UTC

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