• Download the spreadsheet for your language by clicking on the relevant code.
  • Column A is the name of the object. It might give a hint on how to translate: if it's a button, you may want to keep the text short, while a tooltip has some more space
  • Column B is the source language (always English). If it has a blue background, the item was translated already, but needs review because the source has changed. This could just be a fixed typo, but also a more fundamental change in functionality
  • Column C is where the translations go. If it has a green background, translation is required
  • Column D sometimes contains notes if the source text looks a bit cryptic
  • The only translations are from column B to C, do not modify or translate Column A

   Previewing your changes
You can verify how your changes look in the converter (version 6.2 or later required):
  • Download the Resource Converter here and unpack it.
  • Run it, it should open a window with brief instructions
  • Drag and drop the xlsx file with your translation: it should create a txt file for the same locale (e.g. de.xlsx => de.txt)
  • Go to the localisation folder of your Glossary Converter, by default "C:\Program Files (x86)\SDL OpenExchange\Glossary Converter\Resources\strings"
  • Back up the txt file in that folder
  • Copy your translated txt in the strings folder
  • Restart the Glossary Converter
If you directly want to edit the txt, DO NOT USE Excel. It is complete rubbish at handling line breaks in cells and will mess up the resource file. Libre Office or a text editor are much better at that.

   Language files