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
Import from Multilizer 5.1 trims localized strings - 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 Feb 13th, 2017 11:48 am
PM Private Upload Quote Reply
huber13
Member
 

Joined: Tue Feb 7th, 2017
Location: Germany
Posts: 1
Status: 
Offline
Hi,

i have to migrate some Delphie XE2 Projects, localized with Multilizer 5.1, to Sisulizer. Therefore I created a new Project in Sisulizer and added the exe, drc & dpr references. When importing the localized strings from an *.mpr file (based on the same exe and drc file) that was saved with Multilizer 5.1, the localized strings are trimmed.

Besides the fact, that leading/ending blanks are trimmed when importing localized strings, there is another problem when the checkbox "Import also those items where the translated value equals to the original value" on the Import Wizard-Options page is not checked. Because apparently localized strings are trimmed before the comparison takes place. Hence localized strings, which are not equal to the original string because of leading/ending blanks, are ignored during an import.

I could reproduce this behaviour with Sisulizer version 4.0.364 & 4.0.365.

If needed, i can provide an mpr, exe & drc file with which this problem can be reproduced.

Thanks in advance,

Chris

Last edited on Mon Feb 13th, 2017 09:37 pm by huber13

Back To Top PM Private Upload Quote Reply

 Posted: Mon Feb 13th, 2017 02:07 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1944
Status: 
Offline
Hi Chris,

Can you please send the sample files to us. Zip them and click the Private Upload button above to send them.

Ilkka



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

 Posted: Tue Feb 14th, 2017 03:23 am
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1944
Status: 
Offline
Thank you for a very good sample. I found the bug and fixed it. The fix will be in the next build (366).

I also sent you a preview through private message.

Ilkka



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

 Posted: Wed Feb 15th, 2017 12:46 am
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1944
Status: 
Offline
If you want to import Do Not Translate flag check this check box in the import wizard.

Ilkka

Attachment: Untitled.png (Downloaded 9 times)



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

Current time is 03:38 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Import from Multilizer 5.1 trims localized strings



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

Sisulizer software localization tool - Three simple steps to localize