Glossary file format(s) for use with Google Cloud Translation

[legrandtimonier]

Hello,

I'm interested to know whether it is possible to use a .tmx file as a  source/target-language bilingual glossary with Google Cloud Translation (Advanced) instead of a .csv file. The reason I ask is that when running my program in its early stage of development I got back an error message stating that only a .csv file is the accepted. However,  in a video I happened upon recently, produced by the Google Cloud team, I definitely heard at one point that .tmx was also an accepted format. Does anyone know the definitive answer to this question? Thanks in advance. Regards

[legrandtimonier]

Hi,

Many thanks for this response. The problem is that in an official Google
Cloud video posted around two years ago, the Google presenter states
clearly at around 3 min 10 seconds into the video that it's possible to use
not only .CSV files, but .tmx as well. I've seen similar mentions of this
elsewhere.

The official Google video is available, by the way, at:

https://youtbe.be/A3knNbGfXh4

Regards,

Gary

[ety]

Hello! Thanks for the question. The file format depends on the glossary type: https://cloud.google.com/translate/docs/advanced/glossary#format-glossary. For unidirectional glossaries, you can use TMX or CSV. Equivalent term sets require CSV.

[legrandtimonier]

Hi,

Thanks for getting back to me with this good news. 🙂 I will be
translating texts in a single direction (for now), and so I will start with
the .tmx files, which are much easier to deal with in my scenario. Within
the javascript itself is there anything besides the .tmx that must be added
to the code to tell it to use .tmx? or do I simply provide a .tmx file in
the same subdirectory of my bucket and change the extension from .csv to
.tmx?

Regards

[ety]

I believe you'll need to specify LanguageCodePair instead of LanguageCodesSet. After that, pointing to your TMX file should work.

[legrandtimonier]

Many thanks. That was what I needed to know.

Regards