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: Wed, 08 Jun 2005 12:36:28 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050608123629.6131.24181@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


------------------------------------------------------------------------------
  
  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 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.
- 
- '''[[FS-''' If we want s.t. like this, we need Schematron, or speaking generally XPath and possibly XPointer. That is, we need more than a Schema language in our sense - DTD, RELAX NG, XML Schema - can provide. We should note this fact here, or specify the "wording parts of a <text> element" to "marked up parts of a <text> element" ''']]'''
- 
- '''[[YS-''' I'm not sure if I follow this. Maybe the paragraph is not phrased correctly. I meant that we need a way to tell that an element or an attribute is translatable (at the schema or at a top-document level) and also a mean to override such setting. for example: by default elements of a given resource-kind schema are not translatable, but all <p> element in that schema are translatable (the exception), but a specific <p> could hold only non-translatable text (exception within the exception). One can code this last element with a simple its:translate="no". No need for Schematron or XPath, etc. (?)
- 
- I guess I probably should not say 'exception' for the rule <p> is translatable, it's just a rule that override the default rule). Am I making sense?''']]'''
- 
- '''[[FS-'''Now I understand. How about: '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 (with an attribute its:translate="no") 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 occurences of a <text> element (e.g. with an attribute its:translate="no") may not be translatable.
  
  The mechanism should be able to map existing elements that already carry implicitly or explicitly the translatability information.
  
Received on Wednesday, 8 June 2005 13:36:32 GMT

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