|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > support of embedded xml in an executable?
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > support of embedded xml in an executable?
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| support of embedded xml in an executable? - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Min Member
|
Dear support, I am evaluating a few localization tool for the company, trying to decide which one is most suitable for us. I found sisu Lizer enterprise edition is mostly intuitive, however there is one problem, big problem for us: We have many xml files built in the resource, in the executable, compiled in Visual C++ 2008. when we add the exe into lizer, we found lizer recognize that resource category for xmls but does not allow us to edit it. We can only view them in either text mode or binary mode. It appears Lizer is unable to interpret them as xml files, hence we are not able to localize them. Please see screen shot attached. Is this an expected behavior? Any possibility add in the support or workaround? I understand I can localize the xml files if I load them directly to lizer but we would like to localize the binary directly instead. Best regards, Min Attachment: lizer_xml_problem.jpg (Downloaded 58 times) Last edited on Thu Aug 6th, 2009 06:22 am by Min |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Sisulizer can localize embedded XML resources. Can you zip your EXE and Sisulizer project file (.slp) and then click Private Upload button to upload it to me. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Below is workaround: Sisulizer allows you manually set up custom format for not recognized resources. Right click on "PhonebookD409.dll" > "771" > "32777" sub-node in project tree and select "Properties" item from context menu. Next uncheck "Automatic format" and select "XML" from "Format:" dropdown menu in "Format" tab. After these changes you should re-scan your project. Solution was tested with Sisulizer build 287. Attachment: screen.png (Downloaded 50 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
You can also disable from localization all unnecessary XML items: Right click on "PhonebookD409.dll" > "771' > "32777" sub-node in project tree and select "Properties" item from context menu. Next go to "XML tags" tab and uncheck all unnecessary items (seem to me that in your case you can leave checked only "COLUMN" > "Name attribute" and "FIELD" > "Title attribute"). Next you should re-scan project again. Below, on screenshot is result of this operation: Best regards, Janusz Attachment: screen1.png (Downloaded 50 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Min Member
|
Janusz, Your workaround works great. Thanks. I actually also found I can set up the custom format of the folder from the properties of the folder (i.e. 771 in this case) to be xml. After that, all items under the folder are recognized as xml format and hence viewable and editable. Cool. Being encouraged by this fact, I tried setting up xml tags filter for the folder (not for individual item, since for some projects we may have over 100 xmls built in this way), as shown in the screenshot attached. Unfortunately as it turned out, those tag settings are not somehow remembered by the folder. after I clicked the OK and then re-open the properties window, I found all xml tags are ticked again. Is this a bug or by design? Regards, Min Attachment: folder_xml_properties.jpg (Downloaded 50 times) Last edited on Mon Aug 10th, 2009 03:09 am by Min |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello,Unfortunately as it turned out, those tag settings are not somehow remembered by the folder. after I clicked the OK and then re-open the properties window, I found all xml tags are ticked again. This is normal behavior. Sisulizer remove all XML tag settings for selected resource, if you change format of this resource to other, so when you revert again this node format to XML, Sisulizer use default settings, but you can export these tag settings to external file with SLI extension. Note: During import Sisulizer doesn’t replace tag items, it merge tag items from exported file with existing tag items in project, so sometimes useful is unchecking all items ("XML Tags" tab toolbar) before import. Best regards, Janusz Attachment: screen.png (Downloaded 46 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Min Member
|
Janusz Grzybek wrote: This is normal behavior. Sisulizer remove all XML tag settings for selected resource, if you change format of this resource to other, so when you revert again this node format to XML, Sisulizer use default settings, but you can export these tag settings to external file with SLI extension. Thanks for your quick response. But I don't think this is what is happening with my case. Let me try explain what exactly I have done: 1. I righ-click the folder 771, choose properties, and then uncheck the "automatic format" and select "XML" to force xml. As shown in the attached screenshot. Attachment: folder_xml_custom_fmt.jpg (Downloaded 40 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Min Member
|
2. Then I set the tags as shown in screenshot attached, and click "OK". Attachment: folder_xml_tags_set.jpg (Downloaded 40 times)
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Min Member
|
3. Then immediately I open the properties of the folder again , only find all tags I have set for the folder are gone. Attachment: folder_xml_tags_lost.jpg (Downloaded 40 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Min Member
|
Could you please advise again? Is this by design (not saving xml tags for folders), or a bug? BTW: just one more gripe from me, it seems the trial version is assigning this string "[Sisulizer Trial]" randomly into the manifest and xml files in the resource, which caused a lot of trouble for our testing: either the resulting dll can't be loaded because manifest info became invalid, or the xml file can't be loaded. This is quite annoying frankly. It cost me 4 hours to figure this out this morning when the destination dll failed to load. And unitl now I basically could not proceed any further with our xml files as there are way too many xml files that have been corrupted due to this random string. May I suggest you to look into some better way to stamp the trial version in future other than this design? I think it may scare some potential customers away. Anyway, still heaps of thanks for looking into this xml issue. Cheers Min Last edited on Tue Aug 11th, 2009 06:03 am by Min |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Min Member
|
btw, pls feel free to move this thread to the other forum since this thread does not appear to be a "wish" but a bug/feature discussion. Thanks.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
Could you upload that Priced409.dll file also. I will take a look of it.
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Min Member
|
priceres.dll uploaded thru private upload. Cheers.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Min wrote: btw, pls feel free to move this thread to the other forum since this thread does not appear to be a "wish" but a bug/feature discussion. Thanks. I fixed this in build 288. The problem was that Sisulizer did not save the settings you set either to folder or node of a custom resource. Now it does. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Min wrote: We have many xml files built in the resource, in the executable, compiled in Visual C++ 2008. when we add the exe into lizer, we found lizer recognize that resource category for xmls but does not allow us to edit it. We can only view them in either text mode or binary mode. It appears Lizer is unable to interpret them as xml files, hence we are not able to localize them. Please see screen shot attached. The problem was that your XML resources do not contain XML header <?xml version="1.0" encoding="UTF-8"?> Because data does not contain XML header it is not valid XML. This is why Sisulizer detects the data as HTML instead of XML. I recommend you to add XML header to the resources. If you can not do that then you have to set the format manually. Either way you have to wait for build 288 in order to configure what XML elements are scanned. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Min Member
|
The format of the XML files have to stay as is since they are like that for historical reason, which is fine as I don't mind manually changing the format. But the one with settings on folder is very important. I am actually surprised no one has ever reported before. Anyway, excellent work! I am very impressed by your quick response. Cheers Min
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Min Member
|
Min wrote: just one more gripe from me, it seems the trial version is assigning this string "[Sisulizer Trial]" randomly into the manifest and xml files in the resource, which caused a lot of trouble for our testing: either the resulting dll can't be loaded because manifest info became invalid, or the xml file can't be loaded. This is quite annoying frankly. It cost me 4 hours to figure this out this morning when the destination dll failed to load. And unitl now I basically could not proceed any further with our xml files as there are way too many xml files that have been corrupted due to this random string. May I suggest you to look into some better way to stamp the trial version in future other than this design? I think it may scare some potential customers away. Per the suggestions from Markus, I have uploaded some files to demo this problem thru private upload. I'll look forward to your comments. Cheers Min
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:05 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > support of embedded xml in an executable? | |
Sisulizer software localization tool - Three simple steps to localize
