|
|||
|
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 > Importing translation from Catalyst Projects
|
|
|||
|
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 > Importing translation from Catalyst Projects
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Importing translation from Catalyst Projects - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Reeva Member
|
We have been using Catalyst 6 for localization of our software UI strings. We found that it is not easy to use, it is most expensive and it is very difficult to automate the process using Catalyst. Now we are in the process of evaluating Sisulizer. According to Sisulizer help we should be able to import translation from Catalyst project into new Project in Sisulizer. We found that we have to convert Catalyst Project into Resource DLLs before importing the translation into Sisulizer. Is this how it is done? I would really appreciate it if you please also describe what other benefits Sisulizer has over Catalyst apart from what I have already mentioned. Looking forward to your answer.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Hi, What kind of files you have localized with Catalyst. Are they .EXE or .DLL files? If yes what was the development tool that was used to create them. Visual C++? Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Reeva, Jaakko takes care of the technical issues of your switch. He is one of our developers and will lead you through the many possibilities we offer. He will assist you to find the optimized way for your personal switch situation. But you also asked about the benefits you get from using Sisulizer. You already found the most important one: ease of use. Here are some other samples a) Outstanding developer support. You are already testing it it now :-) b) We listen to the needs of our customers. Everbody in our sales team has developed and localized software in the past. We all know the needs of the business from first hand. c) Bullet-proof support of far-east languages (e.g. we eat our own dog food and have two Chinese and a Japanese localization of Sisulizer and run a development office in Tokyo) d) Very small footprint of our free Translation Edition on your translator's computer. The translator does not need to install multiple runtimes, e.g. .NET e) Support for VCL and Classic VB, HTMLHelp, Mobile platforms - and of couse we also support the platforms our competition supports. f) Our version-independent .NET support is ideal for .NET 1.0, 1.1, 2.0, 3.0 and already prepared for future version. Please let us know if you have more specific requests. We are here to help you with your localization tasks. And please do not forget that we run a special at the moment :-) Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Reeva Member
|
Yes, DLL and .exe files. We use .Net Framework.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
So these .DLLs and .EXEs are .NET assemblies, right?
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
When you used Catalys to localize .NET asseblies it crearted the localized satellite assembly files. One for each language. Let's have a example You have Application.exe and you used Catalyst to create German and French. The C creates de\Application.resources.dll and fr\Application.resources.dll Now when you create a new Sisulizer project and select Application.exe into the project, Sisulizer imports translations from de\Application.resources.dll and fr\Application.resources.dll. If your output files created by C are different let me know. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Reeva Member
|
Thanks, Jaakko. My colleague (who is a developer) is using Sisulizer for evaluation. He will get back to you with further questions. One other thing that he told me that Sisulizer does not seem to be compatible with com controls.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Reeva Member
|
Hi Markus, We are impressed with your support. Thanks for your answers. Reeva
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Reeva, you are welcome. Let your colleaque send us the COM control issue and we sort it out right away. If you need to send files please send it to support (at) sisulizer.fi directly. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 01:27 am | |
| 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 > Importing translation from Catalyst Projects | |
Sisulizer software localization tool - Three simple steps to localize
