Is it possible to generate an .xlf file from a .csv file?

Hello all,

I have written some code to convert an .xlf to a .csv file for the purpose of creating a language comparison spreadsheet (we need to compare two en-fr translations side-by-side) for a language reviewer that doesn't have access to SDL Trados.

In an effort to save time (in writing the reverse code), I was wondering if it's possible for SDL Trados to import the completed .csv files and then export it as a valid .xlf.

The csv file contains all the necessary tags, as well as the tag attributes for the <trans-unit id>... is it possible to create a filter to "teach" SDL Trados how to reassemble our .xlf file from the .csv?

Thank you.

Parents
  • 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!

    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?

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Thanks for your reply Paul.

    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.

Reply
  • Thanks for your reply Paul.

    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.

Children