|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > WPF application: xml file attached in a resource
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > WPF application: xml file attached in a resource
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page:   1 2 3   |
|
|||||||||||||||
| WPF application: xml file attached in a resource - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
I am sending you one of satellite assemlles and yo can open it a text editor and see that it does include xml file.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
p.s. each project consists of two files: for example: Synel.Ozma.Client.Modules.Employees.dll Synel.Ozma.Client.Modules.Employees.resources.dll
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
OK. Thanks for files. We'll check it. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Hi Kostya You are right. If you add an XML file into WinForms project it does not get stored into resource unless you turn them EmbeddedResource. However WPF project behaves different way. If it is not EmbeddedResource XML does not left standalone as in WinForms but is stored as .g resource with XAML and image files. I need to implement this in Sisulizer. It won't take a long time and I can get it to the next build (301) Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Are you using binary or project localization? I mean have you added .csproj or .exe into Sisulizer project? Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
Hi Jaakko, I've added .sln file (as you recommended) into Sisulizer project but I would prefer to deal with satellite files under /he-IL only avoiding filtering irrelevant modules in Sisulizer tool (excluding) p.s. Our solution consists of more than 50 modules and only 12 belong to GUI and should pass a localization process.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
Jaakko, when are you planning to release the next build (301)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
> However WPF project behaves different way. If it is not EmbeddedResource XML does not left standalone as in WinForms but is stored as .g resource with XAML and image files. Jaaakko, let me correct you ... WPF puts all resources into separated satellite assembly (.resources.dll) during compilation since we defined the following property in each project file: he-IL
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
"he-IL"
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
Last edited on Thu Mar 11th, 2010 09:50 am by kostya.shilkrot@gmail.com |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
kostya.shilkrot_(at)_gmail.com wrote: ... you are filtering some symbols in the forum and I can't send the property we defined in .csproj You can use "Insert Code Tags" feature in our forum's post editor. Janusz Attachment: screen.png (Downloaded 33 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello,Our solution consists of more than 50 modules and only 12 belong to GUI and should pass a localization process. Sisulizer has implemented flexible features for excluding from project selected data types, resources, nodes of project tree, strings etc. It allows you not only speed up your project, but also improve comfort and security of your work. You can find more information about these features in following articles on our blog: http://www.the-localization-tool.com/?p=283 http://www.the-localization-tool.com/?p=266 http://www.the-localization-tool.com/?p=454 Articles are based on Delphi examples, but it work in similar way with .NET/WPF platform. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
{ he-IL }
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
okay, thanks for tips
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
Hi guys , any news for me , regarding a new release and functionality ? Thanks in advance Kostya
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, New build (301) will be available later this week. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
Hi Janusz, Does it involve the feature to deal with WPF satellite dlls ?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
kostya.shilkrot_(at)_gmail.com wrote: I've added .sln file (as you recommended) into Sisulizer project but I would prefer to deal with satellite files under /he-IL only avoiding filtering irrelevant modules in Sisulizer tool (excluding) What do you mean by to deal with satellite files inder /he-IL. You should not add a localized satellite assembly file (.resources.dll) into Sisulizer project but the original assembly file (.exe or .dll). Sisulizer then creates satellite assembly files. If you want to localized only 12 modules out of many you have two choices: - Add each individual .csproj instead of one .sln - Add each assembly file (.exe or .dll) that you want to localize. Build 301 will come out tomorrow or Sunday. It contains the XML file. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
kostya.shilkrot_(at)_gmail.com wrote: Jaaakko, let me correct you ... WPF puts all resources into separated satellite assembly (.resources.dll) during compilation since we defined the following property in each project file: You are right. If you add this option VS will build both main assembly (.exe or dll) and one localized satellite assembly file (.resources.dll) for the specified culture. The main assembly does not have .g.resources at all. That resource contains all XAML, image and XML files. This means that you always have to have correct satellite assembly installed. Otherwise you can not run the application. If this is what you want I will check this. Sisulizer is ment to localized either VS project files (.csproj, vbproj or .sln) or original assembly files (.exe or .dll). I don't see any reason why binary localization would not work with satellite assembly files. I will check this. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
I implemented localization of satelite assembly file in build 301. Now Sisulizer can have a satellite assembly file as a orginal file. Now both your issues (XML resources and adding satellite assembly file) should be OK. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 09:31 pm | Page: 1 2 3 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > WPF application: xml file attached in a resource | |
Sisulizer software localization tool - Three simple steps to localize
