Build 303 – implementing sub-languages settings to Translation Memory management
Build 303 comes with a new set of features related to sub-languages using with translation memories. Up to build 302 Sisulizer saved items to translation memory always as neutral language items (without country extension), for example, strings from column “German (Switzerland)” were saved to translation memory as “German” entries. From build 303 Sisulizer saves also the country extensions of saved languages to translation memory. Of course, this feature comes with a set of settings to customize behavior of sub-languages support with Translation Memory. These user interface items are grouped in new “Translate settings” tab of selected translation memory’s management dialog (“Tools” menu -> “Translation Engines” menu item -> selected translation memory in left panel of dialog).
Here in “Language match” section you find the following check boxes:
- Use country neutral translations when translating a sub language – If checked Sisulizer uses also country neutral translations in the case there is no country specific translation. For example if this is checked and you are translating a German (Switzerland) column and there is no translation having de-CH language code but there is a translation having de language code then Sisulizer will use it.
- Use country specific translations when translating the main language – If checked Sisulizer uses also country specific translations in the case there is no country neutral translations. For example if this is checked and you are translating a German column and there is not translation having de language code but there is a translation having German (Switzerland) language code then Sisulizer will use it.
- Use translations of the same language but different country – If checked Sisulizer uses also translations of the same language but different country in the case there is no country specific translations.
For example if this is checked and you are translating a German (Austria) column and there is not translation having de-AT language code but there is a translation having German (Switzerland) language code then Sisulizer will use it.
Of course, you can use different combinations of checked/unchecked above options. Additionally, you can use a different setting for each of your translation memories added to Sisulizer, so new sub-language support for translation memories is very customizable and flexible.
Recently our developers have added also “Import settings” tab to Translation Memory management dialog (“Tools” menu -> “Translation Engines” menu item -> selected translation memory in left panel of dialog), where you can set default import settings for selected Translation Memory.
Here you find the following settings:
- Import also those strings where the translated value equals to the original value – If checked Sisulizer imports the string even if it equals to the original value. If unchecked Sisulizer does not import string if it equals to the original value.
- Ignore country part in the language codes – If checked Sisulizer removes the country part from the language code when importing. For example if the import file contains German (Germany) data, the imported string will have German language property instead of German (Germany). This setting is related to translate settings described above.
- Set the status of imported string to – Specifies the status value that will be the initial status of the imported strings in the translation memory.
- Do not import strings whose length in characters is greater than – Sets the maximum length for imported strings. If a string is longer than that it will not be imported. If the value is 0 all string are imported.
You can import translations from external files (e.g. SLP, TMX, CSV, XLIFF, etc.) via “Documents” tab of Translation Memory management dialog (“Tools” menu -> “Translation Engines” menu item -> selected translation memory in left panel of dialog). You can find some additional information about import to Translation Memory in this article on our blog. When you import document, Sisulizer opens Import Wizard where you can adapt all above described import settings.
Janusz
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.
What are a plas for a translation memory editor so you can change the values in the TM?