|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Message Table incorrect translation!
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Message Table incorrect translation!
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Message Table incorrect translation! - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Larisa Filonova Member
|
Hi, I have a problem with Message Table translation. I can't say what exactly Sisulizer does wrong, but the fact is that after UDV.dll translation all messages in my Software are mixed. I made a very simple test. I translated only one string in Message table first via Microsoft Studio and second via Sisulizer. By the way, I didn't change neither original language nor string length nor string number. The original language is English (USA). Original string in Message Table (in UDV.dll): Operand expected Changed to: Operabj expected 1) In Microsoft Studio translation is correct. After this translation everything works fine in my Software. 2) In Sisulizer translation something went wrong. All messages are mixed. I mean that in my software message like: End of stream detected – may appear instead of: Infix operator expected. So, it’s a total mess. I tried to analyse (please see may attachement). I tried to find the clue: What is the difference between Microsoft Studio translation and Sisulizer translation? Why does Message Table work fine after Microsoft Studio translation and doesn’t work fine after translation via Sisulizer? Please, help me to find the answer. Larisa Attachment: Screenshot.gif (Downloaded 22 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Could you upload to us UDV.dll file? Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Larisa Filonova Member
|
Hello, Janusz! I've just sent you the original UDV-file. Thank you. Larisa
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello Larisa, Currently, I work on PC without VS, so I performed my tests with simple tool named Resource Hacker. Your message table has odd numerical ID order of strings, that is after 93 follows 1 (while next item in numerical order is 96), and it is reason of mixed up strings. I compared message table from your source file and Sisulizer output file (wit empty translations) in Resource Hacker, and on below screenshot you can see results - all items after 96 are mixed up. Attachment: screen.png (Downloaded 17 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Next I recompiled resource in Resource Hacker and it fixed order of items in message table (look on below screenshot). Then I re-scanned Sisulizer project and built output file. Now both files are identical and re-compiling source files fixed issue. BTW: Left instance of Resource Hacker shows source file, right - localized output file. Best regards, Janusz Attachment: screen1.png (Downloaded 15 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Larisa Filonova Member
|
Janusz, Thank you for the idea! I've just installed Resource Hacker. Could you please share your experience? Compile Script button is inactive on my computer. How did you recompile resource? Larisa
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Larisa Filonova Member
|
Janusz, I found the answer. Once more, thank you for good advice!
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Larisa Filonova Member
|
Hi, Janusz, I have one more question. I make translation from English (USA) to Russian. I can't change the original language in UDV.dll because if I do so it will cause a problem in my Software. So, I chose English (USA) for translation but I typed in Russian. Everything is quite Ok with string table and dialogs. It is possible not to change the original language but type in Russian. I made tests, Sisulizer works fine. But there is a problem with Message table. Sisulizer translates like: ??? ?? ?????. So the question is why in my case Sisulizer works fine for dialogs and sring table and can't translate properly Message table? Thank you in advance. Larisa
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Larisa Filonova Member
|
Hi, Janusz, I found option in Sisulizer - Keep original resource language id. It solves my ploblem. Regards, Larisa
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello Larisa, Sorry for late reply, but I was on short trip during weekend - we have here excellent vacation's weather. I found option in Sisulizer - Keep original resource language id. It solves my ploblem. I'm glad you found solution for your issue. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:06 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Message Table incorrect translation! | |
Sisulizer software localization tool - Three simple steps to localize
