|
|||
.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 |
|
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 | |||||||||||||||||
Author | Post | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
cfischer Member
![]() |
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
|
||||||||||||||||
|
| |||||||||||||||||
Markus.Kreisel Administrator ![]()
![]() |
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 |
||||||||||||||||
|
|
|||||||||||||||||
cfischer Member
![]() |
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.
|
||||||||||||||||
|
| |||||||||||||||||
Markus.Kreisel Administrator ![]()
![]() |
Yes, thats a perfect plan! Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
|
Current time is 05:57 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? |
Sisulizer software localization tool - Three simple steps to localize