Shawn Connelly

Shawn Connelly said:

I was wondering if it's possible for SDL Trados to import the completed .csv files and then export it as a valid .xlf.

Yes of course... anyt... most... things are possible!

Shawn Connelly said:

In an effort to save time (in writing the reverse code)

You may find it'll be less time to write the reverse code.  If you want to do this in Studio then you'll have to write a routine to import your CSV and update the Studio project.  This will not be trivial, especially compared to the simple transformation you have already written.

Perhaps it would be easier to use the export for bilingual review so your reviewer can review in Word instead?

Shawn Connelly

Shawn Connelly said:

I was wondering if it's possible for SDL Trados to import the completed .csv files and then export it as a valid .xlf.

Yes of course... anyt... most... things are possible!

Shawn Connelly said:

In an effort to save time (in writing the reverse code)

You may find it'll be less time to write the reverse code.  If you want to do this in Studio then you'll have to write a routine to import your CSV and update the Studio project.  This will not be trivial, especially compared to the simple transformation you have already written.

Perhaps it would be easier to use the export for bilingual review so your reviewer can review in Word instead?

Thanks for your reply Paul.

Paul said:

Perhaps it would be easier to use the export for bilingual review so your reviewer can review in Word instead?

The spreadsheet is pretty "complex" with vlookups, etc. It's a pretty unique situation where we have to compare two sets of translation opinions side-by-side. The intent is to create a difference sheet with the overall accepted strings (or segments) and then convert back to an .xlf for translation memory updating. I wrote the java code to convert our .xlf along with all the important parts, with the intention of writing code to revert back to .xlf. In some ways, the code wasn't trivial because I needed to deal with double-xml encoding. If it sounds convoluted, it is! But it is a unique situation... a kind of one-time only issue because our new partner doesn't like our current translations.

As I experiment with SDL Trados, it seems to be feature-rich... I just thought that I could more easily assemble a quick filter to generate an xlf from the csv.

Shawn Connelly

We do have a plugin to export to Excel that could have saved you the initial task perhaps?

https://appstore.sdl.com/language/app/export-to-excel/532/

That is opensource too so you could perhaps expand it to get an Excel exactly as you'd like it?

https://github.com/sdl/Sdl-Community/tree/master/Export%20to%20Excel

Import is another matter and it really isn't trivial.  But we do have examples of where we have done imports before for other formats and these might help.  In fact you could, if you were inclined, adapt this one to use Excel rather than XLIFF and then you'd even have a managed Export/Import process:

https://github.com/sdl/Sdl-Community/tree/master/XLIFF.Manager

Relates to this one:

https://appstore.sdl.com/language/app/xliff-manager-for-sdl-trados-studio/1099/

Thank you again Paul. I appreciate your detailed replies.