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 
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > "Do not translate" rows are being translated automatically after a scan

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
"Do not translate" rows are being translated automatically after a scan - 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: Wed Mar 7th, 2012 01:43 am
PM Private Upload Quote Reply
greg_s
Member
 

Joined: Thu Feb 2nd, 2012
Location:  
Posts: 14
Status: 
Offline
 I'm having issues when scanning an XML file for changes. I've attached the xml file that shows the behaviour. This file is set to translate the tag "textcell". Using Sisulizer 3 build 328

Before the scan I tag anything uppercase (for example "NO_ACTION") as do not translate (ctrl+R), and the translations are empty. After the scan those rows end up with incorrect translations added (e.g. "No_Action" receives the French translation "Aucune action".

Any ideas what is happening? I cannot see anything in the project set to automatically translate after the scan - and I would have thought "Do not translate" strings should remain untouched?
Back To Top PM Private Upload Quote Reply

 Posted: Wed Mar 7th, 2012 06:07 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2993
Status: 
Offline
 Could you also upload to us your SLP file?

Best regards,
Janusz



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

 Posted: Wed Mar 7th, 2012 06:53 pm
PM Private Upload Quote Reply
greg_s
Member
 

Joined: Thu Feb 2nd, 2012
Location:  
Posts: 14
Status: 
Offline
 I've uploaded the SLP. Cheers, Greg
Back To Top PM Private Upload Quote Reply

 Posted: Wed Mar 7th, 2012 08:09 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

Thank you for file. I reproduced issue. We'll investigate it.
Workaround:
Open XML source properties, go to "Tags" tab, right click on "fieldId attribute" item under "textCell" item and select "Localize" value in context menu, next go to "Options" tab and type/paste DSDBM_PCAINPUT_INPUT_KEY text to "Disable field" (like on below screenshot). Next re-scan project. This solution has following advantages comparing to Do Not Translate feature:
  • It automatically disable all key items by one simple operation, so when you'll add next similar items to your XML file, Sisulizer automatically disable those items from localization.
  • This is safer solution, because all disabled items are unavailable in sheet.
Best regards,
Janusz


Attachment: screen.png (Downloaded 11 times)



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

Current time is 11:58 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > "Do not translate" rows are being translated automatically after a scan



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