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 
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Any hints for migration from Sisulizer 1.6?

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
Any hints for migration from Sisulizer 1.6? - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Wed Sep 25th, 2019 02:38 pm
PM Private Upload Quote Reply
cfischer
Member
 

Joined: Wed Apr 12th, 2006
Location: Berlin, Germany
Posts: 123
Status: 
Offline
 Hey,
are there any tutorials / FAQs / hints available regarding a migration of SLPs from Sisulizer 1  to Sisulizer 4?
(1.6.5 to 4.0.374)

I.e., as far as I can see, the context has been changed.
This may (!) lead to the weird behaviour that the 1.6 SLP is opened without any complaints, but after scanning (source files available) all rows are marked as "unused" now.

Regards,
Carsten
Back To Top PM Private Upload Quote Reply

 Posted: Wed Sep 25th, 2019 04:05 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3322
Status: 
Offline
 From 1 to 4... a rare situation...
Apply the translations "by value" using Translate Duplicates. Of import the translations from your old project "by value". While the context changed you still have the link by value.

Sisulizer will re-use the translations from the unused rows if the value matches. That's the reason the unused rows are in your project.
Markus



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

 Posted: Thu Sep 26th, 2019 06:18 am
PM Private Upload Quote Reply
cfischer
Member
 

Joined: Wed Apr 12th, 2006
Location: Berlin, Germany
Posts: 123
Status: 
Offline
 Thank you for the quick support ;)

I think we will even re-create these projects with Sisulizer 4 and import all the existing translations. This should prevent all further side effects.

C.
Back To Top PM Private Upload Quote Reply

 Posted: Thu Sep 26th, 2019 06:23 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3322
Status: 
Offline
 Yes, thats a perfect plan!

Markus



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

Current time is 08:54 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Any hints for migration from Sisulizer 1.6?



WowUltra modified by Sisulizer Copyright © 2007-18 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize