|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Public information from the Sisulizer team > Offers, Announcements and FAQs > Neutral language in the main assembly or not
|
|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Public information from the Sisulizer team > Offers, Announcements and FAQs > Neutral language in the main assembly or not
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Neutral language in the main assembly or not - Offers, Announcements and FAQs - Public information from the Sisulizer team - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
DanMitsu Member
|
Hi, Maybe this forum is not the right one to ask this question, but it was difficult to find the right one. My doubt is : do you recommend to set neutral language in the main assembly or in a satellite assembly in order to work with Sisulizer ? I know that MS recommends to do it in a satellite assembly but maybe you recommend the other way. Does Sisulizer support both properly ? Thanks in advance.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
What is your platform: 1) .NET or 2) Visual C++ or 3) Delphi Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
DanMitsu Member
|
.NET, and I am mainly talking about wpf because in WinForms all technical articles recommend neutral language in the main assembly , don't they ?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
In .NET the satellite assembly name is the same for all languages. For example if we have main assembly: MyApplication.exe, all satellite assembly files are name MyApplication.resources.dll. Only their location is different. Each satellite assembly file must be on a language depend directory. For example de\MyApplication.resources.dll is the German satellite assembly file. The name of the file is only half the job. Another important issue is the name of the resource inside the assembly. The main assembly file contains (in most cases) neutral resources. For example MyApplication.Form1.resources. This is the original neutral resource. Each satellite assembly file contains the same resource as localized. The name of the localized resource must also be "localized" such way that it contains the language part just as the sub directory where the satellite assembly file is. So our German assembly file contains MyApplication.Form1.de.resources. It is very important that both the sub directory, file name and resource names in the satellite file are right. Otherwise .NET runtime can not use them. So place neutral resources in the main assembly file and let Sisulizer you create the localized satellite assembly file. Such way they file names and resource name will be right. if you compile your satellite assembly files yourself follow the instructions I gave above. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 03:48 am | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Public information from the Sisulizer team > Offers, Announcements and FAQs > Neutral language in the main assembly or not | |
Sisulizer software localization tool - Three simple steps to localize
