IssuesAndProposedFeatures

From ITS

Jump to: navigation, search

Contents

Issues and Proposed Features

Proposal: targetPointer

This feature would complement the global rule for the Translate data category.

Rational

There is no way in the 1.0 translateRule element to handle multilingual document designed to have a source and one or more target text. XML format such as XLIFF, TMX, TS and others have such capability but cannot be processed without some kind of pre-processing by an ITS-aware tool.

The proposed additional attribute to the translateRule would simply provide a way to point to the node where the translation of the selected node should go or could be found.

Proposed Text

GLOBAL: The translateRule element contains the following:

  • A required selector attribute. It contains an XPath expression which selects the nodes to which this rule applies.
  • A required translate attribute with the value "yes" or "no".
  • An optional targetPointer attribute. It contains the relative XPath expression which selects the node where the translation of the node to which this rule applies should be located.

For example: 

<file>
 <its:rules xmlns:its="http://www.w3.org/2005/11/its" version="1.0"
  xmlns:itsx="http://www.w3.org/2008/12/its-extensions">
  <its:translateRule translate="no" selector="//file"/>
  <its:translateRule translate="yes" selector="//source"
   itsx:targetPointer="../target"/>
 </its:rules>
 <entry xml:id="one">
  <source>Text one of the source</source>
  <target>Text one of the target</target>
 </entry>
 <entry xml:id="two">
  <source>Text two of the source</source>
  <target></target>
 </entry>
</file>


Proposal: idPointer

This feature would complement the global rule for the Translate data category.

Rational

There is no way in the 1.0 translateRule element to associate the content with an identifier. Using identifiers with content is a very common activity in localization. Having a mechanism in place for this would be a significant improvement of the ITS capabilities.

The proposed additional attribute to the translateRule would simply provide a way to point to the node where the identifier of the selected node should go or could be found.

Proposed Text

GLOBAL: The translateRule element contains the following:

  • A required selector attribute. It contains an XPath expression which selects the nodes to which this rule applies.
  • A required translate attribute with the value "yes" or "no".
  • An optional targetPointer attribute. It contains the relative XPath expression which selects the node where the translation of the node to which this rule applies should be located.
  • An optional idPointer attribute. It contains the relative XPath expression which selects the node where the identifier of the node to which this rule applies should be located.

For example: 

<file>
 <its:rules xmlns:its="http://www.w3.org/2005/11/its" version="1.0"
  xmlns:itsx="http://www.w3.org/2008/12/its-extensions">
  <its:translateRule translate="no" selector="//file"/>
  <its:translateRule translate="yes" selector="//source"
   itsx:idPointer="../@name"/>
 </its:rules>
 <entry name="one">
  <source>Text one of the source</source>
 </entry>
 <entry name="two">
  <source>Text two of the source</source>
 </entry>
</file>

Proposal: Local "Elements within Text"

See original proposal at http://lists.w3.org/Archives/Public/public-i18n-its-ig/2008Oct/0014.html

This would complement the current Gobal rule of the "Elements Within Text" data category.

Rational

There is no local rule for the "Element Within Text" data category. Have a local rule would allow ITS processor without XPath support to still identify element nested or within text from other elements.

Proposed Text

LOCAL: The following local markup is available for the Element Within Text data category:

A withinText attribute with the value "yes, "no or "nested".

Example: the Element Within Text data category expressed locally.

The itsext:withinText attribute indicates that the <bold> element should be treated as part of the flow of the <par> element content. 

<text
 xmlns:its="http://www.w3.org/2005/11/its"
 xmlns:itsx="http://www.w3.org/2008/12/its-extensions"
 its:version="1.0">
 <body>
  <par>Text with <bold itsx:withinText='yes'>bold</bold>.</par>
 </body>
</text>

Proposal: "Context" data category

See original proposal at http://lists.w3.org/Archives/Public/public-i18n-its-ig/2008Oct/0015.html and thread at http://lists.w3.org/Archives/Public/public-i18n-its-ig/2008Nov/0002.html

Rational

TODO

Proposed Text

TODO

Retrieved from "http://www.w3.org/International/its/wiki/IssuesAndProposedFeatures"
Personal tools