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
Forwards compatibility of Sisulizer - Wish list for software localization tool - 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: Tue Jul 15th, 2008 12:00 pm
PM Quote Reply
Dmitry
Member
 

Joined: Thu Jul 10th, 2008
Location: Haifa, Israel
Posts: 7
Status: 
Offline
Hi.

After upgrading to Sisulizer 2008, loading an .SLP project created in a previous version, modifying and saving it made the project incompatible with the previous version. Trying to build it with older version SLMake resulted in error: "TPictureRow class nof found".

Is it a known problem?



____________________
- First we learn that memory leaks are impossible in the CLR. Later, when our app consumes all available RAM, we learn more. (c) Eric Sink
Back To Top PM Quote Reply

 Posted: Tue Jul 15th, 2008 12:14 pm
PM Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 829
Status: 
Online
Hi Dmitry,

Sisulizer projects are not meant to be downward compatible. They are only forward compatible. Why don't you use the SLMake coming with V2008 to build your project?

Markus




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

 Posted: Tue Jul 15th, 2008 12:29 pm
PM Quote Reply
Dmitry
Member
 

Joined: Thu Jul 10th, 2008
Location: Haifa, Israel
Posts: 7
Status: 
Offline
We did :)

Later, when it was apparent that there is version incompatibility.

We had a build server and a couple of workstations, on WS machines we manage the translations and on Server we make the build.

I've upgraded my WS, but the server was not upgraded, which caused the build error. It did not occur to me that there would be problems in that area.

I still think there is a place for a warning of sorts. It would be nice if SISUlizer, when loading older .slp and saving it in new version, would give a warning that format has changed which would make the .slp incompatible with older versions, and it would also be nice if during the build it detected the version mismatch and issued a similar warning instead of breaking the build.



____________________
- First we learn that memory leaks are impossible in the CLR. Later, when our app consumes all available RAM, we learn more. (c) Eric Sink
Back To Top PM Quote Reply

 Posted: Tue Jul 15th, 2008 12:58 pm
PM Quote Reply
Renate.Reinartz
Administrator


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

I moved the thread into the wish list because of your wish to give out a warning when saving a project from an older version.

Anyway in your case I have checked our license database and you should already received updates for all your licenses. Please ask your collegues.

Best regards,
Renate



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

Current time is 12:23 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) > Wish list for software localization tool > Forwards compatibility of Sisulizer



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