Hi again,

I have tried to retranslate the source file with a different name and got the same message.

This time I even got two error messages

I look forward to your help.

Thanks again,

Cynthia

Hi Cynthia Gandeborn

It's a shame it's the weekend or I'm sure someone from SDL would have replied to you by now.

The errors you're getting are indicative of an error in the Word document itself.

As it was created from a PDF (PDF gets converted to Word when a project is created from a PDF) then it could be that the process of the file creation caused some sort of issue that didn't prevent the translation file (sdlxliff) being created but does prevent saving the Target file to Word.

Alternatively, it could be that a 'tag error', for example, has occurred during translation, causing the same issue.

Have you verified the file? I was going to send you a link to the documentation page that covers tag verification which is the process most likely to find an error in an SDLXLIFF target segment in relation to the source, that could prevent Target file creation. It seems the site is down.

So, with your file open in the Editor window, click on F8 and if you still have the default settings in Studio, it will automatically run a tag check on the file.

This may indicate a tag of some sort that hasn't been copied over from source to target, that could cause this issue.

I doubt it, but it's a starting point...

All the best,

Ali

Hi Alison,

Many thanks for your response.

I tried your suggestion but there was no change. 

Thanks anyway.

Best regards,

Cynthia

Hi Cynthia Gandeborn 

OK, another old trick is to try saving the Source Word file to a different version. So, if it's .docx then save it as a .doc and vice versa.

Create a new project with that file but set to 'analyse only' i.e. don't pretranslate.

Open the Word based sdlxliff then before you translate it, first try saving to Target via File>Save As Target.

If this fails, it is the source file that is faulty rather than the translation process. You need to open the Word file again and look for anything that might be causing the issue.

It that works, then p/retranslate it via batch tasks using a TM based on the first translation.

Then try Save as Target again. If that works, you've solved the problem.

If it doesn't then it's the translation process that has done something to cause the error message.

Let me know if any of the above works.

All the best,

Ali

Hi Alison,

Thanks for following up

I am on my 4th retranslation trial now...with very little sleep.

I have actually had a look at some old posts and deactivated the File Type word 2007-2016 in Trados options before translating. With 88% repopulated, I kept going saving the target file at several stages, while keeping a copy (just in case), and was able to open the target document until I got close to 95% completion. 

I have thrown the towel as time is ticking and am working with the last target file I was able to open. I had initially managed to finish and proofread the original job on Trados and can still open it on editor view, so I will read through and copy-paste the 5 or 6% I missed on the final try while I work on the formatting as well.

BTW, I thought that since I hadn't installed the latest service pack (as I was in the middle of a project), it could be time to do it and possibly sort the problem, but when trying to install it I got an error message and left it as it was until I send away the finished work.

Best regards,

Cynthia

Hi Cynthia Gandeborn

"...with very little sleep..." I know that feeling, you have my sympathy!

Deactivating file types till you find the one that works is a very sensible idea... It would probably have been my next suggestion. I'm so glad to read that through trial and error you've found a workaround that worked, even if not completely, so you can deliver the file in time.

Well done!

Regarding installing the latest service pack, it is always wiser to wait until you've finished the projects in hand before updating...

Then, if Studio misbehaves in any way you can run a  Windows Repair on Studio and MultiTerm - don't forget if you install an upgrade/update for Studio that you need to open MultiTerm and check for updates there too (via the Help>Check for Updates ribbon).

I hope that your problem does not repeat itself and that you continue to learn by doing and that it means you enjoy using SDL Studio & MultiTerm.

All the best,

Ali

Hi Alison,

Many thanks for your encouragement and for your support.

I will keep going anyway I can to deliver on time and wait until I have done so before any updates ;)

Very best wishes,

Cynthia

Hi Cynthia Gandeborn

I hope you met your deadline OK. Well done for being so dedicated as to push through for the end result. I bet your final Target version is better than the original source version you were sent!

All the best,

Ali

Hi Alison,

My deadline is on Friday, but I am not there yet. Thanks for asking :) 

I am still proofreading and copy pasting, while reformatting numbered lists and footnotes that Trados tends to convert from PDFs as flowing text. All in all about 100 pages of headaches. If anything, I will be a word processor master at the end of the week. ;)

Best wishes,

Cynthia

Hi Cynthia Gandeborn

If I'm working on a PDF-based translation, I usually open the source Word file created by the project creation process and work on that before translation then create a new project with it. 

It is easier to compare it to the source PDF in the source language and get the layout tidy before translation.

As I described earlier in this thread, sometimes doing this will also iron out potential problems that might prevent saving to Target...

I would say it's an essential way to smooth the production of a good Target file.

Good luck with the work!

All the best,

Ali