tag:blogger.com,1999:blog-20155610.post1686799063803507791..comments2024-03-06T02:46:19.929+00:00Comments on Translation Tribulations: memoQ projects now translatable and editable in an RTF editor!Kevin Lossnerhttp://www.blogger.com/profile/14727800526216764023noreply@blogger.comBlogger11125tag:blogger.com,1999:blog-20155610.post-68434583037559035512010-05-08T03:19:24.404+01:002010-05-08T03:19:24.404+01:00@Rod: Not betting the drilling, but you can have m...@Rod: Not betting the drilling, but you can have my first-born son instead. If I lose the bet, I'll just have to find a volunteer to bear him first. <br /><br />But even if I were to bet the rifle I'm sure to keep it. Yesterday at lunch the developer responsible for the new memoQ editor sat on my left and a charming outside consultant to Kilgray who teaches students of Japanese and Chinese translation, uses those languages herself and is aware of the problem sat on my right. Before the main course arrived they were talking. So I believe that matters <i>will</i> get worked out. Maybe not tomorrow, but within an objectively reasonable time, and with her support, appropriate testing by a good number of persons with the relevant linguistic competence is assured.Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-84419332075999358312010-05-06T09:46:35.743+01:002010-05-06T09:46:35.743+01:00Thanks Kevin!
That's good news.
I will of co...Thanks Kevin!<br /><br />That's good news.<br /><br />I will of course be very happy to cooperate with any testing and feedback that might need to be done. <br /><br />(If you're betting something, I already have a decent bike, so why not put up your new shooting iron instead?)<br /><br />Enjoy the rest of your conference, and I look forward to your updates.<br /><br />RodRodhttps://www.blogger.com/profile/04229724488178529402noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-74122670184103272592010-05-06T08:35:13.822+01:002010-05-06T08:35:13.822+01:00@Rod: The matter has been under discussion for two...@Rod: The matter has been under discussion for two days already. It will be dealt with, but there the developer who rewrote the editing engine needs to spend some time to understand the issue more clearly. The people in the Kilgray camp who actually read the languages affected haven't seen the relevant information yet. I will forward it to them personally to make sure that everyone understands the matter. If Wenjer has good examples for Chinese I would like to see those too.<br /><br />Actually, as far as I could tell from our chat, the developer understand at a theoretical level what's wrong. He explained the technical challenge of the underlying technology in more detail than I could follow, but the upshot is that he's very aware of it and simply needs to get some specific feedback from the right people. It will get fixed, I'll bet my bicycle on it.Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-17494754911967674932010-05-06T07:10:57.635+01:002010-05-06T07:10:57.635+01:00Hi Kevin,
I see you're in the TeNT even as we...Hi Kevin,<br /><br />I see you're in the TeNT even as we speak. <br /><br />The Kilgray people have no excuse not to understand the matter I raised since I sent them screenshots of the problem and a careful, atonal analysis. You can see the shots here;<br />http://translationandlanguage.ning.com/group/memoq/forum/topics/memoq-with-japanese<br /><br />For people who aren't used to looking at Japanese, the way the text is rendered may look OK. But let me assure you, it isn't. By way of analogy, it's a bit like trying to work all day with a Fraktur font. It's a big step backwards from earlier versions.<br /><br />Since you're there, could I ask you to give one of the Kilgray people a poke from me about this? I've come to rely on memoQ and I was looking forward to some improvements. Well, they came, but hobbled with something that looks like Fraktur. I'm sure you can appreciate how frustrating that would be. If you could just convey that, I'd be delighted to readjust my position with regard to the TeNT. <br /><br />I'd be much obliged to ye.Rodhttps://www.blogger.com/profile/04229724488178529402noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-61341591124924677232010-04-30T14:37:17.162+01:002010-04-30T14:37:17.162+01:00@Kevin
Thanks for the tip!@Kevin<br /><br />Thanks for the tip!Mykhailo Voloshkohttps://www.blogger.com/profile/17969878128467008625noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-17364589122722328332010-04-30T06:33:06.611+01:002010-04-30T06:33:06.611+01:00Rod, while you are relieving yourself, you might c...Rod, while you are relieving yourself, you might consider that the particular feature I mention here - the importable/exportable RTF tables for translation and review - will be utterly unaffected by the character display issue you mention. An exported table can be translated using whatever tool you please, including a word processor.<br /><br />This, by the way, is a feature for which I have waited for a total of about two years now, because it is a critical part of my workflow with Déjà Vu (another tool about which I think you have anything nothing good to say). During those two years Kigray continued to develop other aspects of the software as a matter of priority. In fact, until last year's memoQfest 2009, I'm not really sure they understood what I wanted or whether it was important to anyone but me. Then an interesting thing happened: in an open discussion after one of the presentations, a half dozen members of the audience discovered that they had been asking for the same thing, just calling it by different names. Suddenly it became a priority (among other priorities for version 4), and now we have a better implementation of the feature than what I know and love from Déjà Vu.<br /><br />Was I frustrated with the wait? You bet. Was I tempted to unzip and let it rip on the only TEnT tool provider I know that seems to have a viable strategy for satisfying both the corporate and freelance sides of this business, that provides excellent, friendly support and that has staff who are allowed to act like real people? No way. There were simply too many positive things going on for me to reach for the long knife.<br /><br />I have some - not a lot - background in your working language, Japanese, though when I learned it I don't think there were any word processors usable by humans that could deal with it. Come to think of it, there weren't any word processors. That came later. In any case, although you have articulated this issue with font display a number of times on Watercooler and elsewhere and Wenjer has confirmed the same or something like it for Chinese, I haven't really understood what you're talking about. It's obvious that there is a problem, one which needs to be corrected before the product is viable for the Far East market, but a combination of foggyheadedness (lack of sleep on my part) and tone (on yours) makes it hard to grasp the point.<br /><br />I don't know what's on the plan for this in Budapest, nor do I lose sleep at night worrying about it, because it's not my market. I would, of course, look at things very differently in your position. However, as I recall you had a good, working system with MQ 3.6, didn't you? And the TMs and termbases are compatible at the desktop level. So patience with concurrent productivity is in fact an option with the software. Try waiting as long as I did for RTF tables before you play with your zipper.<br /><br />When I see that people like Angelika Zerfass (a German trainer who is competent in Japanese and/or Chinese) are heavily involved in Kilgray's effort, I have some confidence that these things will be worked out. But one thing I have learned to respect highly in the two years I have watched the company closely: this team has an excellent understanding of how to set priorities, and when a good case is made or presents itself, priorities are adjusted accordingly. They are simply brilliant in this regard, and my hat is off to them even if I often don't get what I want when I want it.Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-19146205745098295902010-04-30T03:50:13.550+01:002010-04-30T03:50:13.550+01:00Ah, how I wish I were inside that TeNT pissing out...Ah, how I wish I were inside that TeNT pissing out, rather than the other way round at present! <br /><br />Until Kilgray sorts out the way it displays Japanese, all these beneficial new developments will be useless to me. And Kilgray have not given any indication of when they intend to fix the problem. <br /><br />Actually the problem with Japanese in MemoQ is like the expression TeNT - it's godawful to look at. So I shall keep pissing into it until the occupants get the message!Rodhttps://www.blogger.com/profile/04229724488178529402noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-49789431237507665282010-04-29T00:00:38.193+01:002010-04-29T00:00:38.193+01:00@Mykhailo: You can do exactly that with this featu...@Mykhailo: You can do exactly that with this feature. If you want only commented segments in your RTF export, then create a corresponding filtered view and export that as a bilingual RTF table. Denis Hay at Kilgray sent me that tip yesterday after reading this post.Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-92028662054963253922010-04-28T23:24:59.864+01:002010-04-28T23:24:59.864+01:00Thanks for the great news, Kevin!
I also asked Ki...Thanks for the great news, Kevin!<br /><br />I also asked Kilgray staff to add feature enabling the user to export the segments with comments.Mykhailo Voloshkohttps://www.blogger.com/profile/17969878128467008625noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-62192876650098189972010-04-28T20:54:37.360+01:002010-04-28T20:54:37.360+01:00@barbudo: Of course you ask me this question a few...@barbudo: Of course you ask me this question a few weeks after I de-installed SDLX for testing purposes :-) Nonetheless there are likely a number of options. Doesn't SDLX handle Trados bilingual RTF/DOc files? If it does, you can produce those exports from memoQ. Or you can use these new RTF table exports in version 4.2 and copy the source column into a separate document, translate it, then paste the results into the target column and re-import. (Or make things easier by populating the target column with the source and hiding all the text you don't want translated if SDLX has an "ignore hidden text" option. The guidelines I wrote on prepping RTF and Word files with content to exclude (available <a href="http://www.simmer-lossner.com/lib/examples/PreparingFilesWithUntranslatableContent.pdf" rel="nofollow">here as a PDF</a>) might help you in this regard.Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-83727949263426822412010-04-28T19:09:21.683+01:002010-04-28T19:09:21.683+01:00Thanks, Kevin.
BTW, do you happen to know if ther...Thanks, Kevin.<br /><br />BTW, do you happen to know if there is a way to prepare projects in memoQ and export them for translation in SDLX?Grisha Gazarianhttps://www.blogger.com/profile/15082445039147079471noreply@blogger.com