Of course, Sisulizer allows to re-use translations from your already existing projects in a new project. You can do it in the following ways:
- Directly import from other Sisulizer projects
- Using of Translation Memory feature
Each method has some faults and advantages, and choosing most appropriated method depends on your needs. Below are short descriptions of both methods.
Directly import from another Sisulizer project:
This feature is available via “File” menu ->”Import”. This solution allows:
- Import translations only from selected projects, while Translation Memory use always all translations from all projects saved to Translation Memory
- Import translations for more languages in one operation, while Translation Memory in one operation can translate only currently edited language. You can select desired languages in “Import Wizard Languages” step of Import Wizard. Sisulizer display in this step only matched languages (languages existed in both projects),
- Sisulizer’s import feature is very customizable and you can set up in “Import Wizard – Options” following options:
- You can select import method (“By context”, “By value”, “By context first then by value”). Translation memory use always “By value” setting, while using “By context” method can give you more precise translation in some cases.
- Import also those items where the translated value equals to the original value
- Import also those items that are empty
- Import only if context and original value match
- Import translation statuses
- Import comments
Generally, directly import allows you the fine-tuning of imported contents, and in a result you can get more precise translations.
Using the Translation Memory feature
This feature is available via “Column” menu -> “Translate Using Translate Engine” -> Translation Engines submenu or via Translation Sheet context menu -> “Translate” -> “Translate Using Translate Engine” -> Translation Engines submenu. This solution allows you to:
- Using translations from all your projects saved to Translation Memory by one click, without browsing your HDD, while for directly import you need repeat all Import Wizard steps for each selected project
- You can use one selected Translation Memory, all enabled Translation Memories/Engines or Translation Memories/Engines (also disabled) via Translate Using Translate Engine submenu. So this solution allows you customize contents used in “Translate Using Translate Engine” operation
- You can select scope of auto-translate operation, that is, you can use Translation Memory for whole language column (Column menu), limit scope to current view or selected cells (using via sheet context menu), while import feature works always for whole project
- Translation Memory ignore country extensions, while Import feature require matched country extensions for imported languages
- You can use remote Translation memory (Enterprise Edition), so using of translation resources isn’t limited to your PC
Generally Translation Memory is more easy to use (you needn’t go through wizard steps etc.), usually it gives more translations, but import feature can give you more precise translations with better quality.
1. Of course, you can use combination of both solutions. Sometimes, I use following combination for new projects:
- First I use Import feature (when new project contains similar files to source files from other project I use “By context” import method). Import gives me better control on re-using of existing translation, and for this reason I can influence the quality of imported items
- Next I use my internal Translation Memory
- Then I use external translation engine services, that is, Google Translate or Microsoft Translator, but items translated by these features should be verified, because both services doesn’t give high quality translations.
You can use different translation statuses for each auto-translation/import operation, for example “Translated” for imported items, “Auto translated” for items translated with your Translation Memory, and “Best guess” for items translated e.g. with Google service. It allows you to separate items auto-translated in different ways and it probably make an easy potential verification of these translations. You can change status imported/auto-translated item here: “Tools” menu -> “General” -> “Translations” tab -> “Change translation status” section -> “When importing”.
2. Because Import feature is very customizable, you can even use this feature for merging two Sisulizer projects. It was described in other article on our blog.
3. You can store in one Translation Memory all resources from all your projects. So it allows you on easy, centralized managing all your verified translations. But of course, uou can create many, different Translation Memories for specified purposes e.g. for specified projects, languages, branches. Using this solution maybe require some effort, but it can be flexible and useful solution. You can learn more about managing many Translation Memories in this article on our blog.
4. If you like to import translations for this same language, but with not matched country extensions, you can import it to Translation Memory, and next use these translations via Translation Memory, because import to Translation Memory can ignore country extension. It was described in this article on our blog.
5. If you use import with “By context” method, you can next use “Translate Duplicate” feature (via Column menu or sheet context menu), because it can give you new translated items. You can learn about “Translate Duplicate” feature using in this article on our blog.