Transit package does not export as translated from MemoQ
Thread poster: Ales Horak

Ales Horak  Identity Verified
Czech Republic
Local time: 07:06
Member (2009)
English to Czech
+ ...
Aug 17, 2015

Hello!

I have had a problem today - I exported a Transit package from MemoQ, the export was successful, but when I opened the package (pxf file) in Transit, the file was not translated.
Actually, I sent the txf file to the client first, which was very shameful as the package was untouched
Later, I exported it as a pxf file and realized that it was really not translated at all (although all segments in MemoQ were finished and confirmed).

It never happened before. Is there any solution to this? I had not enough time, so my only way was to import the tmx file to Transit and include it in the Reference material folder. The fuzzy matches from the TM worked well, but some segments required editing of the mark-ups (bold font) which took me more than 40 minutes (4500 words in total). Some wrong mark-ups were revealed after running the QA check too.

Thanks to anybody who has ever had the same experience!

Ales


Direct link Reply with quote
 

Andrea Muller  Identity Verified
United Kingdom
Local time: 06:06
English to German
+ ...
Export settings? Aug 17, 2015

I don't know if this is relevant, as I never worked with a transit package.

But I had the same thing recently when exporting a Studio package with the Export (dialog) option – the target text segments were empty. But it worked fine with the Export (stored path) option.


Direct link Reply with quote
 

ahartje
Portugal
Local time: 06:06
Member (2006)
English to German
+ ...
File's name Aug 17, 2015

Hello,

I experienced this problem 3 x within Transit packages. Each package included about 12-15 files, all completely translated except 1 file.

Shortly after we decovered the reason: the name/designation of the respective files showed some special German characters: ä, ü and ß. Since the TM saved all data, we renamed the files and translated them again.
Everything worked smoothly!

So check your file´s name and maybe you will find the motive...


Direct link Reply with quote
 

Ales Horak  Identity Verified
Czech Republic
Local time: 07:06
Member (2009)
English to Czech
+ ...
TOPIC STARTER
Thanks a lot! Aug 17, 2015

ahartje wrote:

Hello,

I experienced this problem 3 x within Transit packages. Each package included about 12-15 files, all completely translated except 1 file.

Shortly after we decovered the reason: the name/designation of the respective files showed some special German characters: ä, ü and ß. Since the TM saved all data, we renamed the files and translated them again.
Everything worked smoothly!

So check your file´s name and maybe you will find the motive...


I renamed, pre-translated and exported the original package and it worked

Thank you very much!


Direct link Reply with quote
 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Transit package does not export as translated from MemoQ

Advanced search






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 »
SDL MultiTerm 2017
Guarantee a unified, consistent and high-quality translation with terminology software by the industry leaders.

SDL MultiTerm 2017 allows translators to create one central location to store and manage multilingual terminology, and with SDL MultiTerm Extract 2017 you can automatically create term lists from your existing documentation to save time.

More info »



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