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: Tue, 17 May 2005 21:26:33 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050517212633.22114.55655@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


------------------------------------------------------------------------------
  
  Follow the [http://esw.w3.org/topic/itsHowTo conventions] for editing this page.
  
+ '''[http://esw.w3.org/topic/its0505WikiProcess Status: Initial Draft]''' 
- '''[http://www.w3.org/International/geo/2004/article-devt-process.html Status: Initial Draft]''' 
- ie. please focus on technical content, rather than wordsmithing at this stage.
  
  Author: Yves Savourel
  
@@ -16, +15 @@

  
  == Summary ==
  
+ Methods must exist to allow to specify the parts of a document that are translatable or not.
- Methods must exist to specify that the content of an element, part of the content of an element, or an attribute value, are translatable or not.
- 
- '''[[YS-''' It's bad to have translatable attribute, but they exist. So, should be have provision for them then?''']]'''
  
  '''[FS] It is necessary to have a provision for attributes, but it it not necessary to describe the provision in the requirements spec. We can leave that to the actual description of the tag set.'''
+ 
+ '''[YS-''' Does the updated text above sound better?''']]'''
  
  
  == 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 the exception.
+ 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 mechanism should also allow to specific exceptions within exceptions. For example, it should allow to specify that SVG <text> is translatable, but also that some parts of a <text> element may not be translatable.
+ 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 parts of a <text> element may not be translatable.
  
  The mechanism should be able to map existing elements that already carry implicitly or explicitly the translatability information.
  
@@ -37, +36 @@

  
  Example 3: The translate attribute in DITA is used to flag translatability.
  
- It 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.
+ 
+ The methods used to identify the translatable parts of a document should be useable by localization tools for both:
+ 
+  * Processing the document directly.
+  * Generating localization properties settings files that can be used on all documents of the same document type.
  
  == Note ==
  
- Part of this requirement is related to the "Span-Like Element" requirement [http://esw.w3.org/topic/its0503ReqSpan]
+ 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].
  
Received on Tuesday, 17 May 2005 21:37:58 GMT

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