Nathanael Fourie

Sounds as though a better process would be to simply correct the source file before you even create the project.  Why don't you do that?

Hi Paul

The files in the package are sdlxlif's. Not sure I can correct those...

Nathanael Fourie

Save the source, then recreate the project after you've corrected it.

What's the point in even correcting the source?  It can only be for two reasons:

1. you want clean TUs for your TM or
2. you want a decent source file

If you don't clean the source file then the clean TUs in your TM will be useless anyway as they won't match the file in the future if it gets updated, unless it gets cleaned properly before the project is created.  In my opinion it's a foolish way to work.

Thanks for your help Paul !

I agree, but in this case, I'm doing the prep work for the agency and they only have/supplied me with sdlxliffs.

My main prerogative is to kickstart the project with a clean source file, which would then enable me to end up with a clean TM.

I saved the source files, am cleaning them up now and will bring them into the project as new translatable source files.

That should work too, right?

Nathanael Fourie said:

I saved the source files, am cleaning them up now and will bring them into the project as new translatable source files.

That should work too, right?

In terms of technically working... then yes.  It's a better solution.  But what will you return to your client?  Ideally you'd speak to your client, explain the problem and ask them if you can create the project the project yourself and send them a TM plus your bilingual files, updated source and target.

Or, they recreate the package using your improved source.

Thanks. I see what you're saying...

I think communication is key here.

By the way, is there any reason why importing a Bilingual Review ("Updated from Bilingual Review") in which I made changes to the source column didn't do anything to the source segments in Trados?

Nathanael Fourie said:

By the way, is there any reason why importing a Bilingual Review ("Updated from Bilingual Review") in which I made changes to the source column didn't do anything to the source segments in Trados?

Yes.  Source has always been sacrosanct in Trados and the review is intended for the target only.  It's called bilingual because you see source and target, not because you can edit both.  If you think about how long it took to convince people we should allow edit source you'll get the point.

It's as important to make sure the source is well written and well prepared in a professional workflow as the translation itself.  If clients understood this they'd realise how much it would benefit them in an ongoing relationship and the whole localization process would be a lot smoother.  I think all professionals in the industry today owe it to themselves to educate their clients :-)

Nathanael Fourie said:

By the way, is there any reason why importing a Bilingual Review ("Updated from Bilingual Review") in which I made changes to the source column didn't do anything to the source segments in Trados?

Yes.  Source has always been sacrosanct in Trados and the review is intended for the target only.  It's called bilingual because you see source and target, not because you can edit both.  If you think about how long it took to convince people we should allow edit source you'll get the point.

It's as important to make sure the source is well written and well prepared in a professional workflow as the translation itself.  If clients understood this they'd realise how much it would benefit them in an ongoing relationship and the whole localization process would be a lot smoother.  I think all professionals in the industry today owe it to themselves to educate their clients :-)

Much appreciated, Paul !

Now I know for next time!