|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page: 1 2   |
|
|||||||||||||||
| DotNet 2.0 and 4.0 and Chinese - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Christine Member
|
Hi all, we have the problem that we have a mixed environment with DotNet 2.0 and 4.0 and we also have shared components between projects. Under DotNet 2.0, Sisulizer creates zh-CHS. Under DotNet 4.0, it creates zh-Hans. This behavior is correct, but we have problems with the mixture of both folders. As far as I understand it, it would be possible to either use zh-Hans under 2.0 or zh-CHS under 4.0. [Chinese (Simplified) Legacy]. I have two questions: 1.) Is it possible in Sisulizer to build either zh-Hans under 2.0 or zh-CHS under 4.0 so that we don't get a mixture? Is there a parameter for it? 2.) In a DotNet 4.0 project, we still get zh-CHS for an XML file. Is this a bug? Thanks in advance, Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
Christine wrote: 1.) Is it possible in Sisulizer to build either zh-Hans under 2.0 or zh-CHS under 4.0 so that we don't get a mixture? Is there a parameter for it? No. This is because .NET patform would not use them. 2.0 uses zh-CHS and 4.0 uses zh-Hans. When .NET tries to load a satellite assembly fiels it checks four things: 1) File name. The assembly must be in the right sub directory (e.g. zh-Hans) 2) The .NET version of the assembly is the same as main assemblly 3) If main assembly is signed the satellite assembly must als be signed with same key. 4) Resources names. The assembly must use locale depend resource names. For example if original was Sample.Form1.resources the Chinese would be Sample.Form1.zh-Hans.resources Sisulizer checks that all these are right for satellite assemblies it creates. If we would place assemblies into different directory that would break #1 and satellite assembly would never loaded. In a DotNet 4.0 project, we still get zh-CHS for an XML file. Is this a bug? Is this a standalone XML file that you have added into the same project where .NET 4.0 project is or is it an emabedde XML file that belongs to a .NET project? If standalone the output shoudl be zh or zh-CS depending if you have added Chinese Simp or Chinese Simp (China) into the project. If embedded Sisulizer does not add any name part into it unless you check Add language part into localized resource names check box (you propably checked this). This uses either zh-CHS or zh-Hans depending on the .NET There was a bug in build before 319 and assembly fiel as source (instead of .csproj or .sln). In that cases Sisulizer created wrong file and resource names. Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Nieminen Administrator
|
I studied this more and it turned out that .NET 4.0 can use the legacy Chinese code: zh-CHS and zh-CHT. This means that we can implement the feature you requested. I start working. It will be in the next build. Jaakko
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
Hi Jaakko, thank you very much, this is good news. Best regards, Christine
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Christine Member
|
Hi Jaakko, I just tried out build 322. I cannot find the new feature, can you point me to it? Another question: Instead of "zh-Hans", Sisulizer is now building localized folders with "zh-Hant". Is this correct? Best regards, Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
Is the language Simplified or Traditional Chinese. zh-Hans is the output of Simplified and zh-Hant is the output of Traditional. Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Christine Member
|
Hi Jaakko, sorry, my mistake. Can you please also comment on my main question: Where do I find the "Legacy" option in build 322? Thanks in advance, Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
Choose Project | Edit Source | source name Select Languages sheet and turn on Legacy coding. See the screenshot. Jaakko Attachment: Untitled.png (Downloaded 31 times)
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Christine Member
|
I don't have a Languages sheet in this dialog box, please check the screenshot.  Attachment: sc_Sisu_ResourceProperties.png (Downloaded 32 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
Sorry, my mistake. The feature will be in the next version (3.0) and not next build as I told earlier. Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Christine Member
|
That's really bad news as we are already waiting for the feature. Chinesisch (Simplified und Traditional) are currently not working in some of our products. Could you tell me when 3.0 might be available? Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
In a month. Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Christine Member
|
Hi Jaakko, we now upgraded to 3.0 (build 328), but I still don't have a Languages sheet in this dialog box. Actually the window looks the same as in Sisulizer 2010. Can you please comment? Thanks, Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
Christine wrote: we now upgraded to 3.0 (build 328), but I still don't have a Languages sheet in this dialog box. Actually the window looks the same as in Sisulizer 2010. The sheet is visible only if you have at least one language in the project that uses legacy language codes. For example if you add Chinese into a Sisulizer project that contains .NET 4.0 projects then the sheet is visible. Best regards, Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Christine Member
|
Thank you for the information. I needed to switch off the sublanguage from Chinese to show the Language tabbed page, which seems not so logical to me, but anyhow. Best regards, Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
Hi again, I tried it, but the combo box item "Legacy (zh-CHS, zh-CHT)" does not seem to work properly. I am using "\.resources.dll" as Output files parameter, and Sisulizer is still creating the folder "zh-Hans" instead of "zh-CHS" during build. Do you need the SLP for further analysis? Christine
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
I checked it and seems to me that you are right. I'll ask our R&D about this. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator
|
I tested this and it worked on just like it should be. I used Visual Studio 2010 and .NET 4.0. Janusz, can you send me your sample application and SLP Ilkka Attachment: Untitled.png (Downloaded 7 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Salmenius Administrator
|
No need to send. The bug occurs when there is a VS solution instead of project file in SLP. I will fix this. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator
|
I fixed this. The custom language code settings worked only Visual Studio project sources but not Visual Studio solution sources and .NET assembly souces. The fix will be in the next build (329). It will be released in two weeks. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 10:16 pm | Page: 1 2 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > DotNet 2.0 and 4.0 and Chinese | |
Sisulizer software localization tool - Three simple steps to localize
