Transit XV Export Error
Thread poster: Egidijus Slepetys
Egidijus Slepetys
Egidijus Slepetys  Identity Verified
Local time: 00:07
German to Lithuanian
Mar 11, 2011

This is how it looks:

"[name of the doc file] : Lithuanian : [Filtering] Filter error: XML format violation. (Line: 128 Position: 33)"

(and around 10 times the same line in the error log)


This is a MS-Word file, a manual, but clean, not after OCR. Import process went as usual, without errors.

I have translated only a couple of sentences and tried to export to see the results.
No export file were created.

What is a "lin
... See more
This is how it looks:

"[name of the doc file] : Lithuanian : [Filtering] Filter error: XML format violation. (Line: 128 Position: 33)"

(and around 10 times the same line in the error log)


This is a MS-Word file, a manual, but clean, not after OCR. Import process went as usual, without errors.

I have translated only a couple of sentences and tried to export to see the results.
No export file were created.

What is a "line"? I checked the line 128 in Transit and in Word - nothing suspicious.

Any ideas? I would be very grateful for any suggestion.
Collapse


 
Brand Localization
Brand Localization
Egypt
Local time: 00:07
German to Arabic
+ ...
Workaround Mar 11, 2011

As long as you already checked the tags on that line, try this workaround:

Use the translated language pair as reference material for a new project.

I think, this will help you overcoming this error and export the file.

Best regards

ATT


 
Egidijus Slepetys
Egidijus Slepetys  Identity Verified
Local time: 00:07
German to Lithuanian
TOPIC STARTER
Transit never dissapoints :) Mar 11, 2011

Thank you ATT!

Your suggestion inspired me to play a little bit around with importing/exporting.

The reason for the fail export was like this:

I actually have a project based on a previous one.
So importing process pretranslates the new file.
After importing, if I do "Check Formatting Codes", the Check is completed without errors - but the export fails.

What I did: with filters I did "Show segments with state -> Translated" and I di
... See more
Thank you ATT!

Your suggestion inspired me to play a little bit around with importing/exporting.

The reason for the fail export was like this:

I actually have a project based on a previous one.
So importing process pretranslates the new file.
After importing, if I do "Check Formatting Codes", the Check is completed without errors - but the export fails.

What I did: with filters I did "Show segments with state -> Translated" and I did a quick "Processing step -> Check 1". After that I did "Check Formatting Codes" again and there were found some tagging errors ("wrong order of tags..." without actual text). I corrected them simply restoring source and ---- voilà - export is working!

I even would not have noticed this after translating the whole file, because Transit does it's job always very well till the end!

Thanks again!
Collapse


 
Brand Localization
Brand Localization
Egypt
Local time: 00:07
German to Arabic
+ ...
Ende gut, alles gut! Mar 11, 2011

Hi Egidijus,

Nice, that you could find out the problem and overcome it.

As you said, Transit is a clever TM system.
Having used many TMs, I can assure, that Transit is the best for many reasons.

As long as, Transit couldn't export because of a tag, then it is a serious one.
In many cases, it can still export your file, if the tag errors are minor ones.

Best regards
ATT


 
damaged Word files Mar 25, 2011

Hi,

mainly this error message comes because of a tag error, but to replenish this; sometimes this even comes even without (!) a pretranslation or touching the fresh imported language pair.

In my cases this was because of "damaged" DOC-files. You can only see this, if you open the DOC file from word directly be opening this file with the "open and repair" function. (hidden beside the "open" button in the small arrow of word...)

This damaged doc file (came di
... See more
Hi,

mainly this error message comes because of a tag error, but to replenish this; sometimes this even comes even without (!) a pretranslation or touching the fresh imported language pair.

In my cases this was because of "damaged" DOC-files. You can only see this, if you open the DOC file from word directly be opening this file with the "open and repair" function. (hidden beside the "open" button in the small arrow of word...)

This damaged doc file (came directly from customer) made me mad one day...

regards,
Richwood
Collapse


 


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

Moderator(s) of this forum
Maya Gorgoshidze[Call to this topic]

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

Transit XV Export Error






TM-Town
Manage your TMs and Terms ... and boost your translation business

Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.

More info »
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 »