- From: Felix Sasaki <fsasaki@w3.org>
- Date: Thu, 02 May 2013 06:47:27 +0200
- To: "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>
Hi all, As we discussed, bringing HTML "translate" into ITS 2.0 is not about defaults like with "elements within text", "id value" or "language information". It's rather about the interaction between elements and attributes defined within HTML5.x, see e.g. http://www.w3.org/html/wg/drafts/html/master/dom.html#the-translate-attribute "When an element is in the translate-enabled state, the element's translatable* attributes and the values of its Text node children are to be translated when the page is localized." * points to the list of translatable attributes. If we would adopt such an interaction (or just refer to above definition), what would that mean for global rules and inheritance? Suppose I have <p> ... <img alt="..."/>...</p> and this translate rule <its:translateRule selector="//h:p" translate=yes"/> or just locally <p translate="yes"> ... <img alt="..."/>...</p> would both the "img" element and "img", including "alt" be translatable? Above definition talks about translatable elements like this "When an element is in the translate-enabled state, the element's translatable attributes and the values of its Text node children are to be translated when the page is localized." This means no inheritance to elements, but only application to text nodes. Best, Felix
Received on Thursday, 2 May 2013 04:48:20 UTC