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

Re: Question on "phrasing content" definition

From: Robin Berjon <robin@w3.org>
Date: Wed, 15 May 2013 12:07:18 +0200
Message-ID: <51935E56.2010508@w3.org>
To: 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" <public-html@w3.org>
On 15/05/2013 11:07 , Silvia Pfeiffer 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.

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 
specialised translation. I'm not familiar enough with ITS to know if 
this can be expressed or not.

In fact, completely irrespective of where it occurs in the document, 
script may or may not require translation. And I can't think of a useful 
default that would work well. Note that it's very common to have scripts 
at the end of the body for performance reasons.

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Wednesday, 15 May 2013 10:07:32 UTC

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