Re: Refinement for the translate data-category?

> Am 03.07.2015 um 19:25 schrieb Richard Ishida <ishida@w3.org>:
> 
> 
> one of the Russian participants in the W3Cx HTML5 course asked an interesting question:
> 
> ===
> The question is what do you expect to happen to "Michel Ham" when translating to non latin. Do you want it to stay in latin? You are making it unreadable to someone who can't read latin script. Google Translate keeps it in latin with translate=no.
> ===
> 
> Suppose you have the text:
> 
> <p>Welcome to <span translate="no">Michel Ham</span>!</p>
> 
> where the name has translate=no to avoid it becoming, say, Michel Jambon in French.
> 
> the result of running it through a translation service would then be:
> 
> Добро пожаловать Michel Ham .
> 
> Russian translations generally transliterate things like names, just as we would transliterate Russian names into Latin script.  Currently the translate data category and the translate attribute in HTML5 block that process, and cause the name to remain in the original script.
> 
> Perhaps we need another value than yes|no, such as translitOk?

This would break a lot of tools that use only translate yes or no. Transliteration information should be conveyed by a different field.

- Felix 

> 
> what do you think?
> ri

Received on Sunday, 5 July 2015 06:24:46 UTC