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

[ESW Wiki] Update of "its0505Translatability" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Mon, 13 Jun 2005 08:08:17 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050613080817.12035.26848@localhost.localdomain>
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification.

The following page has been changed by YvesSavourel:
http://esw.w3.org/topic/its0505Translatability


------------------------------------------------------------------------------
  
  == Summary ==
  
- Methods must exist to allow to specify the parts of a document that are translatable or not.
+ Methods must exist to allow to specify the parts of a document that are to translate or not.
  
  
  == Description ==
  
- The content of XML documents can usually be seen as either generally translatable (e.g, and XHTML file), or generally not translatable (i.e. An SVG file). A mechanism should exist to identify the parts of the document that are exceptions to the rule.
+ The content of XML documents can usually be seen as either generally to translatable (e.g, an XHTML file), or generally not translatable (i.e. An SVG file). A mechanism should exist to identify the parts of the document that are exceptions to the rule.
  
- The mechanism should also allow to specify exceptions within exceptions. For example, it should allow to specify that SVG <text> is translatable, but also that some occurences of a <text> element (e.g. with an attribute translate="no") may not be translatable.
+ The mechanism should also allow to specify exceptions within exceptions. For example, within the elements of an SVG document, which are generally not translatable, it should allow to specify that <text> is to be translated, but also that some occurences of the <text> element (e.g. with an attribute translate="no") may not to be translated.
  
  The mechanism should be able to map existing elements that already carry implicitly or explicitly the translatability information.
  
- Example 1: The <code> element in XHTML may be an indicator the its content is not translatable.
+  * Example 1: The <code> element in XHTML may be an indicator the its content is not translatable.
  
- Example 2: The <text> element in SVG indicates translatable content.
+  * Example 2: The <text> element in SVG indicates translatable content.
  
- Example 3: The translate attribute in DITA is used to flag translatability.
+  * Example 3: The translate attribute in DITA is used to flag translatability.
  
- The mechanism should provide a way to delimit a portion of the content if such mechanism does not exists in the original vocabulary.
+ The mechanism should provide a way to delimit a portion of the content if such mechanism does not exists in the original vocabulary (so parts of a content could be set to be translated or not).
  
  The methods used to identify the translatable parts of a document should be useable by localization tools for both:
  
@@ -41, +41 @@

  
  == Note ==
  
- Part of this requirement is related to the "Span-Like Element" requirement [http://esw.w3.org/topic/its0503ReqSpan]. Another part is related to the "Purpose specification/mapping" requirement [http://esw.w3.org/topic/its0504ReqPurposeSpecMap].
+ Part of this requirement is related to the "Span-Like Element" requirement [http://esw.w3.org/topic/its0503ReqSpan].
  
+ Another part is related to the "Purpose specification/mapping" requirement [http://esw.w3.org/topic/its0504ReqPurposeSpecMap].
+ 
+ There is a relationship between indicating the parts of a content that are to be translated and the parts of a content that are to be included in metrics counts [http://esw.w3.org/topic/its0505WordCount].
+ 
+ The information about the parts of a document that are translatable is not limited to localization. Such information can be used in other contexts. For instance when implementing Accessibility features, it can be used to identify content that need to be process differently from the rest of the document.
+ 
Received on Monday, 13 June 2005 09:19:08 GMT

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