- From: Felix Sasaki <fsasaki@w3.org>
- Date: Mon, 4 Dec 2006 08:15:33 +0900 (JST)
- To: "Yves Savourel" <yves@opentag.com>
- Cc: public-i18n-its@w3.org
Hi Yves (moving this to the public list, let's have technical discussions here ;) ), > > Hi Sebastian, > >>> ... >>> Am I correct to assume that the content of <code> should end up to be >>> translatable? (because the local translate='yes' in <par> is inherited >>> and overrides the global translate='no' for <code>). >>> >> No, I disagree. If it was true, a "translate='yes'" on the root of the >> document would prevent any "no" rule from firing. The explicit rule >> for code must override the inherited value. > > But the inherited value comes from a local rule, which has precedence over > global rules. actually http://www.w3.org/TR/2006/WD-its-20060518/#selection-precedence is not clear about this: [[1. Implicit local selection in documents (ITS local attributes on a specific element) 2. Global selections in documents (using a rules element) 3. Global selections in an external file (using a rules element), linked via the XLink href attribute or a different mechanism 4. Selections via defaults for data categories, see Section 6.1: Position and Default Selections of Data Categories]] this list does not talk about inherited values. > > So it seems logical that any global translate rule on <code> should be > overriden by the local its:translate on its parent element. I would agree with Sebastian that this should not be the case. Take a look at CSS: a global rule like em { color: blue ; } is overridden by <em style ="color: blue;"> , but it is for the <em> element *not* overridden by a local rule like <p style ="color: blue;"> ...<em> ... > > >> ... If it was true, a "translate='yes'" on the root of the >> document would prevent any "no" rule from firing. > > That would be my expectation: a "translate='yes'" on the root of the > document would prevent any global "no" rule from firing. I would not expect that, see the CSS example above. Of course we don't need to do everything like CSS, but so far it seemed to be helpful. > > Maybe I'm not understanding the difference between inheritence and > override. We had a discussion on this before > <http://lists.w3.org/Archives/Public/public-i18n-its/2006JanMar/0290.html> > but I guess I'm still unclear. oh, that discussion ... I feel still sorry for that. I'll take CSS again to try to make that clearer: global rule: em { color: red; } div { color: green ; } <div> <p style ="color: blue;"> ...<em> ... the style property set globally via the rule for <div> is *inherited* to all children of <div>. It is *overridden* by the explicit rule for <p>, which when *inherits* to all children of <p>. This inheritance is *overriden* by the global rule for <em>. Cheers, Felix
Received on Sunday, 3 December 2006 23:15:42 UTC