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
used items will be removed by funktion "remove usnused" - 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: Fri Nov 9th, 2018 08:49 am
PM Private Upload Quote Reply
MichaelV
Member
 

Joined: Mon May 25th, 2009
Location:  
Posts: 30
Status: 
Offline
Hello support team.

if i click "remove unused items", used items will be removed. I attach a sample project. source ist "de".
Example: "217="Bodenschwelle" from de\pdb_texts.ini
is in the list of "can deleted items". why?

Thanks, Michael

Back To Top PM Private Upload Quote Reply

 Posted: Fri Nov 9th, 2018 11:09 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3866
Status: 
Offline
Hello,
Thank you for files. I checked your the SLP file and after removing all unused items "217="Bodenschwelle" still exists in the project. Your project contains 1443 strings with 208 unused items. After removing all unused items I got 1235 strings in the project, so seem to me that it working well.
Best regards,Janusz

Attachment: stats.png (Downloaded 16 times)



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

 Posted: Fri Nov 9th, 2018 11:44 am
PM Private Upload Quote Reply
MichaelV
Member
 

Joined: Mon May 25th, 2009
Location:  
Posts: 30
Status: 
Offline
Thanks Janusz,

but i don't understand, why there are double ids. In our source the ids are always unique.

Michael

Back To Top PM Private Upload Quote Reply

 Posted: Fri Nov 9th, 2018 12:50 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3866
Status: 
Offline
Hi Michael,

Sisulizer always uses unique context items. You are right, there are context duplicates, but second instance of this same context in your SLP is always marked as unused item. So actually, the project doesn’t break unique context rule. I don’t know why Sisulizer marked some context items as unused and created new, identical context items after updating/rescanning of source file. Maybe, items have been reordered in source file, etc. I can check it by comparing both versions of source file, if you still have this file, and upload it to us.


Best,
Janusz



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

 Posted: Fri Nov 9th, 2018 12:58 pm
PM Private Upload Quote Reply
MichaelV
Member
 

Joined: Mon May 25th, 2009
Location:  
Posts: 30
Status: 
Offline
Ok,

thanks. No problem. The files are from a database export. I dont have old one. May be, it is no ordered.
If i don't loose any translation, it is ok for me if there are double items.
But i was not shure about.

Michal

Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 20th, 2019 01:44 pm
PM Private Upload Quote Reply
MichaelV
Member
 

Joined: Mon May 25th, 2009
Location:  
Posts: 30
Status: 
Offline
Hello!

Again the problem returns, translatated lines get the state "1" in slp. Dont know why...
Sisulizer creates a new item to the node an moves all translated to state "1". I loose translations!
pls look at my file at the item "elementsize_glassweight" in slp file, it appears two times.

and another mystsery, if i purge with the command "remove unused items" the "elementsize_glassweight" is 2 times visible. Why?

Thanks Michael

Attachment: doubled.png (Downloaded 10 times)

Back To Top PM Private Upload Quote Reply

 Posted: Wed Feb 20th, 2019 03:40 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3237
Status: 
Offline
Dear Michael,
hard to say why these three rows do not match with the existing ones. Perhaps they missed while a Scan for Changes. Hard to say since there is no logfile for that in Sisulizer.
But don't worry:

If this happens you still have the old rows marked with a "Blue" dot.
So translations are not deleted. You never loose translations.

With one click to Project - Translate Duplicates you can re-use the translations in the new rows. If you choose Skip-All in the wizard only rows without translations will be translated by that.

Then you can use remove unused items.
And still your translations are not deleted. Sisulizer will move them into the embedded translation memory. You can re-use them with Project - Translate using Translation Engine - Use embedded.
And you always can import translations from previous project files.
But as said, the first option will already do the trick.
Markus



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

 Posted: Wed Feb 20th, 2019 04:16 pm
PM Private Upload Quote Reply
MichaelV
Member
 

Joined: Mon May 25th, 2009
Location:  
Posts: 30
Status: 
Offline
yes ok.
now i found a way that i can give you something reproduceable for the support.i will upload tommorrow.

the way that i can reimport is not possible, because our localization process is mostly automated.

Michael.

Back To Top PM Private Upload Quote Reply

 Posted: Thu Feb 21st, 2019 06:16 am
PM Private Upload Quote Reply
MichaelV
Member
 

Joined: Mon May 25th, 2009
Location:  
Posts: 30
Status: 
Offline
hello,

here ist somewhat reproduceable...
(i do a private upload with title "unused_item.zip")

in the archive is the slp and only one of our sources.
1. look into slp and search for <row id="elementsize_glassweight"> at first.
2. open slp with sisulizer
3. look for "locals.elementsize_glassweight" in the node "constructionwrapper.ini", eg. english. it is translated.
4. run actualisation (F5), sisulizer now marks the item with blue dot as unused, why?
5. run "remove unused items" now, the item ist shown as last, and klick ok.
6. now... there is a new node visible for "locals.elementsize_glassweight", all translations are lost now for this item.

thanks

Last edited on Thu Feb 21st, 2019 06:20 am by MichaelV

Back To Top PM Private Upload Quote Reply

 Posted: Thu Feb 21st, 2019 10:28 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3866
Status: 
Offline
I created my own sample SLP for your INI file, and this SLP behaves normally (there is no duplicate elementsize_glassweight context item). So maybe it occurred somehow during scan/build operation on your system, maybe as result of changes in the source file. But I can’t reproduce it for now.
Workaround:
By default, Sisulizer saves translations from removed Unused items to Translation Memory. If you use SlMake, you can use Translate command for re-translating those same originals without translations.
BTW:
Third instance of "Das erlaubte Glasgewicht von %1 wurde mit %2 überschritten." has different context (sashsize_glass).


Best regrds,
Janusz



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

 Posted: Thu Feb 21st, 2019 11:04 am
PM Private Upload Quote Reply
MichaelV
Member
 

Joined: Mon May 25th, 2009
Location:  
Posts: 30
Status: 
Offline
yes, i use slmake.

I created my own sample SLP for your INI file, and this SLP behaves normally (there is no duplicate elementsize_glassweight context item)
yes of course, in my sample this item is also unique. After scanning i have two :(

the key problem is, why sizulizer marks this line as unused, even though the lines is still in the source? it is exactly one times there (in both, my source an my slp).
with my sample with my files (at the scannig step) it is reproduceable. the scanner says:

<img src="BlueBall.gif"> = Unbenutzt Zeilenstatus. Dieses Element wurde im Ursprung des Projekts entfernt
13:01:08 Wählen Sie <b>Projekt | Nicht verwendete Objekte entfernen</b> um nicht verwendete Objekte zu entfernen

Thanks

Last edited on Thu Feb 21st, 2019 02:47 pm by MichaelV

Back To Top PM Private Upload Quote Reply

Current time is 09: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 > used items will be removed by funktion "remove usnused"



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