TMX import/export troubles
Thread poster: FarkasAndras

FarkasAndras  Identity Verified
Local time: 04:31
English to Hungarian
+ ...
Apr 19, 2011

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  Identity Verified
Local time: 04:31
English to Hungarian
+ ...
TOPIC STARTER
No takers? Apr 26, 2011

Any comment from Kilgray?

 

FarkasAndras  Identity Verified
Local time: 04:31
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  Identity Verified
Turkey
Local time: 05:31
Member (2006)
English to Turkish
+ ...
TMX import DVX>MemoQ was not easy Jun 1, 2011

Some people do not mind about additional fields and some others try to find a solution. For a similar problem see http://tech.groups.yahoo.com/group/memoQ/message/19632

Selcuk


 

rmackay
Local time: 03:31
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  Identity Verified
Poland
Local time: 04:31
Member (2010)
English to Polish
+ ...
Not a myth Jun 2, 2011


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  Identity Verified
Local time: 04:31
English to Hungarian
+ ...
TOPIC STARTER
Details Jun 6, 2011

Selcuk Akyuz wrote:

Some people do not mind about additional fields and some others try to find a solution. For a similar problem see http://tech.groups.yahoo.com/group/memoQ/message/19632

Selcuk

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.


 

István Lengyel
Hungary
Local time: 04:31
English to Hungarian
+ ...
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  Identity Verified
Local time: 04:31
English to Hungarian
+ ...
TOPIC STARTER
Works Jul 11, 2011

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

Advanced search






SDL Trados Studio 2019 Freelance
The leading translation software used by over 250,000 translators.

SDL Trados Studio 2019 has evolved to bring translators a brand new experience. Designed with user experience at its core, Studio 2019 transforms how new users get up and running, helps experienced users make the most of the powerful features.

More info »
CafeTran Espresso
You've never met a CAT tool this clever!

Translate faster & easier, using a sophisticated CAT tool built by a translator / developer. Accept jobs from clients who use SDL Trados, MemoQ, Wordfast & major CAT tools. Download and start using CafeTran Espresso -- for free

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search