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
Sisulizer do not generate translated output BPL file correctly - 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: Mon Dec 11th, 2017 01:04 pm
PM Private Upload Quote Reply
triszterer
Member
 

Joined: Mon May 5th, 2008
Location:  
Posts: 49
Status: 
Offline
Hello,

All looks fine in the sisulizer gui, so every items are translated in the preview (See: Sisulizer.png) but when the translated
binary is generated then some items are not translated (see: Restorator.png)

Please check the text: "Pressure control valve on wheel %s" which is translated but always remains in English in the output file.
I can not find the reason. Susilizer Enterprise 4.0 (Build: 369) was used.

All files are uploaded in private.

Attachment: Restorator.png (Downloaded 6 times)

Last edited on Mon Dec 11th, 2017 01:06 pm by triszterer

Back To Top PM Private Upload Quote Reply

 Posted: Mon Dec 11th, 2017 04:19 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3826
Status: 
Offline
Hello,

Thank you for files. Sisulizer uses component name as context item. Sisulizer always requires unique context items, while name="PCV_%s" occurs several times in this XML node. Probably this caused incorrect building of output files. You can use following solution. Save backup of your SLP, optionally save translations to TM. Next right click on Bin\NeoCore.bpl.XML.COMPNAME node in the Project Tree and select "Properties" in the context menu. Next go to "XML Tags" tab, right click on "Name attribute" and change it from "Context value" to "Normal value" and rescan source. Next you can re-translate new items via TM or by import from SLP backup file you made before.

Janusz

Attachment: xml_properties.png (Downloaded 5 times)



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

 Posted: Tue Dec 12th, 2017 08:24 am
PM Private Upload Quote Reply
triszterer
Member
 

Joined: Mon May 5th, 2008
Location:  
Posts: 49
Status: 
Offline
Thank you it helped. Can you explain how Sislizer will be able to identify the node for translation in this case?

Back To Top PM Private Upload Quote Reply

 Posted: Tue Dec 12th, 2017 09:36 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3826
Status: 
Offline
Hello,

If your project does not use XML context attributes, Sisulizer calculate context based on item index or item value:
  • Item Index: Item index is the string context. Each item (code or string) has an index value that is a counting integer values starting from 0. Compared to String value method this method creates own row for each instance of the same string letting you to translate them in a different way. This is the default value. When you re-order items in updated XML file (for example, you add or remove some item) it can generate new rows in a SLP, also for already existing items, because index is changed.
  • String Value: String value is the string context. If the source code contains same string twice of more than all instances share the single row and they all are translated in the same way. When you change original strings updated XML file, it can generate new rows in a SLP, also for already existing items, because index value is changed.
You can choose context method matched with your needs in "Options" tab of source properties dialog. Please, look at attached screenshot.

Best regards,
Janusz

Attachment: xml_context.png (Downloaded 2 times)



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

Current time is 10:40 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer do not generate translated output BPL file correctly



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