|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Choosing the right Output Format - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
renatonow Member 
|
Hi: I read the Quick Start Guide on section 3.4 about how to choose the right output format. However there is little information on how to actually use the generated files in the case of "One executable, several resource DLLs" and "One executable with embedded resource DLLs". How should I load them at runtime to replace the original resources? Thanks Renato
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Renato, the usage of the files is pretty easy in the most cases, e.g. if you use VCL or MFC this libraries do most of the job. For .NET you have to add only a single line of code for language selection. The platform specific technical information on this topic can be found in the online-help. Open the property dialog (right click on source in the project tree -> properties) and then press F1 or click the help button. Also take a look at the samples coming with Sisulizer for the different platforms. Hope this helps Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Localized files If checked Sisulizer creates a localized file for each language in the project. For example if the original file is MySample.exe and the project contains German and Japanese, Sisulizer will create deMySample.exe and jaMySample.exe. These files are equal to the original file except resource data has been localized. Multilingual file If checked Sisulizer creates one multilingual file containing all the languages of the project. For example if the original file is MySample.exe, Sisulizer creates allMySample.exe that contains resources in each language of the project. Resource DLL files If checked Sisulizer creates localized resource DLL files. They are resource-only DLLs that contains the same resource data as the original file but the resource data has been localized to the target language. VCL: Use resource files and Sisulizer VCL functions to enable run-time language switch. For example if the original file is MySample.exe and the project contains German and Japanese, Sisulizer will create Sample.DE and Sample.JA resource DLL files. MFC: Use resource files and MFC functions to enable run-time language switch. For example if the original file is MySample.exe and the project contains German and Japanese, Sisulizer will create SampleDE.dll and SampleJA.dll resource DLL files. Embedded resource DLL files If checked Sisulizer creates an output files that contains all the resource DLL files embedded into the binary file. Such an EXE can support several language in one file and the user can even change the language of the application on run time. The output directory for the embedded file is "emb". What is your development tool and what programing language you use? I can tell more when I know these. Jaakko Last edited on Fri Apr 20th, 2007 10:50 am by Jaakko.Salmenius ____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
renatonow Member
|
Hi thanks a lot for your help. The projects we have are large and complex. The current need is to localize an application written with MFC, that has uses static libraries, dynamic libraries and COM components. Our first attempt to localize was:
The way I think will better in our case is to let the tool duplicate the .exe's and .dll's for every different language and let the application install system (currently InstallShield) decide which files to install depending on the user choice. If this approach is correct, are there any suggestion in other arrangement that needs to be done at the source level (besides compiling in UNICODE for instance)? Cheers, Renato
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi, > The way I think will better in our case is to let the tool duplicate the .exe's > and .dll's for every different language and let the application install system > (currently InstallShield) decide which files to install depending on the user choice. Exactly right. This is the easiest and least error prone approach. It is also the default output file in Sisulizer. You do not have to compile in Unicode. Sisulizer can localize Ansi applications as well. However if you do not mind that you applications will not work on 95/98/ME then we recommend to compile in Unicode. This has advanagage that you can run your application on any language on any computer (if they have correct fonts installed). For example you can run Japanese Unicode application on English computer. But if you run Japanese Ansi application on English computer you will get mojibake. http://en.wikipedia.org/wiki/Mojibake Just make sure that you do not have any hard coded string. If any, remove them and put them to the string resources. Check you UI if it is easy to translate: http://www.sisulizer.com/translation/vcl/delphi.shtml This is for Delphi but most of the tips are good for Visual C++. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 08:13 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 > Choosing the right Output Format | |
Sisulizer software localization tool - Three simple steps to localize
