Migrate to sisulizer - 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 ...

Support forum of the software localization tool Sisulizer

Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Not logged in - Login | Register

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 > Migrate to sisulizer

Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius

New Topic

Printer Friendly

Migrate to sisulizer - 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

Posted: Tue Nov 18th, 2008 08:46 am

Quote

bogdantomita
Member

Joined:	Tue Nov 18th, 2008
Location:
Posts:	1
Status:	Offline

Hi,

We are currently using Multilizer's Localization Components, Dictionary - Translator approach to localize our projects with CodeGear C++Builder.

How can we switch to Sisulizer keeping this approach?
Or do you recommend other approach?

We use the Translators OnLanguageChange and OnLocaleChange events for performing additional tasks when changing the language.

Thank you,
Bogdan Tomita - Software Developer

Quote

Posted: Tue Nov 18th, 2008 11:48 am

Quote

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Tokyo, Japan
Posts:	1641
Status:	Offline

Hi,

Sisulizer's (SL) approach to language switch is different. SL uses VCL's resource dlls (e.g. Project1.DE) and SL's own unit to perform language switch. The point is that by default VCL loads the default resource DLL. After that you can change the resource DLL to any. To do that you use LaResource.SelectResourceLocale that shows language available resource DLLs, lets you select a new language, loads the new reasource DLL and finally translates existing forms usin the new resource data.

Multilizer's (ML) dictionary translator has the following drawbacks:

It uses it's proprietary resource format (MLD or txt files) to store translations. SL uses standard resource DLL's of VCL
With ML you have to add translator component to every form. With SL you only have to add LaResource.pas unit to your project and call SelectResourceLocale or LoadNewResourceFile.
ML can only locale string properties. It can not handle With, Height, etc. SL can handle this.

SL's OnLanguageChange are LaBeforeTranslate and LaAfterTranslate event of LaTranslator.pas. You can use them to control what and hwo properties are translated. For example you can disable translation of a property/component.

SL contains two samples for language switch:
<sldir>\VCL\DelphiWin\Converter
<sldir>\VCL\DelphiWin\LangChange

If you have any questions I am happy to help more.

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Quote

Posted: Tue Nov 18th, 2008 01:38 pm

Quote

Markus.Kreisel
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Bedburg, Germany
Posts:	831
Status:	Offline

Hi Bogda,

if you decide to make the switch from ML please don't forget to contact sales (at) sisulizer.com to get your x-grade discount code.

Markus

____________________
http://www.sisulizer.com - Three simple steps to localize

Quote

Current time is 03:00 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 > Migrate to sisulizer

Sisulizer software localization tool - Three simple steps to localize