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) > Usage - Three simple steps to localize > Problem with "Do not translate" / "Unused" flag when scanning DLLs from two bran

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
Problem with "Do not translate" / "Unused" flag when scanning DLLs from two bran - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Mon Jun 7th, 2010 01:45 pm
PM Private Upload Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 183
Status: 
Offline
 Dear all,

I do the following:

1.) Scan DLL from branch A. Mark strings as "Do not translate".
2.) Scan DLLs from branch B. Strings are "Unused".
     Problem 1: A lot of strings do not show up as "Unused". They are removed from the project.
3.) Scan DLL from branch A again. Strings are "New".
    Problem 2: A lot of strings do not have the flag "Do not translate" anymore. I think the ones that did not show up as "Unused".

I am guessing that all strings with a "Do not translate" that do not have a translation do not show up as "Unused".

I expect that all strings are kept in the project, especially to keep the flag "Do not translate". We are speaking about several hundred strings with the flag, so we could not reapply the flag each time we do a scan.

Is there a solution to our problem?

I upload screenshots, the project, and the DLLs in question.

Thanks, Christine
Back To Top PM Private Upload Quote Reply

 Posted: Tue Jun 8th, 2010 02:18 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

Thank you for files. On my machine all work correctly, that is, after replacing file from Branch A by file from branch B all unused items are still in project. After replacing A -> B -> A, Sisulizer correctly restored project to old version of source file and keep all (403 rows) items with "Do Not Translate" status. So seem to me that issue could be related to your settings of Sisulizer. Could you check following setting?
"Tools" menu -> "General" -> "Settings" -> "Remove unused items automatically". If you have checked this setting, uncheck it.

Best regards,
Janusz

Attachment: screen.png (Downloaded 17 times)



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

 Posted: Wed Jun 9th, 2010 01:48 pm
PM Private Upload Quote Reply
Christine
Member
 

Joined: Tue Nov 20th, 2007
Location:  
Posts: 183
Status: 
Offline
 Dear Janusz,

excellent, that's it!

Thanks for the quick and competent support.

Christine
Back To Top PM Private Upload Quote Reply

Current time is 06:02 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Problem with "Do not translate" / "Unused" flag when scanning DLLs from two bran



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