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

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

--- Comment #16 from Karl Dubost <karl+w3c@la-grange.net> 2011-07-27 12:32:38 UTC ---
Hello Felix :)

(In reply to comment #13)
> Hi Karl,
> > > 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

It was said "several content providers". In Richard answers, I see two:

* Microsoft
* Google

are there others and if yes how, what do they do, etc? 
(just trying to have a better overview of the extent of things)

> > 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?

We have often a tendency to focus on the solution we have already imagined.
It's normal. no blame on that. But sometimes there is more than one opportunity
to solve an issue. Sometimes more practical/less costly ones emerge in the
discussion.

For example, I had not realized for the "code" element (not relying on the
attribute), it is quite cool.


> <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).

thanks a lot. Clearer.

-- 
Configure bugmail: http://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 Wednesday, 27 July 2011 12:32:40 UTC