|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Problem with old projects - 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 ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
qnik Member
|
Dear Sirs, I have a problem with the project saved in the Sisulizer 1.6.23 and1.6.21 version. The first translator worked with the 1.6.21 version and sent the project (*.slp) file to the other translator for correction. The second translator worked with the 1.6.23. version. Now I have the 1.6.28 version and when I open the project I do not have any possibility to see single fields. Moreover, when I run the compilation, the program informs that about 1000 new phrases have been found! When I open the *.slp file in Notepad , the fields with the translations can be found in the project:
Nevertheless, Sisulizer cannot see them. When I click 'node:256', the list is empty, whereas I should see 'node:191' and the other ones. How can I correctly import the file with the project saved in previous versions 1.6.21 and 1.6.23 to the 1.6.28 version? Both projects (from Sisulizer 1.6.21 and 1.6.23) are in attachments. Best Regards Qnik Attachment: SisulizerProjects.zip (Downloaded 1 time)
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Ilkka.Salmenius Administrator 
|
There was a bug in 1.6.28 that rejected the custom binary strings. Unfortunally there is no work around. You have to wait till next version of Sisulizer. With the new version you can import the custom binary strings correctly. The new version will be released soon. regards Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Ilkka.Salmenius Administrator
|
You have two choices waiting for the next version of Sisulizer. 1. Return to use build 1.6.23. You can import and build without any problems. 2. Keep using the build 1.6.28. You can't import those string in custom binary folders. Those strings left untranslated. Later when you upgrade to the next version of Sisulizer you can import those missing strings. It however needs litte bit manually editing. I can give you specific intractions later. Keep the existing project files made by your translators in safe. regards Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
qnik Member
|
Thank you for answer! :-) Can you tell me, where I can find 1.6.23 Sisulizer Install Version? Qnik Last edited on Thu Jun 26th, 2008 03:40 pm by qnik |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi, we send you a PM with the password to access the area. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 02:40 am | |
| 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 > Problem with old projects | |
Sisulizer software localization tool - Three simple steps to localize
