- From: Lieske, Christian <christian.lieske@sap.com>
- Date: Mon, 13 Aug 2007 14:35:59 +0200
- To: <public-i18n-its@w3.org>
- Message-ID: <544FBEB6875DAA46A08323B58D26B80102133090@dewdfe14.wdf.sap.corp>
Dear all, I had an action item (see http://lists.w3.org/Archives/Public/public-i18n-its/2007JulSep/0022.html) to rework the "Why do this" part of BP 9. Please find my suggestion below. A look at BP 1 furthermore suggested some changes to the BP name and the "blue" text. Please find my suggestions (starting with New> below as well. In addition, I was under the impression that some notes for the "How do this" part might be helpful as well. Please find my suggestions (starting with New> below as well. Best regards, Christian === Best Practice 9: Provide xml:id specify unique identifiers New>Allow localizable elements to be annotated with unique identifiers Provide a way to assign a unique identifier to localizable elements. New>Include xml:id in your DTD or schema to allow localizable elements to be annotated with unique identifiers. How to do this Make sure the attribute xml:id, or a different attribute of type ID, is available, at least, the "paragraph" level, for the elements that contain translatable text. NEW>Make sure an attribute which represents a unique identifier is available at least for all elements that may contain translatable text. NEW> NEW>Note: It is highly recommended to name the ID attributes "xml:id", and follow the rules put forth in [http://www.w3.org/TR/xml-id]. This increases the interoperability of these identifiers on the Web, and helps to make XML sub-resource linking robust. NEW> NEW>Note: Internal or external declarations in DTDs or XSDs may assist in declaring and checking the unique identifiers. NEW> NEW>Note: Attention should be paid to the lexical forms and attribute value normalizations described in [http://www.w3.org/TR/xml-id]. NEW> NEW>Note: Provisions for using a globally unique or even persistent identifiers (i.e. ones which do not change over) often provide additional benefits. Why do this The reuse of translations during updates is facilitated if changed or unchanged items can be easily identified. Identifiers allow translation tools to correctly track an item between versions or locations. Items which have been deemed to be the same in terms of identity can be examined for content changes. If no change has taken place, the potential for reuse of the previous translation is very high. Change analysis constitutes an extremely powerful productivity tool for translation when compared to the typical source matching techniques (a.k.a. translation memory). These techniques simply look for similar source text in a multilingual database without, most of the time, being able to tell whether the context of its use is the same. Identifiers also help to trace texts to their uses. If for example a User Interface (UI) string has to be corrected, then a unique identifier which is ease to access from the UI will enable efficient correction in the underlying source (e.g. a resource file). === Christian Lieske MultiLingual Technology Solutions (MLT) SAP Language Services (SLS) SAP Globalization Services SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf Germany T +49 (62 27) 7 - 6 13 03 F +49 (62 27) 7 – 2 54 18 christian.lieske@sap.com http://www.sap.com Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Léo Apotheker (stellvertretender Sprecher/Deputy CEO), Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
Received on Monday, 13 August 2007 12:36:15 UTC