Hi John, The M4Loc tool chain only handles a subset of XLIFF inline tags generated by the Okapi Moses Text Filter
http://www.opentag.com/okapi/wiki/index.php?title=Moses_Text_Filter The complete list of tags generated by the filter is: g|x|bx|ex|lb|mrk If you aren't using the Okapi tools, you can still use their library, I believe, to convert das ist ein <bpt id="1"><b></bpt>kleines haus<ept id="1"></b></ept> into das ist ein <g id="1">kleines haus</g> and apply the reverse process to the translation. Alternatively you could modify M4Loc to handle all XLIFF inline tagging http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#Struct_InLine But I think that this would be more messy and with using Okapi you also get future XLIFF (e.g. 2.0) support. Achim From: [email protected] [mailto:[email protected]] On Behalf Of John Tinsley Sent: Wednesday, October 16, 2013 7:20 AM To: [email protected] Subject: [Moses-support] XLIFF support in the M4Loc project Hi folks, I'm having a little trouble with XLIFF handling using some of the M4Loc tools, specifically 'reinsert.pm' for replacing inline markup after translation.(https://code.google.com/p/m4loc/wiki/Pod_reinsert) It works fine for simple tags where the text between the tags *should* be translated, e.g. src: das ist ein <bx id="1">kleines haus</bx> tgt: this is |0-1| a |2-2| small |3-3| house |4-4| output: this is a <bx id="1"> small house </bx> However, there are often examples of paired tags (kind of like markup around markup) which are not handled, e.g. das ist ein <bpt id="1"><b></bpt>kleines haus<ept id="1"></b></ept> In this case, the <bpt> and <ept> tags are paired, and everything in between both sets of tags should be stripped out, e.g. <b> but this doesn't appear to be the case. Is there another tool in the project that handles this kind of markup or is it not supported? Thanks John -- John Tinsley
_______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
