OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [okapi-devel] Global <gls:glossary> element in XLIFF 2.0?

Hi Martin,


Actually there is another way to point to glossary data.


The Term annotation, which is part of the Core, can use the ref attribute to point to information about the denoted term (See http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html#termAnnotation) so you could do something like this:


<xliff xmlns='urn:oasis:names:tc:xliff:document:2.0' version='2.0'

srcLang='en' trgLang='fr' xmlns:gls="urn:oasis:names:tc:xliff:glossary:2.0">

<file id='1'>

<unit id="1">


       <gls:glossEntry id='g1'>

         <gls:term source="publicTermbase">TAB key</gls:term>

         <gls:translation id="1" source="myTermbase">Tabstopptaste


         <gls:translation source="myTermbase">TAB-TASTE


         <gls:definition source="publicTermbase">A keyboard key that is

             traditionally used to insert tab characters into a document.





       <source>Press the <mrk id="m1" type="term" ref="#gls=g1">TAB key</mrk>.</source>

       <target>Drücken Sie die <mrk id="m2" type="term" ref="#gls=g1">TAB-TASTE</mrk>.







As you can see the pointing is done from the <mrk> to the glossary entry, rather than the reverse. That allows several occurrences of the same term in a single unit to refer to a single glossary entry.


The tricky part is to remember to use a URI in the ref of the <mrk>, not just an ID. In this case ref="#gls=g1" will be resolved as "f=1/u=1/gls=g1" and will point to the corresponding <gls:glosEntry> element.


You can verify this online here: http://okapi-lynx.appspot.com/fragments


Or you can use the –vr command of Lynx, the little tool that comes with the XLIFF2 toolkit distribution (https://bintray.com/okapi/Distribution/Okapi_XLIFF_Toolkit, (BTW we need to release 1.0.1 there)).


I hope this helps,




From: Yves Savourel [mailto:ysavourel@enlaso.com]
Sent: Sunday, October 18, 2015 7:45 AM
To: 'okapi-devel@googlegroups.com' <okapi-devel@googlegroups.com>; 'xliff-comment@lists.oasis-open.org' <xliff-comment@lists.oasis-open.org>
Subject: RE: [okapi-devel] Global <gls:glossary> element in XLIFF 2.0?


Hi Martin,


Yes, I suppose: pointing to the first occurrence is the only option.

It’s not great as the several occurrences may be in separate segments, and thus treated separately from the user viewpoint.


Maybe someone in the XLIFF TC has some idea how to address that use case?






From: okapi-devel@googlegroups.com [mailto:okapi-devel@googlegroups.com] On Behalf Of Martin Wunderlich
Sent: Friday, October 16, 2015 6:05 AM
To: okapi-devel <okapi-devel@googlegroups.com>
Subject: [okapi-devel] Global <gls:glossary> element in XLIFF 2.0?



This is not strictly an Okapi question, but somehow I have this feeling that people here might be able to help. I am currently looking into using the glossary module provided by XLIFF 2.0. I noticed that the glossary entries can be attached to several different strucural elements. One glossary entry can reference one id atrribute. This is the id attribute of the mrk element, which is used to mark the occurrence of the term. However, since this id attribute needs to be unique within a <unit> element, how would you deal with the same term occurring in several segments in the same unit? Would you reference only the first instance?


PS: I haven't forgotten about checking the source jar generation; it's been a weird week...

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]