|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Different output command line / Sisulizer program with XML
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Different output command line / Sisulizer program with XML
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Different output command line / Sisulizer program with XML - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Christine Member
|
Dear all, we do the following: a) "create" command with the command line tool b) "build in selected language" with the Sisulizer program With XML resources, the built outputs of (a) and (b) are different. (a) produces a wrong output: translations are mapped to wrong originals. If we make a scan in Sisulizer first, the output of (a) is correct. We tried to combine "scan create" or to make a "scan" in the command line first before "create", but this did not solve the problem. In other words, there seems to be a difference between the scan and/or build between Sisulizer and the command line tool. Question: Is this a bug or are we missing a parameter in the command line? Please find a zipped file in Private Upload: Original: Sisulizer_2010-8-24\PresetRepository.xml a: Sisulizer_2010-8-24\CMD_PresetRepository.xml b: Sisulizer_2010-8-24\GUI_PresetRepository.xml We are using Sisulizer 2008, build 301. Thanks in advance, Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello Christine, Thank you for files. I tried reproduce issue with these files, but SlMake produced identical file as Sisulizer (UI), and after SlMake's create command I've got new, unused and changed items in project. Could you check, if after create operation SlMake displays information about changes (like on below screenshot)? Best regards, Janusz Attachment: screen.png (Downloaded 22 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, I tested your file with latest Sisulizer build, while you use build 301. Could you update your Sisulizer and check this issue again? Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Christine Member
|
Dear Janusz, thank your for the quick response and the information that the problem is already fixed in version 307. I tested it and it seems to be working fine. Thanks, Christine
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello Christine, Thank you for information, I'm glad it solved your issue. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:24 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Different output command line / Sisulizer program with XML | |
Sisulizer software localization tool - Three simple steps to localize
