- From: Felix Sasaki <fsasaki@w3.org>
- Date: Thu, 16 May 2013 07:11:39 +0200
- To: Karl Fritsche <karl.fritsche@cocomore.com>
- CC: Yves Savourel <ysavourel@enlaso.com>, 'Silvia Pfeiffer' <silviapfeiffer1@gmail.com>, 'Pēteris Ņikiforovs' <peteris.nikiforovs@tilde.lv>, public-multilingualweb-lt@w3.org, 'Mārcis Pinnis' <marcis.pinnis@tilde.lv>, public-html@w3.org
Am 15.05.13 17:35, schrieb Karl Fritsche: > On 15.05.2013 17:10, Yves Savourel wrote: >>> I meant to say: ignore, i.e. "within-text=nested" for <script> and >>> the text within <script> doesn't even get classified as translatable >>> text, since it's code and not text to be translated. >> I think Silvia has a good point about "within-text=nested". >> >> so maybe: >> >> [[ >> The default is "within-text=yes" all elements in phrasing content >> (http://www.w3.org/TR/html51/dom.html#phrasing-content-1), except for >> the <script> element which is "within-text=nested" independent of its >> position. >> ]] >> >> -ys >> >> >> > After looking over the Phrasing elements again, I think there should > be also other elements with nested, like code, iframe, noscript. I wouldn't specify a default for "code" since it can be both withn-text=nested or within-text=yes, the latter e.g. in <p>the <code>return</code> key ...</p>. The defaults are only for cases with no ambiguity. > Not sure how to handle most of the Interactive contents (3.2.5.1.7), > like button, select, keygen, ... Then better let's define no defaults for these, and encourage users to set within-text explicitly - which is the way to go anyway imo. Best, Felix > > Cheers > Karl > >
Received on Thursday, 16 May 2013 05:12:11 UTC