OASIS XML Localisation Interchange File Format (XLIFF) TC

Dear all,  the attached slides are joint work done between LRC and Alan Melby's translation research group at BYU. The slides and mapping have been elaborated by Alan's assistant James Hayes. This was presented by Alan and found worthy by the participants of the 5.5 XLIFF Symposium last week in Vancouver. It basically shows that a bidirectional lossless mapping between XLIFF 2.0 core + gls and TBX basic is possible and relevant for a number industry use cases.  The proposal is to make  [TBX basic] <-> [XLIFF 2.0 including gls module] mapping  an XLIFF 2.1 feature. The mapping should be described in an Appendix similar to the ITS support appendix we are working on for the the ITS mapping. Unlike the ITS mapping the TBX basic mapping does not seem to require an extra namespace or module. That's also why we think it is feasible to add this feature to 2.1 and not waiting for 2.2. The current thinking is that the Appendix be informative from the XLIFF point of view but the TBX Steering Commitee at LTAC http://www.ltacglobal.org/ who should be in charge of developing freely available TBX based industry specifications can and will make normative references to the mapping. Alan Melby and Hanne Smaadahl who are on the LTAC committee and ISO TC 37 are on CC.  Thanks and regards dF Dr. David Filip ======================= OASIS XLIFF TC Secretary, Editor, and Liaison Officer  LRC CNGL CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 http://www.cngl.ie/profile/?i=452 mailto:  david.filip@ul.ie ---------- Forwarded message ---------- From: Alan Melby < alan.melby@gmail.com > Date: Wed, Oct 29, 2014 at 8:24 PM Subject: slides for Melby presentation today at FEISGILTT To: alan melby < alan.melby@gmail.com > Cc: "Dr. David Filip" < David.Filip@ul.ie >, olaf-michael Stefanov < omstefanov@gmail.com > see attached files: slides and two XML files to put onto presentation laptop AKM Attachment: XLIFF2_TBX_Presentation.pptx Description: application/vnd.openxmlformats-officedocument.presentationml.presentation Attachment: sample1(TBX-Basic).tbx Description: Binary data Attachment: sample1.xlf Description: Binary data

Hi all, I couldn’t attend this interesting presentation, but now looking at the example files, and in the spirit of not applying Postel's Law (the new policy being "Don't go Postel, go postal!"), here are a few errors: -- The attributes in the glossary elements must not be prefixed. In <gls:glossEntry ref="..."> and <gls:glossEntry gls:ref="..."> the ref attributes are seen differently by the XML processors. In XLIFF (and in 99% of the XML applications) you should use un-prefixed attributes so they are seen as belonging to the element where they are declared. Nothing to do with XLIFF: this is XML stuff. So to be valid all attributes in the glossary elements must be un-prefixed. -- The reference in <gls:translation ref="#m2" > points to nothing. The ref value is an IRI, so it must use the fragment identifier mechanism. To point to the <mrk id="m2"> that is in the target, you must use ref="#t=m2". Not Soroush's fault: he just used the incorrect example we have in the specification and that (I think) we already have taken steps to fix. The conclusion: it's always a good idea to validate an example :) (That goes for the specification too) One additional thought: In real life, it's likely that at first the source will be copied into the target and therefore we would have no target-specific marker m2, but instead an m1 in the target too (which would also help in linking the source term and its translation without using the glossary module). I think it would be perfectly fine to have: <unit id="1"> <gls:glossary> <gls:glossEntry ref="#m1"> <gls:term source="publicTermbase">TAB key</gls:term> <gls:translation id="1" source="myTermbase">Tabstopptaste </gls:translation> <gls:translation source="myTermbase">TAB-TASTE </gls:translation> <gls:definition source="publicTermbase">A keyboard key that is traditionally used to insert tab characters into a document. </gls:definition> </gls:glossEntry> </gls:glossary> <segment> <source>Press the <mrk id="m1" type="term">TAB key</mrk>. </source> <target>Drücken Sie die <mrk id="m1" type="term">TAB-TASTE</mrk>. </target> </segment> </unit> Cheers, -yves