- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Wed, 15 May 2013 09:10:36 -0600
- To: "'Robin Berjon'" <robin@w3.org>, "'Silvia Pfeiffer'" <silviapfeiffer1@gmail.com>
- CC: "'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>
> Well, depending on how the script is written it might contain > strings that need translation. That's not a happy design by any metric, > but it's probably something that needs to be handled. > In other words, I don't think that it can be treated like any > other element. It needs a class of its own that can convey the information that > it may require some form of specialized translation. > I'm not familiar enough with ITS to know if this can be expressed or not. ITS has only one way to indicate that something is 'translatable'. But there is no prescribed way on what tasks to perform on those nodes. I think it would probably be ok to have simply some note associated with the attributes or elements that request a secondary parsing. Something similar to the comment here: https://www.w3.org/Bugs/Public/show_bug.cgi?id=21495#c1 >From the ITS viewpoint the translate property would be applied correctly regardless if the element is <script>, <style> or <p>. And the application that uses the ITS information could apply different behavior to perform the actual 'translation', guided by the informative distinction made in the HTML specification between content/values that are text and the ones that need a secondary process to access the text parts. -ys
Received on Wednesday, 15 May 2013 15:11:30 UTC