|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Mismatch of Simplified Chinese and Traditional Chinese
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Mismatch of Simplified Chinese and Traditional Chinese
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Mismatch of Simplified Chinese and Traditional Chinese - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
starr Member
|
Please look at this project: http://rapidshare.com/files/143273158/CL264decTest.zip.html The original should be Chinese, Traditional (Taiwan) instead of Chinese, Simplified (Taiwan) though it actually contain resources in English. You can try creating a new project with the dll file and you'll find the resource wrongly identified. And it seems that the file is packed so the target dll created is corrupted. However, if you use some professional resource editor such as ResScope (http://www.restools.net) to edit it and save it the file still works. I think it just creates the target without changing the size of the resource section and simply makes a copy of other sections. So I wonder how Sisulizer deals with such situation. What about adding an option to disallow the program to modify the resource size and keeping all other things intact? Thanks.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Thank you for found it. I have reproduced this issue both for Delphi source and Visual C++ source, and for new project during adding languages in "Select the original language of the source" visible is "Chinese, Simplified (Taiwan)" instead "Chinese, Traditional (Taiwan)". Name displayed during wizard is incorrectly, but Sisulizer correctly recognize language, because in tab "Encodings" of source properties displayed is correctly name "Chinese, Traditional (Taiwan)" (look on screenshot). Mixed up Chinese Tradional/Simplified name appear only for files with multiple original languages. For one original language, name of original language are displayed correctly (your file have English language setting for Dialog resource and Chinese Traditional for all other resources). Best regards, Janusz Attachment: screen1.png (Downloaded 49 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
starr Member
|
Fortunately it seems to be a display issue only. I think it easy to fix. Then what about another issue I reported?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
I fixed the first issue in build 271. However the other issue is is difficult. Our policy is that Sisulizer does not work on crypted or compressed PE file (.exe, .dll). There are many reson for this: 1) There are several different way to crypt/pack and also several way to decrypt and pack. This is something we should not do. File is packed or crypted for a reson. 2) However localizes a PE file should have acces to the original non-crypted/packed PE file. The vendor of the file has the original and it should be easy to ask the original file for localization purposes. 3) There is also a major technical problem to read crypted/packed file. The formats (there are many of them) are not public and we definetely do not know them. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
starr Member
|
So I partially agree with your stand, however, why not adding an option to disallow the change of the file size? For instance, Visual Localize will not change the target's file size by default. eXeScope also has an option to prohibit touch the resource's size. I think Sisulizer can also follow the pattern that is just not to modify the resource's size and keep ALL OTHER stuff intact (such as header or data sections).
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
starr Member
|
So I partially agree with your stand, however, why not adding an option to disallow the change of the file size? For instance, Visual Localize will not change the target's file size by default. eXeScope also has an option to prohibit touch the resource's size. I think Sisulizer can also follow the pattern that is just not to modify the resource's size and keep ALL OTHER stuff intact (such as header or data sections).
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
The point is that we can not safely read and write crypted or packed PE files. The format differs from PE file standard. Sometimes Sisulizer can correctly read crypted resources but in most cases if we modify such resources they are not valid any more. Keeping the original resource size does not solve the problem. We can not modify these PE files. There is a simple solution: use the original PE files created by compiler (e.g. Visual Studio or Delphi) Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
We could add an option that keeps the resource size as it was in the original. But this would work only if the translations fit into that original resource size. On the others words the translations havt to be shorter or equal than original. Or can be little bit wider if still fit to the same segment (segments are allocated by 512 bytes). It is very likely when you translate for example from english to german that the translations will become so much wider that don't fit into the same resource segment as original. In that situation Sisuluzer have to grow the resource segment. regards Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
starr Member
|
Why I think it reasonable is for that for English-Chinese translation the length of the target's resource is almost always shorter than the original one. I know it is varied between different language combinations, but at least it helps to reduce some problem under lots of situations. So why not adding this option? 
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Starr, we discussed the issue internally. Here is the opinion we share on this: a) we should not do anything that gets Sisulizer close to a hacker tool. It should not work on protected binaries. There is a reason for the protection and we have to respect that. b) Sisulizer should always work the same for all language pairs. It is not an option that Sisulizer can build a encrypted or protected binary from English to Chinese but if you try to build the German version it says, sorry, bad luck, segment to long. Please ask the vendor of the software to provide you an unprotected binary of his software. If he likes to have a localized version he will not hesitate to do that. If he does not want to authorize you for the localization of his binary (an encryption or obfuscation of a binary is a clear STOP sign) there is nothing we are willing to do - even while it id technically possible for our R&D. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
starr Member
|
Dear sir, I understand your concern and appreciate your effort to improve the program. However, I must argue that I suggest you add this feature NOT to make a so-called hacking tool. In fact even with this feature no one can crack nothing. What I actually recommended is that you can add another way to deal with the resources as other competitors do such as Visual Localize, whose developer is German and I believe they master the English-German translation better. You can try VL and take a look how it treats the resources. Nevertheless it is always glad to see Sisulizer to get better as it is promising in comparison with other similar programs.
|
||||||||||||||||
| |||||||||||||||||
| Current time is 06:27 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Mismatch of Simplified Chinese and Traditional Chinese | |
Sisulizer software localization tool - Three simple steps to localize
