|
|||
|
.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
|
Hello Janusz, I was recommended (by Markus) to apply to you with some questions we stayed while dealing with Sisulizer tool having eval license. Actually we had some progress in localization process but here are the list of open issues we are interested to get an answer. I'd like to remind that our software is WPF C# application and all resources reside in satellite dlls. Our default language is Hebrew. How to configure the tool to be able recognize the following items from 1. xml file with the following structure: … <Items> <Item name="" caption="דיווח נקודות מדד" visible="true" enabled="true"/> <Item name="" caption="תוספת יוקר" visible="true" enabled="true" image="pack://application:,,,;Component/Images/image1.png"> <Groups> <Group name="" caption="תוספת יוקר" visible="true" enabled="true"> <Items> <Item name="" caption="עובדים נכללים בתוספת יוקר" visible="true" /> <Item name="" caption="דיווח" visible="true" enabled="true" /> a. We'd like to recognize and translate the "caption" field belonging to "Item" and "Group" elements. b. We'd like to recognize and change the path to the image file defined in "image" field of "Item" element 2. During localization process we have to control the following xaml property of the main window FlowDirection="RightToLeft" / LeftToRight to be able swiching from Hebrew to English and vice versa. 3. We'd like to translate all strings residing in .resx file Thanks in advance I am looking forward to your help
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
kostya.shilkrot_(at)_gmail.com wrote: How to configure the tool to be able recognize the following items from Sisulizer automatically detects XML data in resource data as XML and lets you to choose what items to localize. Is your XML file added to VS project as Embedded Resource? If not it is a standalone file and you have to add it manually to Sisulizer project. See screenshot to see how embedded XML files appers in Sisulizer project. To get the property dialog right click the XML node and choose Properties. Jaakko Attachment: Untitled.png (Downloaded 44 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
kostya.shilkrot_(at)_gmail.com wrote: 2. During localization process we have to control the following xaml property of the main window The current Sisulizere build can correctly change the FlowDirection only if the original value is LeftToRight or does not exist. If the original value is RightToLeft as you do Sisulizer fails to set it LeftToRight when creating English (or other lefto to right language). Fortunately I fixed this in build 301. The new build correctly sets the FlowDirection on the case where original language is RTL. The new build will come out in next week. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
kostya.shilkrot_(at)_gmail.com wrote: 3. We'd like to translate all strings residing in .resx file This works. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
Hi Jaakko, Thanks for your quick response. Our xml files were added to the project as "Resource" and not as "Embedded Resource". After I've change this definition it started to be recognized by the tool. The property dialog of the XML node shows all fields checked except the one I need to be included as localized item (caption). This field appear as disabled and marked as "Context value". How can I exclude all fields except this one (caption) that has Hebrew text ? Thanks
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
It's okay, I have found the decision ...
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
Hi Jaakko, does Sisulizer have an ability to recognize xml file if it's defined as "Resource" and not as "Embedded Resource" in VS ? Thanks in advance
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Yes. You have to add the XML file itself into Sisulizer project. Sisulizer does not automatically add such an XML file. The differenced between Resource and EmbeddedResource is that embedded XML is actually stored inside assembly file. In the case of resource the resource data is in standalone file. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Can you upload me the XML file. Click Private Upload to send the file. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
kostya.shilkrot_(at)_gmail.com wrote: (caption). This field appear as disabled and marked as "Context value". How can I exclude all fields except this one (caption) that has Hebrew text ? Right click the field node and choose Normal value. See the screenshot. Jaakko Attachment: Untitled.png (Downloaded 35 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
Hi Jaakko, Of course, I've sent you one of our xml files. By the way yesterday when I was trying to define an xml relevant fields to localize, Sisulizer got a crash during rescaning process. I will reproduce this situation and will send you the details Thanks Kostya
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello,By the way yesterday when I was trying to define an xml relevant fields to localize, Sisulizer got a crash during rescaning process. I reproduced this error, so you needn't send to us your bug report. However, don't worry this error and continue your work with Sisulizer - it should work correctly. If you would like avoid this error for your XML files with current build, you should before re-scan uncheck all unnecessary items in tags tree, or simple, click on "Uncheck all" on toolbar of "Tags" tab in source properties, next check only required items (in your case "caption" and "image" attribute") and re-scan project. You can find more information about XML localization in this article on our blog: http://www.the-localization-tool.com/?p=145 Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
Hi Janusz, Jaakko When I add an xml file to the project and after I've "Uncked All" all attributes and point on one (caption) I wan't to change its property to "Normal Value" it causes to throw an exception and I can't go on to re-scan the soultion . I've attached a print screen as well Thanks
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
sorry , there were some grammar mistakes in my prev post: it should be: "... and point on the one (caption) I want to change its property ..."
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
Okay, I have found the workaround ... it works
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
I'm glad it work for you. Of course, I'll forward this issue to our developers. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
Hi Janusz, Jaakko, Finally Sisulizer tool has created output files under /en-US folder but when I run the application, configured to work with an English version, an exception has been thrown saying that some of resources can't be found. As result I'd like to ask you some questions: 1. I've added an xml file in Sisulizer tool manualy by right click -> Source -> xml file in each project included in the solution (we have 10 like this), because xml file was defined as "Resource" and not "Embeded Resource" therefore it hasn't been recognized by Sisulizer. On the other hand when Sisulizer finished creating an output files ( satelitte dll ) , it seems that an xml file hasn't included in a satellite assemblie and this is a reson why application throws an exception. 2. Sisulizer didn't build the output files for some of the projects, even so it created an xml file translated to English separately. Why ? Hi Janusz, Jaakko, Finally Sisulizer tool has created output files under /en-US folder but when I run the application, configured to work with an English version, an exception has been thrown saying that some of resources can't be found. As result I'd like to ask you some questions: 1. I've added an xml file in Sisulizer tool manualy by right click -> Source -> xml file in each project included in the solution (we have 10 like this), because xml file was defined as "Resource" and not "Embeded Resource" therefore it hasn't been recognized by Sisulizer. On the other hand when Sisulizer finished creating an output files ( satelitte dll ) , it seems that an xml file hasn't included in a satellite assemblie and this is a reson why application throws an exception. 2. Sisulizer didn't build the output files for some of the projects, even so it created an xml file translated to English separately. Why ? Thanks in advance
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
I'd like to emphasis that modules for which the output file has not been built include only two files: xml and C# Business Logic class
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
On the other hand when Sisulizer finished creating an output files ( satelitte dll ) , it seems that an xml file hasn't included in a satellite assemblie and this is a reson why application throws an exception. Sisulizer always create localized versions of added sources as output files. However, for VS solution files or VS project files, Sisulizer instead localized versions of these files can compile localized assembly files. These output assembly files contains all items visible as sub-nodes of sln or csproj nodes in Sisulizer’s Project tree. Because you added your XML as separate source, so Sisulizer created for this file also separated output file (as XML of course). This file is not included directly to your VS project (sln, csproj sub-item in Sisulizer’s project tree), so Sisulizer can’t include it to output assembly file. Jaakko already wrote about it above: Yes. You have to add the XML file itself into Sisulizer project. Sisulizer does not automatically add such an XML file. The differenced between Resource and EmbeddedResource is that embedded XML is actually stored inside assembly file. In the case of resource the resource data is in standalone file. So if you would like add XML resource to assembly files via Sisulizer, you need re-organize your VS projects. 2. Sisulizer didn't build the output files for some of the projects, even so it created an xml file translated to English separately. Why ? Could you upload some example to us (source files and SLP)? We would like check it, but we need more details and files for reproduce it. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
kostya.shilkrot@gmail.com Member
|
I've also compared the size of assemblies that were built under /en-US with original ones under /he-IL and see they have less size and it seems they don't include xml files .
|
||||||||||||||||
| |||||||||||||||||
| Current time is 06:52 am | 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
