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

ITS-related comments for TMX 2 proposal

From: Yves Savourel <ysavourel@translate.com>
Date: Mon, 7 May 2007 15:27:18 -0600
To: <public-i18n-its@w3.org>
Message-ID: <00a501c790ee$7d94d2f0$8f05a8c0@BREIZH>

Hi all,

Here are some ITS-related comments I've found for for the TMX 2.0 Draft.
I've written then as draft for the group review. Please, 


=== 1) Integrating ITS in TMX

While we note that foreign attributes can be assigned to all elements of the TMX 2.0 proposal, we feel that it would help the
implementers to list the attributes related to internationalization and there possible locations, just like xml:lang and xml:spaces
are listed. This is especially important since the section 1.1 states:

"Applications that depend on TMX format for exchanging Translation Memory data are not required to understand and support non-TMX
elements or attributes. A TMX application can safely ignore foreign elements or attributes present in a TMX document."

We think the its:dir attribute should be added to the <prop>, <note>, <tuv>, <g>, and <hi> elements.


=== 2) Replacing <prop> element by foreign attribute

In the description of the <prop> element, the 2.0 proposal states that a foreign attribute should be used instead of <prop>.

This may not be always possible: The content of the <prop> element could be text and requires language-related metadata (i.e.
xml:lang, or its:dir). Applying such metadata cannot be done if the text is moved to an attribute.

We would recommend to either keep <prop> or allow it to be replaced by either a foreign attribute or a foreign element.


=== 3) ITS Rules for TMX

We would recommend LISA to provide an ITS rules file along with the TMX specification. This rules file would specify the different
internationalization aspects of the TMX document and allow generic ITS-aware tools to be able to process it. For example, a
spell-checker could be used to verify the text of the different translation units.

* What elements or conditional constructs do not contain text.

* What elements are "within text" or "nested".

* If there are localization-type notes associated to some elements

* Etc.

Here are some examples of ITS rules pertaining to TMX:

<its:translateRule selector="tmx:tmx" translate="no"/>

<its:translateRule selector="//tmx:seg" translate="yes"/>

<its:translateRule selector="//tmx:bpt|//tmx:ept|//tmx:ph" translate="no"/>

<its:translateRule selector="//tmx:sub" translate="yes"/>

<its:withinTextRule selector="//tmx:g|//tmx:x|//tmx:bpt//tmx:ept//tmx:hi//tmx:ph" withinText="yes"/>

<its:withinTextRule selector="//tmx:sub" withinText="nested"/>

<its:locNoteRule selector="//tmx:seg" locNotePointer="../tmx:note"/>



That is all I have so far.
Still working on it, but the rest seems non-ITS related.

Cheers,
-yves
Received on Monday, 7 May 2007 21:27:02 GMT

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