- From: Yves Savourel <ysavourel@translate.com>
- Date: Thu, 11 Oct 2007 08:22:06 -0600
- To: <public-i18n-its@w3.org>
Hi Richard,
I'm worried about the edit changes to 'translate flag' in BP5.
(http://www.w3.org/International/its/techniques/its-techniques.html#DevTransOver)
One does not override 'flags' but rules. To me the idea of 'flags' is associated to making something, in XML, most likely with an
attribute. But this BP is about overriding rules. If anything here we use 'flags' to override rules and defaults.
I know this is about not using 'translatability'. But to me using 'translate flag' is worst than 'translatability'. 'Translate
information' maybe, ut does not sound good either.
And (unrelated to above) one questions for XPath experts:
In Example 6 we have:
<its:translateRule selector="//*[lang('zxx')] | //@*[lang('zxx')]" translate="no"/>
Is //@*[lang('zxx')] really useful? Since the attributes have the same language as the elements were they are, such case should be
caught by //*[lang('zxx')] already, no?
-ys
Received on Thursday, 11 October 2007 14:21:54 UTC