|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| single language for one build? - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
michael.sync Member
|
I'm a bit confused about step #3. The way that I understand is that we will need to build for each language applicaiton. For example: I have one cs project that is using en-US. I want to support japanese and chinese languages in my application. If I'm using Sisulizer, it seems like I have to build the application for each language. so, i will have MyApplication-en-US.exe, MyApplication-jp.exe and My application-chinese.exe. Is it correct behiovr? or did i miss something? I don't think this is good idea to have one exe for each language.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, On the build process Sisulizer creates the localized resource files. Sisulizer can automatically compile the created localized resource files into compiled resource files (.baml or .resources) and finally link the compiled resource files to satellite assembly files (.dll). NET framework uses satellite assemblies to make applications multilingual. Satellite assembly is an assembly file that contains only resources, no code. It contains the same resources as the main assembly file but in different language. Each satellite assembly file support one language and the file must locate on a language specific sub directory of the directory where the main assembly file locate. For example MyApplication.exe is the main assembly of your application. It contains the original English resources. If we want to localize the application into German Sisulizer create a DLL called MyApplication.resources.dll that contains German resources and place that into "de" sub directory. The Japanese satellite assembly file will have the same name but it will be placed in "ja" sub directory. So our your file and directory structure will be: MyApplication.exe de\MyApplication.resources.dll ja\MyApplication.resources.dll If we want to add more language, Sisulizer just make new sub directories, compile the language specific satellite assembly file and place that on the language specific sub directory. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
michael.sync Member
|
Hi, Thanks. For example: I have the following WPF project. The project structure before using Sisulizer is as below ~ WpfApplication2.sln --[WpfApplication2] -----[Properties] ------------AssemblyInfo.cs ------------Resources.Designer.cs ------------Resources.resx ------------Settings.Designer.cs ------------Settings.settings -----[bin] ------------[Debug] -------------------------------WpfApplication2.exe -----App.xaml -----App.xaml.cs -----Class1.cs -----Dictionary1.xaml -----Window1.xaml -----Window1.xaml.cs -----WpfApplication2.csproj then, I added chinese localization to the project and i got a lot of new files in my project. Please check the project structure below. The new file are in bold. I'm not sure why you guys created new XAML or etc in my project. Those files will mix up with actual files. WpfApplication2.sln --[WpfApplication2] -----[Properties] ------------AssemblyInfo.cs ------------Resources.Designer.cs ------------Resources.resx ------------Resources.zh-CHS.resx ------------Settings.Designer.cs ------------Settings.settings -----[bin] ------------[Debug] -------------------------------WpfApplication2.exe -------------------------------[zh-CHS] ----------------------------------------------WpfApplication2.resources.dll -----App.xaml -----App.xaml.cs -----Class1.cs -----Dictionary1.xaml -----Dictionary1.zh-CHS.xaml -----Window1.xaml -----Window1.zh-CHS.xaml -----Window1.xaml.cs -----WpfApplication2.csproj
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hi, Resource files are necessary to build targeted output files, but you could to check options in projects source properties for removing these files after build process. You can to set up here: - Project menu > Edit source > (name of your source) - Right click on source name in Project tree > Properties Next, in opened dialog window select Options tab and check items indicated by red rectangle on below screenshot. Janusz Attachment: screen.png (Downloaded 7 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 12:47 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 > single language for one build? | |
Sisulizer software localization tool - Three simple steps to localize
