Cristiana Cocco

The Glossary Converter is probably the easiest way to do this.  If you're getting errors it might be better to investigate the files you are converting as the problem may be related to that.

But if you want another way to avoid external tools and rely on your Excel file completely then just use Excel!  For example, take this Excel:

Rewrite it like this:

All I do is this:

1. remove the top row
2. insert a column to the left
3. insert four rows at the top
4. Add the header for the file into the space for the four rows
5. cell A1: "TU ID" as a title for the column
6. cell B1: source language for the TMX
7. cell C1: target language for the TMX
8. Then for each row with the language pairs I use this forumula:
   ="<tu tuid="""&A5&""">"&"<tuv xml:lang="&""""&$B$1&""""&"><seg>"&B5&"</seg></tuv>"&"<tuv xml:lang="&""""&$C$1&""""&"><seg>"&C5&"</seg></tuv>"&"</tu>"
   All that does is concatenate a few values and some text... not as complex as it looks.
9. At the very end of the list of terms add the end of file tags

That's it.  If I now copy the cells F1 to the end, in this example F1 -> F13, into a text file I get this:

That file imports into Studio without any problems.  So once you have this set up it's a simple copy paste operation every time and the TMX will always only be as good as the quality of the content in your Excel glossary.

I put the example I used here so you have a head start.  I'm pretty sure many users did something like this before we had all these conversion tools so perhaps a little back to basics will be useful.

tmx_in_excel.xlsx

Thank you very much Paul!