tag:blogger.com,1999:blog-20155610.post3040715670282228416..comments2024-03-06T02:46:19.929+00:00Comments on Translation Tribulations: memoQuickie: "compatible" XLIFF in memoQ 6, 6.2 and 2013Kevin Lossnerhttp://www.blogger.com/profile/14727800526216764023noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-20155610.post-89851585269743463032016-05-27T17:11:30.370+01:002016-05-27T17:11:30.370+01:00Hi Kevin & all,
I know I'm 3 years late, ...Hi Kevin & all,<br /><br />I know I'm 3 years late, but this seemed relevant to the discussion:<br /><br />I was just investigating the .mxliff format (MemSource).<br /><br />I wanted to import this file into memoQ, and attempted to do so using the default plain XLIFF filter, though unfortunately all the special metadata is ignored (as expected).<br /><br />I got curious and started comparing files to see if it would be simple to write a conversion program for mliff -> mqxliff, when I came across something interesting.<br /><br />The XLIFF 1.2 standard does not specify values for the "locked" attribute of , so the follow is not so surprising, but it's still a situation that incidentally supports vendor lock-in, since it complicates conversion between vendor formats needlessly:<br />Notice how in the below image, MemSource uses "true" to indicate that a segment is locked, while memoQ uses "locked".<br /><br />http://pasteboard.co/1eQl7I6L.png<br /><br />I pity anyone tasked with writing fully-functional conversion filters for these formats. Of course, there is probably some very good reason why memoQ does not use the more obvious choice, "true", like MemSource does.<br /><br />Briefly put, predictability is important, but this is the enemy of vendors who wish to retain and grow their business (preferably until they take over most of the market, like Microsoft brilliantly achieved with their hard-to-crack formats for years. Not to be tough on MS - their recent open source initiatives are commendable.)<br /><br />So, Kevin, I certainly agree that Kilgray could have done more to promote transparency and ease of use, and using a compressed by format could be considered a brazen attempt at boosting vendor lock-in, though it's also conceivable that some clients preferred this for security reasons, since compressed files can not easily be scanned/grepped, assuming the contents are very sensitive.). Moreover, compression can of course greatly reduce file-size, as mqxliff gets bulky rather fast.Anonymoushttps://www.blogger.com/profile/02078747728543041409noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-30107167638217396922015-09-22T08:44:05.755+01:002015-09-22T08:44:05.755+01:00The problem is, however, that they've changed ...The problem is, however, that they've changed the XBench licence and starting from 3.0 it's no more freeware.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20155610.post-34088788859147635292014-10-02T11:39:23.536+01:002014-10-02T11:39:23.536+01:00Kevin, you´re a life saviour :) Thanks for the inf...Kevin, you´re a life saviour :) Thanks for the info and you are absolutely right, both Memo Q and Trados should find a way to work together, streamline system processes for seamingless compatibility - we, who work with these have better things to do with our time than doing research to change file formats!!Felicia O.http://portuguesecomservices.com/noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-80901166521080261912013-08-09T00:54:16.753+01:002013-08-09T00:54:16.753+01:00Does it default to mqxlz? Never noticed that. Appa...Does it default to mqxlz? Never noticed that. Apparently it remembers my preference, which is good.TvNellenhttps://www.blogger.com/profile/10897450787844197904noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-66522085245937352292013-08-09T00:01:16.647+01:002013-08-09T00:01:16.647+01:00Thomas, I don't have much of a problem with a ...Thomas, I don't have much of a problem with a unique, branded extension, though internal identifiers with a known extension would have been better. The biggest problem for me is defaulting to the compressed format (MQXLZ), which is yet another renamed ZIP file. I have seen a lot of people send this on to others, thinking they have shared an XLIFF, and the trouble starts.....Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-7402474998407629592013-08-08T23:57:41.697+01:002013-08-08T23:57:41.697+01:00I believe that. But the fact is that Kilgray's...I believe that. But the fact is that Kilgray's priorities don't always coincide with mine, and if there is a simple solution to a problem that involves some tweaking, I'm happy to settle for that. Xliff is supposed to be an exchangeable standard format. It's sad that Kilgray couldn't resist the urge to imitate SDL and created their own signature extension.TvNellenhttps://www.blogger.com/profile/10897450787844197904noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-73639269332896162022013-08-08T22:32:43.626+01:002013-08-08T22:32:43.626+01:00Doesn't matter Thomas - we should not have to ...Doesn't matter Thomas - we should not have to tweak this. It should be done properly in the system defaults. It's not that hard to make the necessary change.Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-38833263193877809542013-08-08T22:13:26.185+01:002013-08-08T22:13:26.185+01:00The standard addition of the language code in the ...The standard addition of the language code in the names of exported documents can be changed in a deeply hidden system file. I wonder if there exists a similar hack for this issue. <br />ThomasTvNellenhttps://www.blogger.com/profile/10897450787844197904noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-77153858445016710152012-12-04T17:44:55.110+00:002012-12-04T17:44:55.110+00:00Only a little note not directly in behalf: the nex...Only a little note not directly in behalf: the next version of Apsic Xbench(ver.3) will support MemoQ 6 XLiff files :)Pablo Bouvierhttps://www.blogger.com/profile/07439802248509869088noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-88416967380931089012012-09-03T18:16:49.142+01:002012-09-03T18:16:49.142+01:00The need to rename the file extension of the MQXLI...The need to rename the file extension of the MQXLIFF to XLF, etc. also apples to previous versions of memoQ. In those the program will also insist that the <i>Import/update bilingual</i> function be used rather than <i>Add document</i>.Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.com