W3C home > Mailing lists > Public > public-html@w3.org > July 2008

RE: Translation control in HTML5

From: Justin James <j_james@mindspring.com>
Date: Thu, 31 Jul 2008 17:54:28 -0400
To: "'Julian Reschke'" <julian.reschke@gmx.de>, "'Chris Wilson'" <Chris.Wilson@microsoft.com>
Cc: <public-html@w3.org>, "'Chris Wendt'" <Chris.Wendt@microsoft.com>
Message-ID: <02ec01c8f358$01b6d4d0$05247e70$@com>

> -----Original Message-----
> From: public-html-request@w3.org [mailto:public-html-request@w3.org] On
> Behalf Of Julian Reschke
> Sent: Thursday, July 31, 2008 5:30 PM
> To: Chris Wilson
> Cc: public-html@w3.org; Chris Wendt
> Subject: Re: Translation control in HTML5
>
> That would work, but it may make pages with technical content very
> chatty. It probably would be good to attach that property implicitly to
> elements like <code>.

I think that *any* system that allows you to toggle a UA feature on a
per-tag basis runs the risk of being "chatty" in certain use cases. The
alternative is, as you suggest, to put the toggle in the CSS, which also has
the problem (as you also suggest) of putting content into the style sheet.

However, I do think that the toggle should be set to "do not translate" *by
default* for certain items: the aforementioned code, cite, abbr, kbr, and I
would also like to add, pre and blockquote, as well as any form-related
elements (input, textarea, etc.), and of course, any text-within-SVG if we
end up with a final version of "SVG embedded into HTML".

My stance has always been that occasional "chattiness" is not a problem.
It's just an "occupational hazard" from time to time. :)

J.Ja
Received on Thursday, 31 July 2008 21:55:38 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:56 UTC