W3C home > Mailing lists > Public > public-i18n-core@w3.org > October to December 2011

[Bug 12417] HTML5 is missing attribute for specifying translatability of content

From: <bugzilla@jessica.w3.org>
Date: Thu, 08 Dec 2011 10:33:49 +0000
To: public-i18n-core@w3.org
Message-Id: <E1RYbIT-0004hl-Fu@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12417

--- Comment #62 from Jirka Kosek <jirka@kosek.cz> 2011-12-08 10:33:47 UTC ---
(In reply to comment #61)
> (In reply to comment #60)
> 
> To clarify my previous remark: If a website is translated from say English into
> Spanish, the resulting page should not be translated again. That is: if a
> machine translation application comes to the Spanish page, the translate="no"
> will instruct the processor not to translate this page. The application will
> then have to decide on what to do next, for example ask the user to ignore this
> instruction or just show the website as it is. In many of these cases the user
> will see a language selection on top of these pages (such as flags, etc.),
> indicating that a version of the page in the desired language is already
> available. Hence the instruction translate="no" complements the xml:lang="es"
> in the said example. 

I think that this example is not good use of translate=yes/no. In this case
there is no reason to forbid translation of Spanish page. But there should be
more complex metadata attached saying that this is not primary version of page
and that English original is available somewhere else. But this would be
different feature and hence separate bug should be opened.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 8 December 2011 10:33:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:23:07 UTC