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 14:32:39 -0700
To: <public-i18n-its@w3.org>
Message-ID: <004601c6511c$cf0715c0$0300a8c0@Breizh>

Hi Sebastian,

> Yves, do you have a test file I can download 
> which demonstrates how the current rules fail?

Here is one example:

<code> is normally not translatable, <textInCode> is normally translatable, and trans='true|false' behaves like
its:translate="yes|no".

<myDoc>
 <head></head>
  <body>
   <p><code>code <textInCode>text in code <code>code in text</code></textInCode></code></p>
   <p trans="false">some text <code>code <textInCode>text in code</textInCode>code</code>.</p>
   <p><code trans="true">code <textInCode trans="false">text in code <code trans="true">code in text</code></textInCode></code></p>
   <p trans="false">some text <span trans='true'>text</span> text.</p>
   <p trans="true">some text <span trans='false'>text</span> text.</p>
 </body>
</myDoc>

And you are right: we should make sure first that we are all expecting the same output. For me I expected the text marked in Xs to
be seen as translatable by ITS:

<myDoc>
 <head></head>
  <body>
   <p><code>code <textInCode>XXXX XX XXXX <code>code in text</code></textInCode></code></p>
   <p trans="false">some text <code>code <textInCode>text in code</textInCode>code</code>.</p>
   <p><code trans="true">XXXX <textInCode trans="false">text in code <code trans="true">XXXX XX XXXX</code></textInCode></code></p>
   <p trans="false">some text <span trans='true'>XXXX</span> text.</p>
   <p trans="true">XXXX XXXX <span trans='false'>text</span> XXXX.</p>
 </body>
</myDoc>


-ys
Received on Sunday, 26 March 2006 21:32:53 UTC

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