tag:blogger.com,1999:blog-20155610.post1860364547967567520..comments2024-03-06T02:46:19.929+00:00Comments on Translation Tribulations: The truth about memoQ 6.x and XLIFFKevin Lossnerhttp://www.blogger.com/profile/14727800526216764023noreply@blogger.comBlogger11125tag:blogger.com,1999:blog-20155610.post-69077057229882028412013-03-11T11:50:15.145+00:002013-03-11T11:50:15.145+00:00Interesting post, Kevin. As always!
For those who...Interesting post, Kevin. As always!<br /><br />For those who are in the need of looking up the language code of a specific language for Trados (that is "de-DE" for "German-Germany"), one of the most comprehensive overviews can be found in Microsoft's Go-Global Developer Center in the Microsoft Windows National Language Support (NLS) API Reference. The codes listed here, are the codes used in Trados:<br /><br />http://msdn.microsoft.com/de-de/goglobal/bb896001.aspx<br /><br />There you will find more or less all you will ever need for identifying a language, listing the following for each language:<br />- LCID<br />- Culture Name<br />- Language Country/Region<br />- Language Name<br />- Local language name<br />- ANSI codepage<br />- OEM codepage<br />- Country or Region name abbreviation<br />- Language name abbreviation<br /><br />If you should ever be in the need to find the ISO 639-3 code for, let's say, Pennsylvania German (WHAT?!?), check out this:<br />http://www-01.sil.org/iso639-3/codes.asp?order=639_3&letter=%25Stefan Gentzhttps://www.blogger.com/profile/08811475107709935196noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-89252623679602521432013-02-24T18:22:48.561+00:002013-02-24T18:22:48.561+00:00Count me in as part of the half of the world that ...Count me in as part of the half of the world that was confused by the way this change in XLIFF handling was "communicated by our Hungarian friends in the interface" (um, not at all?). While I can understand Kilgray's reasoning here in changing the file format, I would think it would be *very* helpful to to include a line of instructions right on the XLIFF export dialog describing, very briefly, the steps to take for generating a plain vanilla XLIFF file so users don't keep unwittingly sending off the default files produced to clients who can't open them. "Uncheck all boxes and rename the file extension to .xlf in the 'Save' dialog" is fine once you know about it, but this is the first time I've seen this clearly explained - 6 months after the fact!Susan Starlinghttps://www.blogger.com/profile/15682267788296230019noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-21393750621120348562013-02-24T18:17:46.818+00:002013-02-24T18:17:46.818+00:00@Jerzy, just in case you did miss it again, please...@Jerzy, just in case you did miss it again, please note that this article shows you how to create plain vanilla XLIFF, as you like to call it, straight from the Save dialog of memoQ 6. So it remains possible just as before, the options are merely arranged in an admittedly confusing way.Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-38103777867209884112013-02-24T18:00:55.049+00:002013-02-24T18:00:55.049+00:00@Jerzy, you and half the world were misled by the ...@Jerzy, you and half the world were misled by the confusion of those compressed defaults and the way they were communicated by our Hungarian friends in the interface. So I really think if it's time for a flogging, Kilgray gets the first stripes on the back. But what's this about no view filtering? Will you please share what you are smoking? My shoulder hurts, and I could use the really good shit. There are so many view filtering options in memoQ that it can drive you crazy. I agree about autopropagation of numbers. Crap compared to DVX and possibly Studio, for now at least.<br />Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-30557246852352773782013-02-24T16:57:42.401+00:002013-02-24T16:57:42.401+00:00Oh, I beg your pardon - I may have been mislead by...Oh, I beg your pardon - I may have been mislead by the mglxlz files indeed, as the version 5 has created nice plain vanila XLIFF, which could be opened with the standard file type in Studio, while the uncompressed xliff by version 6 will not open in Studio at all, at least not without defining your own file type fo it, but I certainly did not tell half the world MQ is crap :)<br />There is an interoperability between MQ and Studio, and if you define the MQ file type in Studio decently, I have encountered no losses in that exchange. So for the time being MQ serves me again as the mediator between Transit and Studio. Working with MQ is not an option, however, because despite it big advantages, there are some important things missing in MQ, making work with it inefficient. The first and biggest issue is view filtering, the second the way segments with numbers are handled - at least so was that in my last big project in MQ, where over 3000 words repetitions resulting from simple numbering like "part nnn" were not handled as such in MQ, but I simply had to confirm all occurances of "Part 1" separatedly from "Part 2" and so on - which would have been one autopropagation in Studio. Of course you can deal with such segments differently, but somehow I could not find out how to confirm "Part 1" and let all "Part nnn" be confirmed alltogether :)Anonymoushttps://www.blogger.com/profile/04392129096308809764noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-25312707884459497092013-02-23T15:42:10.717+00:002013-02-23T15:42:10.717+00:00@Dominique: Please re-read m comment. I said that ...@Dominique: Please re-read m comment. I said that I DOUBT that you made such claims. Information I see from you is inevitably accurate. Unless you read my crapp English wrong, of course ;-) I am referring to Jerzy. He and some others have told half the universe that memoQ is all screwed up for XLIFF now. It's been a real FUDdle. Even regular memoQ users are a bit confused in many cases for which I lay responsibilit straight at Kilgray's doorstep. You are innocent AFAIK :-)Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-63031830433532173472013-02-23T13:44:36.518+00:002013-02-23T13:44:36.518+00:00I would be grateful if you could point me to the p...I would be grateful if you could point me to the post(s) on the memoQ list (or elsewhere) where I made such claims, because I had a look at all posts of mine where "XLIFF" was mentioned and I couldn't find any.<br />You are perhaps confusing discussions about XLIFF with the uproar related to bilingual Word files. There was indeed a change between memoQ 5 and memoQ 6 in that respect, which upset many people (though not me), and Kilgray eventually reinstated the feature as it was in memoQ 5. But this has nothing to do with XLIFF.Dominique Pivardhttps://www.blogger.com/profile/12433336220556027479noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-5468540779174280292013-02-23T09:00:24.303+00:002013-02-23T09:00:24.303+00:00@Dominique: I doubt by you. J.C. and a number of o...@Dominique: I doubt by you. J.C. and a number of others have claimed for months that version 6 of memoQ will not create XLIFF any more and that a step backward has been taken in compatibility. An obvious, simple solution for the masses here is to add it as an explicit save option ("XLF for other tools" and *.xlf in the Save dialog), but even so, it works as you see and probbably already knew. And that bit with Trados sublanguages bedevils so many people - to the delight of SDL who happily leave the bug in the software to give the impression that others have the problem. Ii cornered the responsible develooper in Warsaw in September 2011 and it was clear he did not give a rat's tail about it. Or was ordered not to.Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-29888965955719372492013-02-23T06:27:26.329+00:002013-02-23T06:27:26.329+00:00Where has the "disinformation and misinformat...Where has the "disinformation and misinformation" been spread, and by whom, if I may ask?Dominique Pivardhttps://www.blogger.com/profile/12433336220556027479noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-16385377413710204842013-02-22T14:29:23.037+00:002013-02-22T14:29:23.037+00:00Thomas, are you sure that is an SDL bug and not a ...Thomas, are you sure that is an SDL bug and not a planned feature? ;-)Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-16671175136066390952013-02-22T13:35:51.510+00:002013-02-22T13:35:51.510+00:00There's another nasty bug in Studio where inli...There's another nasty bug in Studio where inline tags in mqxliff files get corrupt as well.Thomashttp://www.yamagata-europe.comnoreply@blogger.com