- From: Dr. David Filip <David.Filip@ul.ie>
- Date: Fri, 22 Feb 2013 09:12:11 +0000
- To: Felix Sasaki <fsasaki@w3.org>
- Cc: Yves Savourel <ysavourel@enlaso.com>, www-international <www-international@w3.org>, public-multilingualweb-lt@w3.org
Felix, >> >> So, if I got it right: <p translate='yes' class='text'>content<p> applies >> to both "content" and "yes" as well as "text". >> >> First this doesn't match the ITS translate semantics where we exclude the >> attributes, and second, it's obviously not useable as both translate and >> class are not meant to be translated. If this is a correct interpretation, the resulting behavior is so stupid that it cannot be meant IMHO, so my preferred solution would be to ask HTML WG for clarification, eventually for change if this interpretation is confirmed.. >> >> Note that in the current specification we don't explicitely say that HTML >> translate must be used in stead of its:translate, but we give an example >> (http://www.w3.org/TR/2012/WD-its20-20121206/#translatability-implementation) >> and hints at the use of the HTML version here in the first paragraph of this >> section: http://www.w3.org/TR/2012/WD-its20-20121206/#html5-markup >> >> I think we really need to get our mapping between ITS and HTML clear and >> consistent. There is the open issue 97 for this >> (https://www.w3.org/International/multilingualweb/lt/track/issues/97) but >> now I'm not sure we can map HTML translate with ITS translate. + 1 for explicit mapping > > > What would your preference be for resolving this: > - asking HTML5 to change its semantics See above.. Cheers dF
Received on Friday, 22 February 2013 09:13:28 UTC