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: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
Differences in exported Excel - 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: Tue Apr 20th, 2010 11:42 am
PM Private Upload Quote Reply
danics
Member
 

Joined: Fri Nov 13th, 2009
Location:  
Posts: 39
Status: 
Offline
Hello,

I have some problem that has puzzled me.
In Sisulizer, I have a series of strings (I've selected the "Not translated" checkbox, so I only see the blank cells). Then I export to Excel, again only checking the not translated checkbox. This should produce in the Excel the same output as I see in Sisulizer, right?
But that is not the case.

Is this a bug or am I doing something wrong?

Best regards

Back To Top PM Private Upload Quote Reply

 Posted: Tue Apr 20th, 2010 06:41 pm
PM Private Upload Quote Reply
danics
Member
 

Joined: Fri Nov 13th, 2009
Location:  
Posts: 39
Status: 
Offline
I tried the same export on a translated and untranslated SLP file (only changing the checked Translation Statuses). I get on one of them 376 excel lines, and 363 on the other file.

So I guess this is definitely a bug.

Thank you in advance.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Apr 21st, 2010 02:00 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
Did you check Current view in Export Wizard. I found a bug here. Sisulizer did not use the current filer of the the current view but instead of filter on Export Wizard. I fixed this in build 303.

If you checked some other radio button but Current view I need to have you project file (.slp and .sds). Can you zip them and upload to me. Click Private Upload.

Jaakko



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

 Posted: Wed Apr 21st, 2010 05:59 pm
PM Private Upload Quote Reply
danics
Member
 

Joined: Fri Nov 13th, 2009
Location:  
Posts: 39
Status: 
Offline
I've sent you the file.
I've done it by exporting the slp file to excel, selecting only the “Not Translated” strings and excluding both the “Do not translate” and duplicate Rows.
Then, on the excel, I have strings that aren't shown on Sisulizer (even then I check all statuses on Sisulizer).

Thank you in advance.

Back To Top PM Private Upload Quote Reply

 Posted: Mon May 10th, 2010 11:10 am
PM Private Upload Quote Reply
danics
Member
 

Joined: Fri Nov 13th, 2009
Location:  
Posts: 39
Status: 
Offline
Hello!

I've installed the new build (305), but I still get differences...

Back To Top PM Private Upload Quote Reply

 Posted: Tue May 11th, 2010 03:00 pm
PM Private Upload Quote Reply
danics
Member
 

Joined: Fri Nov 13th, 2009
Location:  
Posts: 39
Status: 
Offline
Hello,

I've just noticed that this happens also in SLE files. After checking only the "Not Translated" box, in the statistics I get (for instance) 7000 unique strings, I export the project using the exchange wizard, selecting only the "Not Translated" checkbox, and filter selecting Data Types only String Data Types (as in Sisulizer) and "All duplicate rows" on the Other tab. Everything else is different. Still, when I open the exported sle/slp, checking the statistics always shows me less unique strings than I had initially.
This issue is stalling my project, could you give me a help?

Best regards

Back To Top PM Private Upload Quote Reply

 Posted: Thu May 20th, 2010 06:45 am
PM Private Upload Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Espoo, Finland
Posts: 2275
Status: 
Offline
Thank you for the files. I found a bug and fixed it in build 306. The problem was that your project was exchanged (e.g. sent to you for translation). Some of the rows were hidden in this process. However when Sisulizer exported the project data into Excel sheet it incorrectly included the hidden values (e.g. Data toolbar). This is now fixed. New build will be released late next week.

Jaakko



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

Current time is 08:20 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Differences in exported Excel



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