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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12417

--- Comment #13 from Felix Sasaki <felix.sasaki@dfki.de> 2011-07-27 11:18:30 UTC ---
Hi Karl,

(In reply to comment #12)
> (In reply to comment #9)
> > > Using class="notranslate" isn't an abuse as far as I can tell.
> > 
> > The class attribute is used for other things. Overloading it with "notranslate" is not a viable solution.
> 
> I think the question that hixie had, was does it answer the use cases?
> In which ways, what does it break, what does it improve? (with code scenarios)
> 
> > > This seems like a feature that would get only narrow use.
> > > Is it really worth adding to the language?
> > 
> > I disagree. Several content providers are using workaround because a standard
> > solution does not exist.
> 
> Is there a document with what the content providers are doing? 
> What code (workaround) are they using?

Richard described the workarounds here
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12417#c8

> How to solve it with code without focusing on  one possible solution?

Not sure what you mean by "without focusing on one possible solution" - could
you explain?

> 
> > > It seems like the ideal solution would be a new
> > > language subtag, frankly.
> > 
> > Using a subtag is not the solution either. It overloads the value with
> > information that has nothing to do with the language.
> 
> In which ways? Could you give more details. (code+explanation)

<p lang=en-us>...</p> identifies the content of "p" to be American English.
This identification is independent of an application like machine translation.
So if you change this e.g. to <p lang=en-us-trans>...</p>, other applications
that "understand" en-us will be confused. The issue behind this is that
applications like choice of fonts or spell checkers rely on language
*identification*, whereas "Translation" information is rather a directive for a
process - "translate me" (me, being a human translator, an MT system, or both).

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 27 July 2011 11:18:37 UTC