TMX import/export troubles Thread poster: FarkasAndras
|
|---|
MemoQ seems to have some compatibility problems with metadata in TMX.
One issue involves TMX import; extra text fields are lost in importing.
TMX sample, generated by my aligner - the "Note" field goes MIA after importing to MemoQ:
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE tmx SYSTEM "tmx14.dtd">
<tmx version="1.4">
... See more MemoQ seems to have some compatibility problems with metadata in TMX.
One issue involves TMX import; extra text fields are lost in importing.
TMX sample, generated by my aligner - the "Note" field goes MIA after importing to MemoQ:
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE tmx SYSTEM "tmx14.dtd">
<tmx version="1.4">
<header
creationtool="LF aligner"
creationtoolversion="2.51"
datatype="unknown"
segtype="paragraph"
adminlang="EN-GB"
srclang="EN-GB"
o-tmf="TW4Win 2.0 Format"
>
</header>
<body>
<tu creationdate="20110226T113508Z" creationid="LF aligner 2.51"><prop type="Txt::Note">here's some metadata</prop>
<tuv xml:lang="EN-GB"><seg>Oh look, some English text</seg></tuv>
<tuv xml:lang="HU"><seg>Ez meg magyarul van</seg></tuv> </tu>
</body>
</tmx>
Does MemoQ not support such text fields?
The other problem is that when a TMX export coming from MemoQ is imported into Studio, creation IDs and creation times are all lost, being replaced by the current date and time and the ID set in Studio.
Admittedly, this latter problem could well be more Studio's fault than MemoQ's, but, being the upstart, MemoQ should take extra care to be Studio compatible. I myself solved the same problem in my aligner by spoofing the Trados o-tmf string as you can see above. I would have thought Kilgray would have done some research and found a solution for Studio compatibility as well.
I wonder what the problem is. Does one tool or the other fail to meet the TMX spec? Do both meet the spec, in which case the spec itself is broken? This situation is clearly unacceptable, I just don't know who to blame and how to solve it (apart from kludges like hacking the TMX myself or doing a daisychain import via some other tool). ▲ Collapse
| | | | FarkasAndras 
Local time: 00:07
English to Hungarian
+ ...
TOPIC STARTER
Any comment from Kilgray?
| | | | FarkasAndras
Local time: 00:07
English to Hungarian
+ ...
TOPIC STARTER | That settles it, I guess | Jun 1, 2011 |
The deafening roar of crickets here suggests that it's time to lay this old myth of great MemoQ support to rest.
| | | | Selcuk Akyuz
Türkiye
Local time: 01:07
English to Turkish
+ ...
|
|
|
| try support@kilgray | Jun 2, 2011 |
I think an email to support@kilgray would give a better chance of a reply than posting it on a forum Farkas
| | | | Michal Glowacki
Poland
Local time: 00:07
Member (2010)
English to Polish
+ ...
The deafening roar of crickets here suggests that it's time to lay this old myth of great MemoQ support to rest.
I can assure you this is not a myth. memoQ support guys often visit forums but if you really want their help - support@kilgray.com is the way to go. Alternatively, use the memoQ yahoo technical group, where you can place question that may be answered not only by a lot of advanced users but also by members of the memoQ support. I don't think that asking a question on a forum and blaiming support for not picking it up is fair. Just my two cents.
| | | | FarkasAndras
Local time: 00:07
English to Hungarian
+ ...
TOPIC STARTER
Thanks! Still, I'm afraid it's not totally clear to me how this procedure changes the TMX. Can you give me a short recipe such as "Change the o-tmf string to "XXX" and use <prop type="YYY"> instead of <prop type="Txt::Note">?
Note to the others: I did ask the company about this via email about two months ago and I'm still none the wiser.
| | | | | it appears to import | Jun 6, 2011 |
Hi András,
Sorry, we don't have a policy of frequently monitoring this forum, and for cases like these, support@kilgray.com is really the best place to go. Please do so if you want a quick reply. Thanks!
I checked your TMX and imported it into memoQ 4.5.73, and the note was imported indeed as a custom field. You can check it if you open Tools/Resource Console and edit the TM directly. There is a small inconvenienc... See more Hi András,
Sorry, we don't have a policy of frequently monitoring this forum, and for cases like these, support@kilgray.com is really the best place to go. Please do so if you want a quick reply. Thanks!
I checked your TMX and imported it into memoQ 4.5.73, and the note was imported indeed as a custom field. You can check it if you open Tools/Resource Console and edit the TM directly. There is a small inconvenience in the tool (it's intentional) -- you need to drag the metadata separator bar up a bit to see the note appear under Translation Results.
I hope this helps!
Best regards,
István ▲ Collapse
| | |
|
|
|
FarkasAndras
Local time: 00:07
English to Hungarian
+ ...
TOPIC STARTER
Thanks, I just checked (pretty belatedly, I admit) and the note field does get imported.
I'm sure it was hidden from view when I first tried the import, as you say.
Full Studio compatibility is still missing as far as I can tell, though.
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » TMX import/export troubles | Anycount & Translation Office 3000 |
|---|
Translation Office 3000
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info » |
| | LinguaCore |
|---|
AI Translation at Your Fingertips
The underlying LLM technology of LinguaCore offers AI translations of unprecedented quality. Quick and simple. Add a human linguistic review at the end for expert-level quality at a fraction of the cost and time.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
