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
Export Issue or is it me ?? - 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 Sep 8th, 2010 04:15 am
PM Private Upload Quote Reply
Fairport
Member
 

Joined: Wed Mar 24th, 2010
Location:  
Posts: 22
Status: 
Offline
Hi ...
The attached image tells the story.

I want to send an XLS file to my translator with just the 260 rows that need translating to keep the file size down.
But with the same filters set on the export wizard I'm getting 2900 + rows (includes all the Un-Used rows for some reason??)

I have also tried "Current Node" & "Current View" options - no luck
Using Version # 306

BTW, I have since created an SLE file using the "Exchange" menu option and it created a file, using the filters I had set, with just the 260 rows in it. So I'm happy ... but perhaps we have a bug to fix though.

 
Thanks
Roger

Attachment: sisulizer.jpg (Downloaded 25 times)

Last edited on Wed Sep 8th, 2010 05:42 am by Fairport

Back To Top PM Private Upload Quote Reply

 Posted: Wed Sep 8th, 2010 08:11 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 2542
Status: 
Offline
Hi Roger,

Could you upload to us your SLP file (not SLE)? I'd like check this issue with your project.

Best regards,
Janusz



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

 Posted: Wed Sep 8th, 2010 10:51 am
PM Private Upload Quote Reply
Fairport
Member
 

Joined: Wed Mar 24th, 2010
Location:  
Posts: 22
Status: 
Offline
I have uploaded the file Janusz

... thanks
Roger

Back To Top PM Private Upload Quote Reply

 Posted: Wed Sep 8th, 2010 06:55 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


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

I don't know contents of your export file, but seem to me that I found potential reason of your issue.

Export Wizard:
If you save only not translated items for one language to exported file, count of items saved to XLS file should match with number of not translated strings in this selected language. But when you save to exported file more languages, Sisulizer needs save not translated items for all added languages.
For example in Spanish we have not translated A and B strings and in Portuguese not translated C and D strings.
- When you save only Spanish to XLS file, Sisulizer saves to XLS file 2 strings (A, B) and count of items in XLS file matches with count of not translated items in Spanish column.
- When you save only Portuguese to XLS file, Sisulizer saves to XLS 2 strings (C, D) and count of items in XLS file matches with count of not translated items in Portuguese column.
- When you save both languages to XLS file, Sisulizer should saves all 4 strings (A, B and C, D) and count of items in XLS file doesn't match with count of not translated items in Portuguese or Spanish column.

Exchange Wizard:
- When you use "Create several packages, one for each selected language" option with  Exchange Wizard, Sisulizer create separated packages for all selected languages, and for this reason count of items added to SLE file should match with count of not translated items in selected language.
- When you use "Create one package that contains all selected languages" one for each selected language" option, Sisulizer should add up to to SLE  all not translated items for all languages (like in our example with Spanish and Portuguese items exported to XLS file).

Solution:
Export - create separated XLS files for each project's language.
Exchange - use "Create several packages, one for each selected language" option.

Let me know if my speculations about your export workflow are wrong.

Best regards,
Janusz



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

 Posted: Mon Sep 27th, 2010 02:41 pm
PM Private Upload Quote Reply
eitangabay
Member
 

Joined: Mon Sep 6th, 2010
Location:  
Posts: 35
Status: 
Offline
Thanks for you reply,

It was very helpful.

Back To Top PM Private Upload Quote Reply

Current time is 08:06 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Export Issue or is it me ??



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