This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Comment from MemoQ developers: Issue #3: "I wasn't able to find anything in ITS related to the translatability of attributes - ITS only seems to deal with tags which may limit its scope." Comment from Yves: "I was puzzled the comment at first, but after looking at the specification again, I noticed that we don't seem to have any example of dealing with attributes in that document anymore (some examples were in the modularization section, but it's now gone to the best practices). The example #4 shows a case with sometimes translatable attribute, but it's just an example of issue, not solution." Comment from Sebastian: "agreed, it needs a couple of examples. But also making it ever clearer that translatable text in attributes is a Bad Thing."
A to answer formally to the issue: We do need to add examples for attributes and translatability (and makes sure it also mention the drawbacks coming with translatable attributes). By default, ITS conciders attributes to be *not translatable*. But, if needed, you can specify that some are using a simple <translateRule>, the selector attribute has simply to point to attributes. For example: <its:translateRule selector="/@alt|//@title" translate="yes"/> declares any alt and title attributes to be translatable. A real example with such cases is in the ITS example for XHTML here: <http://www.w3.org/TR/xml-i18n-bp/#relating-its-plus-xhtml>
Added István to the CC list.
To clarify the aspect of attribute translatablity as well as inheritance, I would propose to make the following changes to the section 2.6 (http://www.w3.org/TR/its/#translate) - Current text: [[The data category translatability expresses information about whether the content of an element or attribute should be translated or not. The values of this data category are "yes" (translatable) or "no" (not translatable).]] - Proposed text: [[The data category translatability expresses information about whether the content of an element or attribute should be translated or not. The values of this data category are "yes" (translatable) or "no" (not translatable). By default, element content is translatable, and attribute values are not translatable.]] --- - Current text: [[As for global rules, translatability is expressed with a translateRule element with a translate attribute. The attribute has the values "yes" or "no". In addition, a selector attribute is required. Example 20: Translatability expressed globally <its:rules its:version="1.0"> <its:translateRule translate="yes" selector="//p"/> <!-- All p elements should be translated--> </its:rules>]] - Proposed text: [[Globally, translatability is expressed with a translateRule element. A required selector attribute indicates to what part of the document the rule applies, and a required translate attribute indicates whether the selection is translatable or not. The selection is the textual content of the element, including child elements, but excluding attributes." Example 20: Translatability expressed globally <its:rules its:version="1.0"> <!-- All alt attribute are translatable --> <its:translateRule selector="//*/@alt" translate="yes" /> <!-- All del elements are not translatable --> <its:translateRule selector="//del" translate="no" /> <!-- All alt attributes inside a del element are not translatable --> <its:translateRule selector="//h:del/descendant-or-self::*/@*" translate="no"/> </its:rules>]] --- - Current text: [[Locally, translatability is expressed with a translate attribute with the values "yes" or "no" The selection is the textual content of the element, including child elements, but excluding attributes.]] - Proposed text: [[Locally, translatability is expressed with a translate attribute with the values "yes" or "no" The selection is the textual content of the element, including child elements, but excluding attributes. It is not possible to override the translatability of attributes using local markup. This limitation is consistent with the adviced practice of not using translatable attributes.]] (with "adviced practice" linked to the Best Practices document).
I agree with the proposal from Yves made at http://www.w3.org/Bugs/Public/show_bug.cgi?id=3362#c3 and would propose it as a solution to the commentor if the group agrees.
(In reply to comment #4) > I agree with the proposal from Yves made at > http://www.w3.org/Bugs/Public/show_bug.cgi?id=3362#c3 and would propose it as a > solution to the commentor if the group agrees. > I also agree with Yves's solution, it clarifies things.
This is an reply from the ITS Working Group. You already agreed to our proposal at http://www.w3.org/Bugs/Public/show_bug.cgi?id=3362#c5 . If we don't hear anything else from you within 2 weeks, we will regard this issue as closed. Regards, Felix.
Action: working group to discuss and reply.
Wait: answer sent, wait respone.
Closed. No answer after 2 weeks.