Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
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
AuthorPost
 Posted: Thu Aug 6th, 2009 05:20 am
PM Private Upload Quote Reply
Min
Member
 

Joined: Thu Aug 6th, 2009
Location:  
Posts: 13
Status: 
Offline
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 61 times)

Last edited on Thu Aug 6th, 2009 05:22 am by Min

Back To Top PM Private Upload Quote Reply

 Posted: Thu Aug 6th, 2009 05:25 am
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
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
Back To Top PM Private Upload Quote Reply

 Posted: Sun Aug 9th, 2009 07:54 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3866
Status: 
Offline
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 53 times)



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Sun Aug 9th, 2009 07:56 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3866
Status: 
Offline
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 53 times)



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Aug 10th, 2009 02:07 am
PM Private Upload Quote Reply
Min
Member
 

Joined: Thu Aug 6th, 2009
Location:  
Posts: 13
Status: 
Offline
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 53 times)

Last edited on Mon Aug 10th, 2009 02:09 am by Min

Back To Top PM Private Upload Quote Reply

 Posted: Mon Aug 10th, 2009 05:34 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3866
Status: 
Offline
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 49 times)



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Tue Aug 11th, 2009 04:40 am
PM Private Upload Quote Reply
Min
Member
 

Joined: Thu Aug 6th, 2009
Location:  
Posts: 13
Status: 
Offline
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 43 times)

Back To Top PM Private Upload Quote Reply

 Posted: Tue Aug 11th, 2009 04:41 am
PM Private Upload Quote Reply
Min
Member
 

Joined: Thu Aug 6th, 2009
Location:  
Posts: 13
Status: 
Offline
2. Then I set the tags as shown in screenshot attached, and click "OK".

Attachment: folder_xml_tags_set.jpg (Downloaded 43 times)

Back To Top PM Private Upload Quote Reply

 Posted: Tue Aug 11th, 2009 04:42 am
PM Private Upload Quote Reply
Min
Member
 

Joined: Thu Aug 6th, 2009
Location:  
Posts: 13
Status: 
Offline
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 43 times)

Back To Top PM Private Upload Quote Reply

 Posted: Tue Aug 11th, 2009 04:45 am
PM Private Upload Quote Reply
Min
Member
 

Joined: Thu Aug 6th, 2009
Location:  
Posts: 13
Status: 
Offline
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 05:03 am by Min

Back To Top PM Private Upload Quote Reply

 Posted: Tue Aug 11th, 2009 04:48 am
PM Private Upload Quote Reply
Min
Member
 

Joined: Thu Aug 6th, 2009
Location:  
Posts: 13
Status: 
Offline
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.

Back To Top PM Private Upload Quote Reply

 Posted: Tue Aug 11th, 2009 07:32 am
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 2012
Status: 
Offline
Could you upload that Priced409.dll file also. I will take a look of it.



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 12th, 2009 01:19 am
PM Private Upload Quote Reply
Min
Member
 

Joined: Thu Aug 6th, 2009
Location:  
Posts: 13
Status: 
Offline
priceres.dll uploaded thru private upload. Cheers.

Back To Top PM Private Upload Quote Reply

 Posted: Thu Aug 13th, 2009 08:28 am
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
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
Back To Top PM Private Upload Quote Reply

 Posted: Thu Aug 13th, 2009 08:33 am
PM Private Upload Quote Reply
Sisusupport
Administrator
 

Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2261
Status: 
Offline
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
Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 14th, 2009 05:09 am
PM Private Upload Quote Reply
Min
Member
 

Joined: Thu Aug 6th, 2009
Location:  
Posts: 13
Status: 
Offline
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

Back To Top PM Private Upload Quote Reply

 Posted: Tue Aug 18th, 2009 12:16 am
PM Private Upload Quote Reply
Min
Member
 

Joined: Thu Aug 6th, 2009
Location:  
Posts: 13
Status: 
Offline
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

Back To Top PM Private Upload Quote Reply

Current time is 01:24 pm  
.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?



WowUltra modified by Sisulizer Copyright © 2007-18 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize