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

Action Item: rework 4.1 and 4.1.1 (cf. http://www.w3.org/2007/05/15-i18nits-minutes.html#action11)

From: Lieske, Christian <christian.lieske@sap.com>
Date: Wed, 30 May 2007 16:16:54 +0200
Message-ID: <544FBEB6875DAA46A08323B58D26B801018F860E@dewdfe14.wdf.sap.corp>
To: <public-i18n-its@w3.org>
Dear all,

I worked on my action item related to the BP (cf.
 <http://www.w3.org/2007/05/15-i18nits-minutes.html#action11>
http://www.w3.org/2007/05/15-i18nits-minutes.html#action11).
 
Please note: I included some ideas for additional content. They are prefixed
by <NEW>.
 
Cheers,
Christian

== old ==
4 Generic Techniques
 
This section provides a set of generic techniques that are applicable to
various guidelines, for example, how to add ITS attributes or elements to
different types of schemas.
== new ==
4 Generic Knowledge
 
While addressing internationalization-related issues with ITS or the Best
Practices described in this document,  
generic knowledge such as optimized XPath expressions is helpful. This
section covers this generic knowledge.
 
== old ==
4.1 Writing ITS Rules
 
Whether they are external or embedded, there are a few things you should
take in consideration when writing ITS rules.
 
Note: Try to keep the number of nodes to be overriden to a minimum for
better performances. For example, If most of a document should not be
translated, it is better to set the root element to be non-translatable than
to set all elements. The inheritance mechanism will have the same effect for
a much lower computing cost.
 

Note: Because a rule has precedence over the ones before, you want to start
with the most general rules first and progressively override them as needed.
Some rules may be more complex to take in account all the aspects of
inheritance.
== new ==
4.1 ITS Markup
 
There are a few things you should consider when creating ITS markup.
 
4.1.1 Create Rules in Good Time
 
<NEW> Create rules even you currently do not need it. Sooner or later,
someone will for example ask which elements really need to be translated.
ITS rules will in this case refresh your own memory, and will communicate
effectively the information that is needed.
 
4.1.2 Consider Your Processing Environment
 
<NEW> Be sensitive against your processing environment. It does for example
not make much sense to write ITS with global selection if your processor
cannot cope with it.
 
4.1.3 Take Advantage of Default and Inheritance.
 
Two ITS provisions help to keep ITS markup to a minimum: defaults and
inheritance. Since, for example, the ITS default for elements is "translate"
this does not need to be coded explicitly. In a similar vein, since ITS
inheritance for many data categories passes information from higher-level
nodes to lower-level nodes, you only need to provide ITS markup for
higher-level nodes.
 
For example, if most of a document should not be translated, it is better to
set the root element to be non-translatable than to set all elements.
 
<TODO>Include example
 
Note: Keeping the number of nodes to be overriden to a minimum increases
performance. 
 
The precedence defined for rules elements needs to be taken into account: If
identical selections are defined in different rules elements within one
document, the selection defined by the last takes precedence. Thus, you may
want to start with the most general rules first and progressively override
them as needed.
 
4.1.4 Create your XPath Expressions with Care
 
<TODO>
 

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
 <blocked::mailto:christian.lieske@sap.com> christian.lieske@sap.com
 <blocked::http://www.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 Wednesday, 30 May 2007 14:17:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:49 GMT