We use this terminology, because with “Translation Engines” interface you can manage not only your Translation Memories, but also external machine translator software and services. Below is short description of these features and some hints.
During installation, Sisulizer installs its Translation Memory based on DBISAM engine (named “Embedded”). This Translation Memory is empty, and if you would like to use this feature, you need first to fill this Translation Memory with verified, high quality translations from Sisulizer’s projects or from external resources. More information about saving and import translations to Translations Memory you can find in other article on our blog. Initially, with Sisulizer is installed only one Translation Memory, but you can add to Sisulizer many different Translation Memories, e.g. for selected projects group, language pairs etc. These Translation Memories can be based on different database engines. Below is a list of supported databases:
- SQL Server
If you have already added Interbase translation memory, Firebird will be disabled and vice versa. This is because they both can not be active at the same time.
Machine translator services
- Google Translate
- Microsoft Translator
Google was added to build 280, Microsoft to build 284. Both services are available in in Sisulizer Enterprise edition only. Currently, Google Translate is available for 34 languages, Microsoft Translator for 22 languages. Both Google and Microsoft are installed by default with Sisulizer, and after installation are immediately ready to use. Of course, using of these features requires Internet connection, so if you can’t use Google or Microsoft translation services, you should check your firewall settings, proxy settings (if you use proxy) or ask your network admin about checking your network connections (if you work in a network).
Machine translator software
You can add to Translation Engines also external machine translation software, but first you should install these software on your PC. Currently Sisulizer supports following third party machine translator software:
Translation Engines management
You can manage your all translation engines via “Tools” menu -> “Translations Engines”.
Here you can:
- Add new translations engine, by click on “+” button
- Remove selected translations engine, by click on “x” button
- Change order of translation engines. This order is used in translation process (described below)
- Edit settings of selected translation engine, e.g. disable or enable it etc.. You can also create backups of selected Translation Memory, restore this backup, export contents of Translation memory to external file.
Below is example screenshot from dialog of adding new translation engine:
You can also disable selected translation engine in source properties ->”Engines” tab. This setting is applied only to selected source in project.
Using of Translation Engines
You can use Translation Engines feature via:
- Column menu -> Translate Using of Translation Engine ->translation engines submenu
- Translation sheet -> header’s context menu of selected translation column ->Translate Using of Translation Engine ->translation engines submenu
- Translation sheet -> context menu of selected cell(s) in translation column -> “Translate” -> “Translate Using of Translation Engine” -> translation engines submenu
Mentioned above submenu contains following items:
- “Use all enabled translation engines” – it use all enabled translation engines with order from Translation Engines dialog, that is, Sisulizer first search translations with top translation engine, if this translation engine doesn’t contain matched translation, Sisulizer use next translation engine on list, etc.
- List of all enabled translation engines – you can select desired translation engine
If you disable selected translation engine in source properties, translation engine is still visible in submenu, but this translation engine is separated from other items on list by separator. Additional, in submenu appears also new item – “Use all translation engines”. If you disable translation engine in “Translation engines” dialog, this item is invisible in submenu.
Below is example screenshot from context menu of translation sheet.
- If you are novice and you are evaluating Sisulizer, probably your Translation Memory is empty, but in this case you can use Google or Microsoft services. Quality of Google and Microsoft translation services is not very high, or at least worse than human native speaker translators, but it can be good point for beginning your work with Sisulizer. After verification you can save results to your Translation Memory for future using.
- I recommend using Google or Microsoft services only for current view or for selected cells via context menu, because:
- it gives you better control of results, since using auto-translation feature for whole project can increase possibility of overlooking incorrectly translations
- using these features for whole project sends to Google and Microsoft lot of requests at short time and it (especially for slow network connections) can cause timeout errors
- if your project is really very big, auto-translation operation can take lot of time (especially for slow network connections).
- While Sisulizer has interfaces to machine translation it is highly recommended to use a human translator who is a native speaker. Only a professional translator will produce the translation quality you need to enlarge your markets.
- If you have Sisulizer Enterprise Edition, you can even create shared Translation Memory (based on SQL related engines), and your translators e.g. from China, Germany and Spain can work remotely with these same translations resources.