We may be faced with a slightly different situation, where the schema already has an attribute that indicates that content should not be translated, but that uses its own attributes or elements to express that. It is not obvious to a processor that the change attribute in the example above fulfills the same role as our its:translate attribute. Using global rules, however, we can associate that attribute with the translate data category.

The markup at the top of the slide shows how you could do this. It selects all elements in the document with a change attribute with the value set to false, and using the translate attribute in the rule, asserts that this is equivalent to its:translate="no". There is then a similar declaration for change="true".

This can be useful for describing legacy content so that a translation process can understand what text to lock for translation.