I can’t save strings from my project to Translation Memory. Why?

This issue is usually result of the following Translation Memory setting:
“Tools” menu -> “Translation Engines” -> “Common Settings” tab -> “Add strings if the status is greater or equal to”.

Translation Memory settings

So, when you use e.g. here “Complete” setting, Sisulizer saves to Translation Memory only strings with this status from your project, and Sisulizer doesn’t save to Translation Memory stings with lower statuses, that is, “For Review”, “Translated”, “Auto-translated” etc.. You can select three values for “Add strings if the status is greater or equal to” setting:

You can’t select statuses lover than “Translated”. It prevents saving to Translation memory not verified translations.

Hints:

  1. You can save translations from your project by:
    • “File” menu -> “Save to Translation Memory” -> selected Translation Memory. This option saves language pairs (original and translation language) for all languages in your project
    • “Column” menu -> “Save to Translation Memory” -> selected Translation Memory. This option saves language pair (original and translation language) for currently edited translation language in your project
  2. You needn’t open project for adding its contents to Translation Memory, because you can do it without project’s opening via “Tools” menu -> “Translation Engines” -> “Documents” tab. Just click on “+” button and select your Sisulizer project. You can also import to Translation Memory other file types with translations resources.
    Documents tab
    Sisulizer supports import to Translation Memory from following file types:

    • Borland Translation Repository file
    • Comma Separated Values file
    • EDICT Dictionary file
    • Excel files
    • Microsoft glossary files
    • Multilizer project files
    • Multilizer dictionary files
    • PO file pair
    • Regular expression defined text files
    • Sisulizer project files
    • TMX file
    • XLIFF file

    Wide range of supported file types allows you on using different translation resources. For example:

    • Microsoft repository files can give you access to rich translation resources matched with MS Windows standards
    • TMX (Translation Memory Exchange) file allows you import translations from all extended localization tools with implemented Translation Memory feature
    • XLIFF and Gettext platforms are often used on Linux platform, so you can use translations resources not available on Windows OS

    You can remove selected file at the any time from “Documents” tab. After removing item from this list, Sisulizer removes from Translation Memory all translations belong to removed file. So, if you would like remove only some items from Translation Memory, you needn’t clear all content of translation memory.

  3. When you save translations to Translation Memory  from project, translations are saved without country extension (sub-language), so you can use translations from Translation Memory e.g. for  both “German” language and for “German (Austria)” etc. If you import translations from external file via “Translation Engines” -> “Documents” tab, Sisulizer ask you about import of country extensions.
  4. Sisulizer can automatically save translations from project for removed unused items. This option allows you quickly restore translations, if you decide add again some items to your source file. This feature is by default enabled, but you can disable it via “Tools” menu -> “Translation Engines” -> “Common Settings” tab -> “Add unused strings to the translation memory”
    Unused strings setting in TM
  5. Information about saving to Translatiion  Memory (date, time, count of saved items, etc.) is displayed in “Output” pane.
    Output pane

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.

Comments

No comments yet.

Leave a comment

(required)

(required)


For spam filtering purposes, please copy the number 1625 to the field below: