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

[ESW Wiki] Update of "its0509SpecScoping" by ChristianLieske

From: <w3t-archive+esw-wiki@w3.org>
Date: Wed, 05 Oct 2005 22:10:16 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20051005221016.32637.12353@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 ChristianLieske:
http://esw.w3.org/topic/its0509SpecScoping


------------------------------------------------------------------------------
  
  However, problems may arise if full XPath (rather than only a subset) is permitted. Example: An XPath expression 'pointing' to an elements anchestors. Thus, one could consider an approach for restricted XPath.
  
- One positive aspect about XPath is of course the knowledge which people already have about it, and the libaries and other utilities which already are available for it.
+ One positive aspect about XPath is of course the knowledge which people already have about it, and the libaries and other utilities which already are available for it. In addition, XPath may also be the solution to the requirement related to 'limited impact' since it not only allows for an 'in situ' assignment of ITS related properties but also for a 'dislocated' assignment.
  
+ * in situ
+ 
+ {{{<para id="a1" its:translate="no" its:translateAttributes="productCode">
+ Do not translate this, <span productCode="River"> it's not worth it</span></para>}}}
+ 
+ * dislocated
+ 
+ {{{
+ <its:rules>
+   <its:rule translateNo="\\para"/>
+   <its:rule translateYes="@productCode"/>
+ </its:rules>
+ 
+ <para id="a1">
+ Do not translate this, <span productCode="River"> it's not worth it</span></para>}}}
+ 
Received on Thursday, 6 October 2005 07:47:14 UTC

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