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.

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
Bug in 1.6.28 when creating EXE - 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 ...
AuthorPost
 Posted: Fri Jun 6th, 2008 06:19 pm
PM Quote Reply
PhilipFlesher
Member
 

Joined: Fri Jun 6th, 2008
Location:  
Posts: 3
Status: 
Offline
We're running the Exchange Wizard to produce an EXE containing the 1.6.28 translator to be sent to our localizers.  When they run the EXE, they can successfully complete setup and open the project, but when they try to Import (File, Import), a dialog immediately pops up containing the text:

The system cannot find the path specified

This is a critical issue for us to resolve immediately.  Any assistance would be appreciated.

Thanks,

Philip Flesher (NCsoft Corp.)

Back To Top PM Quote Reply

 Posted: Fri Jun 6th, 2008 07:34 pm
PM Quote Reply
Renate.Reinartz
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 43
Status: 
Offline
Philip,

Importing should work without problems in 1.6.28. Have you tried to resend the file? May be a byte is wrong. Sometimes this happens.

Did I got you right that the dialog immediately appears after you selected File - Import? Or does it occur after your translator selected a file?

If the problem still occurs, please send the file to
support (at) sisulizer (dot) fi
with a short description of your problem.

I hope this helps

Renate



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

 Posted: Fri Jun 6th, 2008 07:56 pm
PM Quote Reply
PhilipFlesher
Member
 

Joined: Fri Jun 6th, 2008
Location:  
Posts: 3
Status: 
Offline
It happens immediately after selecting File - Import.

This isn't a file corruption problem, as we've tried it multiple times now on various different machines.  We went back and tried 1.6.19, and it works fine.  Until we can get this issue resolved, we can't use the latest version.

I'll send an email with the attachment soon.  Thanks!

Back To Top PM Quote Reply

 Posted: Sat Jun 7th, 2008 04:54 am
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1641
Status: 
Offline
I don't need the EXE but the file to be imported would be good and the orignal Sisulizer project file (.slp)

Also what was the localization of Sisulizer project they opend and what was the location and type of the file they tried to import.

Can you zip both of them and send to

support (at) sisulizer.fi

Jaakko



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

 Posted: Mon Jun 9th, 2008 03:01 pm
PM Quote Reply
PhilipFlesher
Member
 

Joined: Fri Jun 6th, 2008
Location:  
Posts: 3
Status: 
Offline
There's no "file to be imported". We took the SLP, opened it in Sisulizer, and used the Exchange Wizard to convert it to an EXE (so the Sisulizer app goes along with the project). We can then take that EXE and run it correctly, installing Sisulizer on another machine and opening the contained project. However, clicking Import in the File menu then causes the aforementioned error dialog immediately.

So the only thing I could send you that would be of any help is the project file itself. I'll send that now.

Back To Top PM Quote Reply

 Posted: Mon Jun 9th, 2008 10:40 pm
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1641
Status: 
Offline
OK. Where (drive and location) did translator install EXE? What is his OS?

Can you send me Sisulizer settings file, Sisulizer.slo, from translator's computer. If OS is Vista it is on <Personal folder>\Sisulizer\Sisulizer.slo. If OS is XP or 2000 it is on the directory where you installed Sisulizer

Jaakko



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

 Posted: Tue Jun 10th, 2008 12:53 am
PM Quote Reply
Jaakko.Salmenius
Administrator


Joined: Sat Apr 8th, 2006
Location: Tokyo, Japan
Posts: 1641
Status: 
Offline
No need to send any files. I managed to reproduce. There was a bug in Sisulizer. I fixed it. I could not fix this in 1.6 but fix will be in Sisulizer 2008 that will come out this month.

There is a workaround. The translator must have the original assembly files that the Sisulizer project contains: _Launcher.exe and NCLauncer.exe. Their relative location to Sisulizer project on transators computer must be the same as you have:
..BuildcurrentProductFiles_Launcher.exe
..BuildcurrentProductFilesNCLauncher.exe

Jaakko



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

Current time is 04:38 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 > Bug in 1.6.28 when creating EXE



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