|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Original Language - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
scheidtmann Member
|
Hi, do i also need to add the language "german" if the original language of my application is german? Dear Andre
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Andre, no, in this case the original language is German and it already shows in the column "Original". There is no need to add another German column, except you want to translate into e.g. Austrian German :-) Another reason why a German column in a German application can be useful is, if you have spelling errors in the German original and you want to give it to a German proof reader. You then would copy all strings from original to the target column and send that in a translation package to your editor. After you got the corrections Sisulizer could build a "corrected" German binary for you. Remember that Sisulizer - like all serious localization tools - will never change your source. With the trick above you can nevertheless use Sisulizer for proof reading of your original language strings. This is one of the reasons why Sisulizer allows you add your original language also as one of the target languages. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
scheidtmann Member
|
Thanks for the fast answer. After removing the additional german language successfully the xxx.de.resx files were not delete. Is there an option to do this automatically and also remove them from the DotNet Solution?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Andre, did you use Project - Build-All after you removed German as target language? The new build should not build new German RESX-files. The Sisulizer build process does not automatically delete any files created in a prior builds. You have to remove files this files manually. It is a very rare situation that a language is removed from a Sisulizer project, especially if already translations exist. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
scheidtmann Member
|
Ok, but what about the other way. After adding an new language and "Build All" the new resx files were generated but not included into the Visual Studio Solution. Do I really need to add every new rexs file manually to the VS project? Dear Andre
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Andre, I think you make yourself the life a little bit harder than needed. Sisulizer creates all needed binaries for you. You do not need to change or rebuild your original project, except that you tell .NET to load the right satellite assemblies at program start with: Thread.CurrentThread.CurrentUICulture = CultureInfo.CurrentCulture; Read NET's satellite assemblies and runtime language change in the online-help to find out more. You can even switch the language at runtime. Take a look at the sample: \Net\CSharp\LangChange\LangChange.slp to get some idea. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
scheidtmann Member
|
Thanks for the info. We are coming from a localization tool which uses the other way. I just read: How to let Visual Studio to compile satellite assembly files In some situations such as using .pfx key files Sisulizer can not compile satellite assembly files. In that case you have to let Visual Studio to compile them. The following instructions describe how to do that. Hopefully we don´t get into problems with our signing... Greets Andre
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Andre, If your have signed your assembly file Sisulizer will automatically sign the satellite assembly files it creates. However this automatic signing work only if you use project file localization. If you use assembly file localization you have to make Sisulizer to sign satellite assembly files. To do that add key file parameter to the assembly linker parameter list. If you use project file localization or assembly file localization with .snk keys you will have no problems with signing. Search for code signing in the online-help. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 11:17 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 > Original Language | |
Sisulizer software localization tool - Three simple steps to localize
