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


--- Comment #30 from Felix Sasaki <felix.sasaki@dfki.de> 2011-07-28 20:26:40 UTC ---
(In reply to comment #16)
> 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)

The above are providers of online machine translation systems. I am currently
preparing a project with two companies (one localization, one  mt provider) who
want the implement the same functionality as a standard means.

So these are then three online MT system, and one is cooperating with a
localization provider. But a standardized mechanism can be relevant for many
other "participants" on the web, and also in the "deep Web": CMS providers who
produce the necessary information in their templates, which is then processed
in MT systems or localization chains; and in larger companies  with often quite
complex content delivery chains (see what Helena mentioned), which result on
surface web html pages.

It is not important to use the ITS translate mechanism. But it is important to
have a mechanism that can be separated from others, and that can be easily
shared among all these groups.

And I would call these also content providers.

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 Thursday, 28 July 2011 20:26:43 UTC