eM Client Localization Tool manual

The aim of eM Client’s developers is to deliver a top e-mail client, that can be used comfortably in every user’s native language.

If you want to participate on improving eM Client’s localization or if you have any comments or suggestions, please feel free to contact us through our support e-mail.

How to use the Translation Tool

First, download the translation tool from here, unpack to a suitable directory and launch the executable file.

Click on ‘File’->’Open’ and select the xml file for translation (you can generate it by your self, but typically you receive the file from us with the most current localization). There is only one xml file for all the parts of eM Client (this was a bit different in the past).

XML files can be generated directly from binary files mailclient.exe and htmleditorcontrol.dll (stored in Program Files/eM Client) with function ‘File’->’Generate blank XML file from binary Folder’. You need to select a folder with eM Client's binary files (exe and dll files). It is typically your Program Files/eM Client folder.

Now you can start translating. The translation process is very simple. From the Main resource explorer panel on the left, select a resource file to translate. Then you can select the items one by one and type the translated texts into the ‘Translated String’ field.

When you are done with the translation please click on: ‘File’->’Save as’ and save the file with a filename you want.

Your work will be saved automatically to prevent data loss to autosave.xml file.

Generating and testing localization file

In the menu ‘File’ select ‘Generate resource DLLs to folder’. Then select a destination directory. You will need to copy generated dll files to a folder based on the target language (for example Program Files/eM Client/de for german localization). You will see the right folder name in a message box once the process is completed.

Now when you run eM Client you should be able to see your language in "settings".

Updating localization

Imagine you have localization which works, but it is a little outdated. You will need to get new resources from current binaries and merge it with your current localization. This task is very easy with our localization tool. Just go to main menu and select File -> Merge translated xml with newer binary folder. Tool will ask you for the newest translated xml and then for the most current binary folder (Program Files/eM Client). It will then perform all merge tasks automatically and you can update your localization to the newest version in a usual way.

Suggestions for comfortable work

In the menu ‘Operations’, there are several useful functions available with shortcuts. Please note that the ‘Replace all’ function has to be used very carefully.

The shortcut ctrl+N skips to another item in an appropriate resource file. This way you don’t have to move your hand from keyboard to mouse so often.

When you use ctrl+F and F3 shortcuts to search for specific words, then after editing a word, press ctrl+N or select another word to save your changes.

You do not have to translate strings that are the same in your language such as ‘&OK’ or ‘12:00'. The best way is to mark them with checkbox "Doesn't need to be translated".

Translation rules

  1. Unique shortcuts
    If an item contains ‘&’ symbol such as ‘&Save as’ or ‘Se&ttings’, the letter following the ‘&’ is used as a key shortcut ( the letter you use when navigating through menus using left Alt key). In your translated text therefore, you also have to specify one letter to be used as a shortcut. For example: ‘&File’ will become ‘&Archivo’ in Spanish or ‘&Datei’ in German.

    When selecting the letter for shortcut, you should adhere to the following rules:

    • The shortcut letter has to be unique within particular menu (or sub-menu) or tab (for forms with tabs). E.g. letter ‘o’ used for ‘&Open’ item in ‘File’ menu can be used for ‘C&opy to folder’ item in ‘Edit’ menu.
    • Some common menu commands (Open, Save etc.) have accustomed shortcuts within all applications - if you think some command is common across applications take a look at other software in your language and respect the shortcut used there.
    • For less common items try to use the first letter of words, if all first letters are taken (or unsuitable) use letters inside the words
    • Unsuitable letter for shortcuts are those that extend below the line of text (e.g. y, j, g, p) or those that are too narrow to be easily visible (i, l)
  2. Keep the suffix/prefix spaces
    Some words start or end with a space like ‘Empty trash and ‘ or ‘ receive messages.’

    This is because there is some other text that will be placed before or after the phrase and therefore the space has to be kept also in the translation file.
  3. Do not translate the international texts such as ‘&OK’ or ‘12:00'
  4. Translating listbox or combobox items
    When you encounter a listbox or combobox item such as: list_Actions_Actions.Items ‘ListViewItem: {move to folder}’ translate just the part in the brackets.
  5. Translating strings containing brackets {0}
    When you encounter a string that contains something like {0} or {1}, please leave this part of the string (brackets and the number inside) unchanged. These are parameters and will be replaced with relevant content when running.
  6. Inflections and other linguistic specialities
    Many languages use words in specific forms according to their meaning in a sentence, which makes correct translation from English quite difficult. If you suspect that your translation may need correction, please put a ‘*’ (star) character at the end of the word.

It is a good idea to have eM Client running during the translation so that you can take a look at the place that corresponds to the resource file you are working on. Doing so gives you the opportunity to see whether some linguistic issues might occur.

Please let us know if you would like to help us with the localization into any language.