W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > May 2013

Re: Question on "phrasing content" definition

From: Karl Fritsche <karl.fritsche@cocomore.com>
Date: Wed, 15 May 2013 17:35:46 +0200
Message-ID: <5193AB52.5020100@cocomore.com>
To: Yves Savourel <ysavourel@enlaso.com>
CC: 'Silvia Pfeiffer' <silviapfeiffer1@gmail.com>, 'Felix Sasaki' <fsasaki@w3.org>, 'Pēteris Ņikiforovs' <peteris.nikiforovs@tilde.lv>, <public-multilingualweb-lt@w3.org>, 'Mārcis Pinnis' <marcis.pinnis@tilde.lv>, <public-html@w3.org>
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. Not sure 
how to handle most of the Interactive contents (, like button, 
select, keygen, ...

Received on Wednesday, 15 May 2013 15:36:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:32:09 UTC