|
|||
|
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) > Usage - Three simple steps to localize > Problems converting Multilizer project
|
|
|||
|
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) > Usage - Three simple steps to localize > Problems converting Multilizer project
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Problems converting Multilizer project - Usage - Three simple steps to localize - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Frede Member
|
I have big problems converting old multilizer project These are some the issues I encountered when opening a ML project. Sometimes SL simply freezes when importing and I have to kill it using task manager. Properties are not the same after import. For example I've excluded bitmaps and different forms etc. from being translated but after import they are back in the SL project. This has the result that although I translated 100% in ML the statistics page in SL tells me that 34% is "Not translated" after import to SL. It complains that XML files "contains different amount of 'row' elements than the original file in the project" I have no idea what this means. A project takes forever to load. Import for our ML project took well over an hour to complete and it appears to run the same sequences over and over and gives the same error messages about the same files more than once. Can you assist in converting our project or what is the best way to convert an existing ML project? Our project contains XML files, Delphi Win32 executables, .NET assemblies. The project is in Multilizer for Developer 6.2.19. Thanks /Fredrik
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Can you send your existing Multilizer project file (.mpr) to me at support (at) sisulizer.fi You you have one single MPR thta contains all XML, EXE, etc or separate MPRs for each file. In order to test the MPR -> SLP conversion I also need the the original file (e.g. XML or EXE) and the most recent localized files created by Multilizer. When SL converts .MPR to .slp it creates a new .slp that contains the same file. Then it imports translations from existing localized file (if existing) and if not then from .MPR. This is why you have to have most recent localized files created by Multilizer. If you have a MPR that contains only one source (e.g. one XML or one EXE) that would be very good place to start. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 05:13 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) > Usage - Three simple steps to localize > Problems converting Multilizer project | |
Sisulizer software localization tool - Three simple steps to localize
