|
|||
|
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 > Import Problems from Multilizer (6.2.19)
|
|
|||
|
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 > Import Problems from Multilizer (6.2.19)
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Import Problems from Multilizer (6.2.19) - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
mac500 Member
|
Hallo, we developed and maintain a big ERP system in Delphi and used Multilizer for the translation. Since we were very disappointed about the quality and support from Multilizer we bought Sisulizer Enterprise. We tried to import our project as described with dll, drc, dpr and the resource dlls .de, .en, .fr but we ended up in numerous of problems like access violations and lots of missing translations. It is very difficult to describe the whole process and all problems, but we think we found one main major problem. During an Import, when the *.drc files are in a different folder as the DLL and the .DE, .EN, .FR files, the Resource String translations are not imported (In Sisulizer in the tree under -> Strings). In our Delphi Project the drc and dpr files are located in : R:\Hits2000\Client\AccountingManager but the DLLs and the Resource DLLs (DE, EN, FR) are located in another folder : R:\Hits2000\Client\bin In this case we get one warning per resource file : 20:00:58 Scanning file "R:\Hits2000\Client\bin\HitsAccountingManager.DE" 20:00:58 Warning DRC file is missing. Without it resource string ids may not be fixed. Right click source and choose Properties... | Options. and the resource string translations are not imported. I put the files together that you need to reproduce the problem and attached them as archive. There is a workaround (you need to move the drc files to the same folder as the binaries are, import then into Sisulizer and then move them back), but for us this is very difficult, because we have very many projects in the BDS group. Importing the Multilizer MPR failed completely with very many missing translations, same warnings for missing drc file and when you selected this warning row in the message list, we got an exception. Maybe this is all for the same reason as above. We would be very happy if you could fix this problem and supply us a detailed description how the preferred way works to import an existing Multilizer project. Best Regards Olaf Kehm Attachment: Susilizer.rar.zip (Downloaded 4 times)
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
How did you import resource DLL to the project. 1) Did project managed import them automatically or 2) Did you imported them one by one by choosing File | Import Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
I tested your project by importing each resource DLL into the project one by one. I clicked the column header of the language column and choosed Import. See screenshot. Sisulizer imported eveything correctly. I was using Sisulizer 1.6.24 Jaakko Attachment: untitled.PNG (Downloaded 29 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
mac500 Member
|
Hi Jaakko, Thanks for your reply. There may be a few workarrounds with a lot manual work, but our project has plenty of DLLs. It would be a pain if we would have to click in each project each column and import manually each language. This is the way how you can reproduce the bug : File -> New -> Localize a file or files -> Select one DLL -> Delphi binary file-> There are existing translations for >DE/EN/FR-> Select Yes -> Leave all Windows Resources checked -> Next -> Check just Resource DLLs Select as Output files : DRC file name -> R:\Hits2000\Client\AccountingManager\HitsAccountingManager.drc Optional project file name -> R:\Hits2000\Client\AccountingManager\HitsAccountingManager.dpr Note that these pathes are different than the path to the DLL ! Next -> German, English, French is preselected -> Select English as original language -> Finish No strings are imported. There is another conceptional bug: When you select not just one DLL in the described way from above, but more than one, there is no way to specify for each DLL the location of the corresponding drc file. You just can select ONE drc file. This makes the import of a whole Delphi project which has more than one DLL impossible. But this should be the way how to import projects with multiple DLLs and our prefered way. Best Regards Olaf Kehm
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi Olaf, Sorry about this delay. I was few days out of officer but I am now working on this case. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
mac500 wrote: This is the way how you can reproduce the bug : I tested this with 1.6.24 and it imported all existing strings. Did you try 1.6.24? Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
mac500 wrote: There is another conceptional bug: The current logic makes it possible to enter only one DRC (the DRC of the first file). I start thinking a way to enter them all. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Jaakko.Salmenius wrote: mac500 wrote:This is the way how you can reproduce the bug : Wait a moment. I found one bug that caused that in this case Sisulizer did not properly used DRC. I will fix this on 1.6.25 Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
There was a bug that caused Sisulizer not to use the given DRC when importing if the DRC file was not on the same directory as the imported DLL. I fixed this in 1.6.25. The new version will come later this week. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
mac500 Member
|
Hi Jaakko, sorry for the delay. Thank you very much for reproducing the issue. I am very happy to hear that you could fix the problem. It still will help us a lot. We appreciate this quick support a lot. Best Regards from Hamburg Olaf
|
|||||||||||||
| ||||||||||||||
| Current time is 04:39 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) > Bugs and Quirks in Sisulizer > Import Problems from Multilizer (6.2.19) | |
Sisulizer software localization tool - Three simple steps to localize
