RE: ITS 2.0 sec1-2 editing current state

Just one note on

"The Translate data category has a direct counterpart in [HTML5], namely the HTML5 translate attribute. ITS 2.0 does not define its
own behaviour for HTML5 translate, but just refers to the HTML5 definition."

(BYW it should be the US spelling "behavior" not "behavior")

Sorry to bring it back... but:

The HTML5 definition of translate does not talk about global rules obviously.
So what is a developer is to do for global Translate rules in HTML5? Does it applies the property applies to the attributes of the
selected nodes too (unlike XML?). I assume so, but it's not written anywhere in either of the specifications.

Note also that we have a note in the Translate section
( that says:

"It is not possible to override the Translate data category settings of attributes using local markup. This limitation is consistent
with the advised practice of not using translatable attributes. If attributes need to be translatable (e.g., an HTML alt attribute),
then this must be declared globally."

I don't think the note is completely applicable for HTML5: if you apply the HTML5 behavior you do override the Translate setting of
attributes using local markup. The alt example is a good example of that. At the same time it's true that you cannot define an
override on *only* an attribute using local markup (even in HTML5).


-----Original Message-----
From: Felix Sasaki [] 
Sent: Thursday, May 30, 2013 11:40 AM
Subject: ITS 2.0 sec1-2 editing current state

Hi all,

I did some editing in sec 1.4 and discussed during the editing call with Dave. See the outcome here

except "1.4.4 Additional or modified mechanisms" and "1.4.7 Extended implementation hints"
sec. 1.4 has all content we discussed yesterday

Any comments? Next call would be Monday 13 UTC
for 1 hour.



Received on Thursday, 30 May 2013 19:20:00 UTC