W3C home > Mailing lists > Public > public-i18n-its@w3.org > July to September 2007

RE: Input to BP 9 http://www.w3.org/International/its/techniques/its-techniques.html#DevUniqueID

From: Yves Savourel <ysavourel@translate.com>
Date: Fri, 13 Jul 2007 14:30:26 -0600
To: "'Felix Sasaki'" <fsasaki@w3.org>, "'Lieske, Christian'" <christian.lieske@sap.com>
Cc: <public-i18n-its@w3.org>
Message-ID: <009201c7c58c$a53b2ac0$8d05a8c0@BREIZH>

>>> Quote>Provide a way to assign a unique identifier to translatable text.
>>
>> Should we really have the restriction "to translatable text"? I guess 
>> that for example having identifiers for XML elements which are related 
>> to graphics (eg. "img") would be beneficial from an i18n point of view 
>> as well - amongst others since you may want to leverage 
>> "translated/localized"
>> graphics as well.
>   
> agree.


So how about:

"Provide a way to assign a unique identifier to localizable elements" ?

or

"Provide a way to assign a unique identifier to localizable content" ?




>>> Quote> Make sure the attribute xml:id, or an equivalent attribute, is
>>> available, at least, the "paragraph" level, for the elements that 
>>> contain translatable text.
>>
>> I guess we need to clarify what the features of an "equivalent attribute"
>> are. Would we simply point to
>> http://www.w3.org/TR/2005/REC-xml-id-20050909/#validation-technologies?
>
> I would rather replace "or an equivalent attribute" with "or a different 
> attribute of type ID", to make the feature clear, that is "type ID" 
> attribute.

Felix rewording sound good to me.


Cheers,
-yves
Received on Friday, 13 July 2007 20:29:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:09 UTC