|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Translation Engines - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
drungrin Member
|
How about sisulizer supporting a custom translation engine? Ex: a ActiveX object that implements a interface or... A webservice that implements a interface. Thus, the developer (sisulizer users are potentially developers) can make his own translation engine. It can be something simple like ITranslationEngine = interface(IInvokable) function Translate(FromLangId, ToLangId: Integer; const Text: String): String; end;
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Sisulizer doesn’t support custom software solution as translation engines. You don’t need any custom tools, because you could create custom extended system only with Sisulizer, or Sisulizer with external database e.g. MySQL or SQL Server without additional programming job. Sisulizer supports two different types of translation engines: 1. Machine translator software. Currently Sisulizer supports following third party machine translator software: - Seram - WorldLingo 2. Translation memory. Translation Memory is smart database system where you could save translations from your project, and next re-use these translations in new projects. You could also import to Translation Memory external files with translations resources e.g. Microsoft and Borland repository files, or to import via TMX file Translation Memories contents of other localization tools. Sisulizer use standard database engines for Translation Memory. Below is list supported databases: - Access - ADO/ODBC compatible - dBase - DBISAM (embedded to Sisulizer) - Firebird - Interbase - MySQL - Oracle - Paradox - SQL Server You could add to Sisulizer many different Translation Memories, e.g. for selected projects, language pairs etc. Every Translation Memory could be based on other database engine. You could even create shared Translation Memory (Enterprise Edition), and your translators from e.g. China, Germany and Spain could work with these same translations resources in this same moment in real time. Translation Memory is very extended and flexible solution and more information you could to find here: http://www.sisulizer.com/online-help/TranslationEngines.htm Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
drungrin Member
|
Suppose that I develop a machine translator software. How do I do to make sizulizer interact with it?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Sisulizer is software localization tool and machine translations is not good solution for software localization, and for this reason we probably won't add in near future possibility of adding custom machine translation solution by users, but of course, if your solution will be attractive and serious, our developers could implement it in future as next add-on. Currently Sisulizer supports only two third-party machine translation software (Worldingo and Seram) as add-ons. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
drungrin Member
|
Our "translation machine" is an internal web service, we just wanted to make an add-on to sisulizer use it (the target software has a lot of stuff that exists on our internal web service, and using it the localization proccess should be faster). thanks for the attention!
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Any time ago some guy ask me about possibility integration online translations solution with localization tool, such as Sisulizer. He used before Excel to localization his software. Excel could be useful solution for exchange translations between translators or localization tools, but as localization tool is completely useless. He chosen XLIFF format, because this localization format is dedicated for web solution, and it could be implemented in easy way to modern interactive websites based e.g. on PHP, additional XLIFF is supported by most professional desktop localization tools e.g. by Sisulizer. Our solution working in following way, translator could translate resources in the Sisulizer and then upload output XLIFF file on web server via special translation website, and vice versa, he could translate strings on this same website, next he could export it from website to XLIFF file and finish translation in Sisulizer. Below is screenshot from this website. Below are some links to websites with useful information about XLIFF format: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff http://developers.sun.com/dev/gadc/technicalpublications/articles/xliff.html http://xliff-tools.freedesktop.org/wiki/ Of course you need to have Sisulizer license (edition) with support of XLIFF localization. Below is link to Sisulizer edition comparison table: http://www.sisulizer.com/sisulizer-features.shtml What do you think about described above idea? Best, Janusz Attachment: screen.png (Downloaded 26 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
drungrin Member
|
I think it can be the "integration interface"! thanks again!
|
|||||||||||||
| ||||||||||||||
| Current time is 03:58 pm | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Translation Engines | |
Sisulizer software localization tool - Three simple steps to localize
