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 01:15:00 +0000
To: public-i18n-core@w3.org
Message-Id: <E1RYSZg-0005vn-Op@jessica.w3.org>

Martin Dürst <duerst@it.aoyama.ac.jp> changed:

           What    |Removed                     |Added
                 CC|                            |duerst@it.aoyama.ac.jp

--- Comment #57 from Martin Dürst <duerst@it.aoyama.ac.jp> 2011-12-08 01:14:58 UTC ---
(In reply to comment #55)
> (In reply to comment #53)
> > 
> > An example at the page level would be to allow the author to specify that the
> > whole page should not be translated expect for some paragraphs.
> Can you give an example of this? (Just trying to understand the use case here
> to be properly informed when addressing this.)

I agree it may be more difficult to find cases where "don't translate" applies
to a full page. But Yves (comment #56) gave a good example.

Even if we didn't find such a good example currently, would that mean that we
should not allow the attribute (or whatever) on the <html> element? In my view,
that would be a bad idea. Even if it gets used very rarely, it's much easier
for users, for implementers, and for spec writers and readers,... if the
attribute is just allowed everywhere. Then if an use case comes up later,
nobody has to wonder "why is this allowed everywhere but not here".

Of course if you had something different in mind when asking for such specific
use cases, then the above reasoning might not apply, but then it would be very
helpful to know what you had in mind.

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 01:15:26 UTC

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