|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Very slow, slow translation - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
software@icg.es Member
|
Hi, we're evaluating sisulizer, we have an application with 50.000 words to translate, translation memory contains 33.000 words, the translation process take more than 600 min. (more than 10 hours) the machine is HP Compaq - AMD Athlon 64x2 Dual (2,19 Gh) - 3 Gb RAM - OS: XP SP2 Thanks
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, Do you use a local TM database or an external SQL-Server? Using an external SQL-Server can speed up the process significant. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, My TM based on internal DBISAM database engine contains above 10 000 strings and using it for project with 8 000 strings takes max 10 – 15 minutes, so time of your translation process with TM is too long, but it could have several reason: - Your PC environment. - Your TM database engine settings (type, locale, remote etc.). - Your TM contents could contain some wrong items. - Your project is very large. But this is very hard to figure without additional details. Workaround: Because your TM works very slow , you can use other method of auto-translation: - If your TM content is based on your project content, you don’t need use TM after source updates (re-scan), because Sisulizer automatically re-use existing translations for updated projects. - If your TM content is based on external localization resources (TMX, CSV files etc.), you can use "File" menu > "Import" feature instead TM. Sisulizer Import Wizard allows on very advanced customization of import process - If you already have localized targeted files (e.g. binary files etc.) you can use "Project" menu > "Import Translations from Localized files" or "File" menu > "Import". Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
software@icg.es Member
|
Using SQLServer database is faster. Now we have a problem, during translation if there is more than one tranlation , sisulizer ask us what translation use, but if we check "Delete all except selected", using SQLServer , say "Can not modify read only dataset" Thanks
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Thank you for your report. I’ve reproduced this issue with translation memory based on my MySQL server database. I’ll forward it to our R&D. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, Please un-check the setting Tools - Translation Engines - <your engine> Common Settings -> "Save all strings every time to the translation memory". If you use Sisulizer in the typical way you have to use its TM very, very seldom. You better transfer translations from one project to the other e.g. with File | Import. If you have e.g. a new build of your software please just store it at the same place the old version was stored and use Project - Scan for Changes to re-use translations. This has the huge advantage that Sisulizer can use the context where the string was stored. TM in contrast works "By Value". This might be a good choice for document translations with large strings. If you have short strings like in software localization, you: a) will have only a very few matches in contrast to document localization b) lack the use of the context. Software localization uses short sentences or even single words. Without context information in TM wrong translations, especially if you have so much strings as you have, will take place. These will be very hard to track down. Using TM in software localization is always the last option you should use. Sisulizer has TM support due to the demand of LSPs who insist to use something that works in document localization should also work with software localization. Some customers export the strings from Sisulizer Enterprise to Excel format, localize with Trados, and re-import the translated Excel file into Sisulizer. The downside is, that you will not have WYSIWYG. Large LSP nevertheless prefer that way. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello,Now we have a problem, during translation if there is more than one tranlation , sisulizer ask us what translation use, but if we check "Delete all except selected", using SQLServer , say "Can not modify read only dataset" This issue was fixed in build 289. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:45 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Very slow, slow translation | |
Sisulizer software localization tool - Three simple steps to localize
