Problems in getting correct Exchange output SLE file - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ...

Support forum of the software localization tool Sisulizer

Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... 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.

Not logged in - Login | Register

Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Problems in getting correct Exchange output SLE file

Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius

Printer Friendly

Problems in getting correct Exchange output SLE file - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ...

Author

Post

Posted: Wed Nov 5th, 2008 03:56 pm

kuykens
Member

Joined:	Sun Sep 2nd, 2007
Location:	Amsterdam, Netherlands
Posts:	13
Status:	Offline

Hi all,

I have been struggling to produce an Exchange SLE file for our translators. We have produed such file to communicate earlier with the translators. When receiving their translated resources some strings appeared to be missing or untranslated. I thought (and still cannot exclude) that they procued the defect. However, when attempting to recreate a package that contains all the missing or faulty stuff I am having a very hard time to get a proper export file.

I am using the exhcange wizard to create a SLE project file. I ensure that nothing is filtered in my current view and have selected the main (All) branch in Sisulizer.
I than startup the Wizard with:
only include items where Translation status : untranslated or For review

I know that in my source project file the Spanish translation misses some 40 items. Sometimes the exported SLE file misses most of these entries.
Then again, in some exports I noticed that a set of dialog initialization items is missing

I tried a couple of times but was unable to get a consistent set that I trust.
Do you have any suggestions to solve this?

regards: Hans

Posted: Wed Nov 5th, 2008 04:41 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

Hello Hans,

Yesterday you sent to us your Sisulizer project, and I'll try to test Exchange feature behavior with your project. I let you now about results of my tests, but I afraid that it could be hard to reproduce without additional information, and maybe when I couldn't reproduce it I'll ask you about some additional information and files.

Best,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Wed Nov 5th, 2008 04:42 pm

kuykens
Member

Joined:	Sun Sep 2nd, 2007
Location:	Amsterdam, Netherlands
Posts:	13
Status:	Offline

I can send you some of my findings as report HTML files...

Posted: Wed Nov 5th, 2008 04:48 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

Thanks, it could be useful for us

Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Nov 6th, 2008 08:07 am

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

Thank you for the files. I am working on this.

Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Nov 6th, 2008 12:09 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

Hello,

I made several tests of Exchange feature behavior with your SLP file, and I've got following results:

1. When I chosen only one language to export e.g. Dutch or Spanish, with following settings:
- "For review" and "Not Translated" statuses
- String and XML as exported Data Types
I've got always correctly results, that is, all "For review" and "Not Translated" items were included to SLE file.

2. I reproduced your issue when I chosen all language to export (instead one language), that is NOT all required "For review" and "Not Translated" items were included to SLE file. All other Exchange settings were identical as in first point (export to one language)

I'll continue investigation and let you know about results.

Best regards,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Thu Nov 6th, 2008 12:16 pm

kuykens
Member

Joined:	Sun Sep 2nd, 2007
Location:	Amsterdam, Netherlands
Posts:	13
Status:	Offline

OK, thanks. I will need to proceed with our translation process so will find a way to communicate the present translation set with our translation buro.

Posted: Thu Nov 6th, 2008 02:50 pm

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

Hello Hans,

I reproduced issue also with other projects and I found reason of incorrectly export. Sisulizer use "For review" and "Not translated" statuses for export, but only for currently edited language in main project. So if you edit Dutch language when you export translations to SLE, Sisulizer save correctly all "For review" and "Not translated" Dutch items to export file, but not for other languages. I'll forward it to our developers.

Best,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Fri Nov 7th, 2008 10:52 am

kuykens
Member

Joined:	Sun Sep 2nd, 2007
Location:	Amsterdam, Netherlands
Posts:	13
Status:	Offline

We are considering updating to V2008 but I read from your reply that this is not (yet) solved in this version either, right?

Posted: Fri Nov 7th, 2008 11:11 am

Janusz Grzybek
Super Moderator

Joined:	Fri Dec 1st, 2006
Location:	Zabrze, Poland
Posts:	564
Status:	Offline

Yes, this is not implemented yet, but I forwarded all necessary information to our R&D, and we should to wait on our developers answer.

Best,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Sun Nov 23rd, 2008 06:14 am

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Tokyo, Japan
Posts:	1641
Status:	Offline

There was a bug when Sisulizer created the exchanged project file (.slp). The translation status filtering was always done based on the current language and not the language that was actually being written.

I fixed this in 276. The new build will come in few days.

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Current time is 04:37 pm
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Problems in getting correct Exchange output SLE file

WowUltra 1.11 Copyright © 2007 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize