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

AW: On issue 3640 and action item http://www.w3.org/2006/09/20-i18nits-minutes.html#action12

From: Lieske, Christian <christian.lieske@sap.com>
Date: Mon, 25 Sep 2006 10:48:04 +0200
Message-ID: <544FBEB6875DAA46A08323B58D26B8011E79D2@dewdfe14.wdf.sap.corp>
To: <fsasaki@w3.org>, <public-i18n-its@w3.org>

Hi Felix,

Thanks for working on the action item. I suggest the following changes to your proposed wording.

Regards,
Christian

Orig>The following table summarizes the position of data categories, their default values, and their inheritance
Orig>and overriding behaviors.

Mod>The following table summarizes for each data category which selection, default value, and inheritance
Mod>and overriding behavior applies.

Orig>Default values are assumed if no ITS markup (global or local) is applicable to an element 
Orig>or attribute node in a document. 
Orig>For example, if there is no translateRule element and no translate element available, elements 
Orig>are translatable, and attributes are not translatable.

Mod>Default values apply if both local or global selection are absent.
Mod>The default value for the data category translate for example
Mod>mandates that elements are translatable, and attributes are not translatable
Mod>if there is no translateRule element and no translate attribute available. 

Orig>Inheritance describes whether ITS information is applicable to nested elements and attached attributes.
Orig>For example, the ITS information its:translate="yes" in
Orig><p its:translate="yes">We define <term its:term="yes"><emph>discoursal</emph> point of view</term> as ...</p>
Orig>means that all elements inside the p element are translatable. In contrast, the ITS information its:code="yes"
Orig>at the term element applies only to this element. It does not mean that the nested emph element is also a term.

Mod>Inheritance describes whether ITS information is applicable to child elements of XML nodes and attributes related
Mod>to these the XML nodes or their child notes.
Mod>The inheritance for the data category translate for example mandates that all child elements of XML nodes
Mod>are translatable whereas all attributes related
Mod>to these the XML nodes or their child notes are not translatable.

Orig>Overriding describes whether ITS information can be overriden or not. Overriding is not possible
Orig>for all data categories without inheritance, that is the Terminology and the Ruby data category. 

Mod>Overriding describes whether ITS information can be overriden/cancelled or not. Overriding is only possible
Mod>for data categories with inheritance. Overriding thus is not possible for the Terminology and the Ruby data category.

-----Ursprüngliche Nachricht-----
Von: public-i18n-its-request@w3.org [mailto:public-i18n-its-request@w3.org] Im Auftrag von Felix Sasaki
Gesendet: Sunday, September 24, 2006 2:10 AM
An: public-i18n-its@w3.org
Betreff: On issue 3640 and action item http://www.w3.org/2006/09/20-i18nits-minutes.html#action12


Hi all,

I did my action item
http://www.w3.org/2006/09/20-i18nits-minutes.html#action12
Felix to add an explanation for Default Values, Inheritance and
Overriding after the table in sec. 6.1

Please have a look at
http://www.w3.org/International/its/itstagset/itstagset.html#datacategories-defaults-etc
. (I added an explanation before the table)

Cheers,

Felix
Received on Monday, 25 September 2006 08:49:20 UTC

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