- From: Felix Sasaki <fsasaki@w3.org>
- Date: Tue, 24 Jan 2006 12:26:58 +0900
- To: "Yves Savourel" <ysavourel@translate.com>, public-i18n-its@w3.org
On Tue, 24 Jan 2006 08:34:43 +0900, Yves Savourel <ysavourel@translate.com> wrote: > > Just some thoughts about inheritance: > > The current specification does not describe precisely how in situ values > are inherited, especially for attribute. Is it working > exactly the same way as xml:lang or differently?: I would say as xml:lang : "The intent declared with xml:lang is considered to apply to all attributes and content of the element where it is specified, unless overridden with an instance of xml:lang on another element within that content." That is, > > Example 1: > > <p its:translate="yes" alt="text">text <img alt="text"/> text</p> > > This makes translatable the content of <p> but the values for both alt > atr strill not transltable, right? no, the attributes would be translatable as well, if we follow xml:lang > > > Example 1: > > <p its:translate="yes" translateSelector="@alt" alt="text">text <img > alt="text"/> text</p> > > This makes the alt attribut of <p> translatable, but not the values of > the alt attribute in <img>, right? yes. There is another issue with inheritance: - its:translate="yes" - in situ - is overridden by its:translate="no" - in situ at a child element. - what should happen with e.g. its:Locinfo, e.g. <p its:locInfo="info no 1">text <img its:locInfo="info no2"> alt="text"/> text</p> As for the <img> element, does both "info no 1" and "info no 2" apply, or only one of these? I guess the general question is: how to handle inheritance if we don't have *alternative* values, that is s.t. different from its:translate, its:dir etc. Cheers, Felix
Received on Tuesday, 24 January 2006 03:27:04 UTC