|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Forwards compatibility of Sisulizer
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Forwards compatibility of Sisulizer
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Forwards compatibility of Sisulizer - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Dmitry Member
|
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 |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
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 |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Dmitry Member
|
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 |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Renate.Reinartz Administrator 
|
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 |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:52 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Forwards compatibility of Sisulizer | |
Sisulizer software localization tool - Three simple steps to localize
