W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > February 2013

Re: mismatch of html translate and ITS translate

From: Felix Sasaki <fsasaki@w3.org>
Date: Fri, 22 Feb 2013 10:50:50 +0100
Message-ID: <51273F7A.5010005@w3.org>
To: Karl Fritsche <karl.fritsche@cocomore.com>
CC: public-multilingualweb-lt@w3.org, www-international <www-international@w3.org>
Am 22.02.13 10:48, schrieb Karl Fritsche:
> Hi all,
>
> On 22.02.2013 10:33, Felix Sasaki wrote:
>> Hi Karl,
>>
>> one process thing: please keep the www-international list in the 
>> loop, since the i18n guys will need to look into the issue too. One 
>> comment below.
>>
>> Am 22.02.13 10:27, schrieb Karl Fritsche:
>>> On 22.02.2013 10:16, Jirka Kosek wrote:
>>>> On 22.2.2013 6:55, Felix Sasaki wrote:
>>>>
>>>>> What would your preference be for resolving this:
>>>>> - asking HTML5 to change its semantics
>>>> I think that HTML5 spec should be changed and attributes should be
>>>> removed from translation. Or as a compromise only title and alt
>>>> attributes should be considered as translateable.
>>>>
>>>>             Jirka
>>>>
>>> The Problem in HTML5 is, you don't have any option to allow 
>>> translation of attributes.
>>
>> But where do you need this, except title and alt?
>>
>>> We can use rules, but this doesn't exists in HTML5. Thats why they 
>>> using this behavior, I think.
>>
>> Actually implementations don't use this - I checked the online MT 
>> translation systems that do HTML translation, and they don't 
>> translate attributes.
>>
>>> And to say some attributes are considered to be translatable and 
>>> others not, would be very confusing. Specially what are you doing 
>>> with data-* attributes - are they are translatable or not? Thats why 
>>> I think they considered everything as translatable and the 
>>> translation software should handle this. 
>>
>> So you are saying we should disalign ITS XML "translate" versus HTML 
>> "translate"? What will happen then for workflows like with 
>> Linguaserve, who do XML processing of XHTML files as part of their 
>> workflow chain?
>
> No, we should definitely find a solution, which in the best case is 
> the same for ITS and HTML. Only wanted to clarify, that maybe somebody 
> want also translate his data-* attribute, but in HTML5 you can't 
> specify, which attribute should be translated and which not.

Ah, I see - sorry for not reading carefully.

I'd say that this is something which when just doesn't work for HTML - 
people have to use global rules for that. But we should people make 
aware of the limitation.

Best,

Felix

>
> Best,
> Karl
>
>>
>> Best,
>>
>> Felix
>>>
>>>
>>
>>
>
>
> -- 
> *Karl Fritsche*, Junior Software Developer
> Tel.: +49 69 972 69 2604; Mob.: +49 1520 206 30 93; Fax: +49 69 972 69 
> 199; Email: Karl.Fritsche@cocomore.com <mailto:karl.fritsche@cocomore.com>
> *Cocomore AG,* Gutleutstra├če 30, D-60329 Frankfurt
> Internet: http://www.cocomore.de <http://www.cocomore.de/> Facebook: 
> http://www.facebook.com/cocomore Google+: http://plus.cocomore.de 
> <http://plus.cocomore.de/>
> Cocomore is active member of the World Wide Web Consortium (W3C)
> Vorstand: Dr. Hans-Ulrich von Freyberg (Vors.), Dr. Jens Fricke, Marc 
> Kutschera, Vors. des Aufsichtsrates: Martin Velasco, Sitz: 
> Frankfurt/Main, Amtsgericht Frankfurt am Main, HRB 51114
Received on Friday, 22 February 2013 09:51:22 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 9 June 2013 00:25:08 UTC