The first message implies that the "source file" does not match that in the project. Try adding the Excel as source file. Translate this using the existing TM - there should be a good match.

The first message implies that the "source file" does not match that in the project. Try adding the Excel as source file. Translate this using the existing TM - there should be a good match.

Hi Anthony Rudd  & Susan Murphy Lamprecht

Good advice from Anthony as it's most likely that the temp files have been corrupted somehow and now Studio can't find what it needs to save target. Can happen if you leave Studio running for long periods of time, or if you have a security check running whicle Studio is open. Depends on your security software and how it's configured.

But I wanted to add that you could change the process in Studio 2017 to be this as there is no need to switch to the source language:

Select the current project -> Select "Files"
Select "Add files" (select the Excel)
Select "Batch tasks"
Select "Prepare" or "Prepare without project TM" as appropriate
this "translates" your Excel file with the existing TM and should produce a "good" result. Hopeful you should need to make only a few minor changes.

If you have Studio 2019 then you only do this:

Select the current project -> Select "Files"
Select "Update file" (select the Excel)
This "translates" your Excel file with Perfect Match and the existing TM and should produce a "good" result. Hopeful you should need to make only a few minor changes.

Regards

Paul

... so long as she has the (corrected?) source Excel file ... she may not have received that with the package... and she hasn't been able to save as Source either...

Hi Alison Field 

I was referring to the original source file, not a corrected one. If she's working with a package that doesn't have the source file AND it was not embedded into the SDLXLIFF because it was larger than the settings used when the project was created then the only way to deal with this is to ask for the source file from the client.

If the source file was embedded and just not included separately then your solution to "try" and save the source file might work. But my guess would be that if the target won't save then the source probably won't either.

 All good ideas though... perhaps Susan Murphy Lamprecht will advise how this was solved and put our minds at rest.

I have a feeling the problem is not related to a missing embedded file, neither a missing Excel source.  The message suggests a corruption as there was a mismatch so it probably found something to go on and then failed to make it work.

OK, thanks Paul Filkin

I thought that if the source file wouldn't save, it would indicate that the source file contained content that needed removing or smoothing, as with Word files.

Sorry I complicated matters...

All the best,

Ali :)

Hi Susan Murphy Lamprecht

That's excellent news Susan, thanks for sharing that. As it came to you as a package, the Project Manager was happy to receive a package back. Problem solved!

Most clients are happy with that, or even with just the SDLXLIFF file, and I only save to target if I have the appropriate software to read the file I've been working on. 

Further to our discussion on tag verification yesterday when I sent you this link: Verifying translations

Here is where you access the settings in Studio for the verification processes described, under Project settings:

(Number Verifier is an extra plug-in that I downloaded from the SDL AppStore)

You can set what you want to check and how you want to check it, which makes for a better translation.

You can run the verification then with the sdlxliff file open in Studio, by pressing F8 or clicking on Verify on the Review tab of Studio.

Have a super day!

All the best

Ali :)