|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page:   1 2 |
|
|||||||||||||||
| Shared translation engine - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Christine Member
|
Dear Janusz, The Translation Engines page is a general setting for all projects or is it related to a project? I mean I can open this page without opening a project first, so it cannot really be related to a project? Is the Embedded TMS from Translation Engines page different for each project or the same? If it is the same, this might be the cause why it reoccurs? (Because it might be still used by another project?) It did not even work to delete the Embedded TMS files in Windows explorer, the files also reoccur. The files are generated in the very moment when the Translation Engines page is opened (without opening a project first), not when a project is loaded. So this behavior does not seem to be related to projects. Best regards, Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
Dear Janusz, we are working with the shared TMS now for a while, but it does not seem to be working as expected. I would have thought the TMS is used each time for all untranslated strings when I scan the project or if I use the command "Translate with TMS". I expected the results would be similar to importing a project file, so that I do not need to manually import project files anymore. However, I started a new project, and auto-translation did not find many matches. I then used the Import feature, and, voila, 861 translations have been imported. Of course, the imported project uses the same TMS than the new project. Could you please explain to me what the difference is between import and TMS and how I could improve the auto-translation with TMS? Thanks, Christine
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello Christine, During import, Sisulizer try use all translations saved to imported project, while to translation memory you can save only translations with "Translated" status or higher. Of course, it depend on "Tools" menu > "Translation Engines" > (selected TM) > "Common settings" tab > "Add string if the status is greater or equal to" setting. Here you can select "Translated", "For Review" or "Complete" statuses, but not lower. This limitation was implemented, because it can prevent saving to translation memory incorrectly and not reviewed translations. I think it could be reason of your issue. You should check translations in your projects and change statuses for correct translations from "Best Guess" and "Auto translated" statuses to status matched with "Add string if the status is greater or equal to" setting, next save your translations to translation memory again. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
Dear Janusz, sorry, I need to bring up this topic again. 1.) I scanned a resource for changes. => TMS did not find much (or any?) translations for the New strings. 2.) I then used the command "Translate Using Translation Engine" and there was at least one string that was Auto-Translated now. => So it seems that the TMS is not used during the automatic Auto-Translation process of New strings during the scan. I guess that Sisulizer looked only for the Duplicate strings in the project. Did I miss an option? (We are still using build 291) Best regards, Christine
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello Christine,=> So it seems that the TMS is not used during the automatic Auto-Translation process of New strings during the scan. Exactly. Sisulizer doesn't use translation memory during scan. Translation memory can be called manually in Sisulizer's UI or via SLMake. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Dear Christine, Please remember that TMs had been made document localization in mind. They do not store a context. Using that automatically would be a bit risky. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:44 pm | Page: 1 2 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Shared translation engine | |
Sisulizer software localization tool - Three simple steps to localize
