W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > February 2013

RE: Issue-55: XLIFF mapping - Terminology and termInfoPointer

From: Yves Savourel <ysavourel@enlaso.com>
Date: Wed, 20 Feb 2013 05:03:00 -0700
To: 'Mārcis Pinnis' <marcis.pinnis@Tilde.lv>, <public-multilingualweb-lt@w3.org>
Message-ID: <002d01ce0f62$3b2d76d0$b1886470$@com>
Sorry Mārcis my question was not clear.

I meant to say: Should a term declared for example on an HTML <p> element be mapped to an annotation on the <source> element in XLIFF, or should we only use <mrk> to map terms?

HTML:

<p its-term='yes' its-term-info-ref='http://en.wikipedia.org/wiki/Adenomus'>adenomus</p>

XLIFF:

<trans-unit id='1'>
 <source its:term='yes' its:termInfoRef='http://en.wikipedia.org/wiki/Adenomus'>adenomus</source>
</trans-unit>

or

<trans-unit id='1'>
 <source><mrk mtype='term' its:termInfoRef='http://en.wikipedia.org/wiki/Adenomus'>adenomus</mrk></source>
</trans-unit>

There are pros and cons for both cases.
 
-yves

-----Original Message-----
From: Mārcis Pinnis [mailto:marcis.pinnis@Tilde.lv] 
Sent: Wednesday, February 20, 2013 2:30 AM
To: Yves Savourel; public-multilingualweb-lt@w3.org
Subject: RE: Issue-55: XLIFF mapping - Terminology and termInfoPointer

Hi Yves,

>> --- Do we want to have a <source>/<target>-level terminology info?

Why not? In our localisation workflows translators heavily rely on external term bank information when they identify terminology. If such information can be wisely passed on to the CAT tools and then translators (for instance, through ITS 2.0 metadata included in XLIFF documents), it would make life easier for them...

Best regards,
Mārcis ;o)

-----Original Message-----
From: Yves Savourel [mailto:ysavourel@enlaso.com] 
Sent: Wednesday, February 20, 2013 3:54 AM
To: public-multilingualweb-lt@w3.org
Subject: RE: Issue-55: XLIFF mapping - Terminology and termInfoPointer

More on the Terminology mapping:

We say we should use <mrk mtype='term' [its:termInfoRef (or xyz:itsTermInfo-like attribute)]>term</mrk> That's good but:

--- Can we put other ITS data categories in that same <mrk> too?
-> why not?

--- How do we express its;term='no'?
Is it even needed in XLIFF?

--- Do we want to have a <source>/<target>-level terminology info?
If no: then what do we do with something like <html:p its-term='yes'>word</html:p>?

We could 'move the info to an <mrk>, but then things become *very complicated* to map back and forth.

any thoughts
-yves
Received on Wednesday, 20 February 2013 12:03:36 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 9 June 2013 00:25:08 UTC