|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Some questions while evaluating Sisulizer
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Some questions while evaluating Sisulizer
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Some questions while evaluating Sisulizer - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
tk Member
|
Hi, I am still evaluating Sisulizer. Before purchasing and using the software, I have some questions regarding the handling: - I found out that the output directory can be defined in Edit Source menu. We have .NET files and need satellite assemblies in subdirectories like de-DE, en-GB ..., while Sisulizer as default creates only de, en directories . I saw that this can be changed manually in the dialog like <net>-DE . Here the questions: is there a common parameter for this? Can I set this as default for the complete project? Our translation project will contain about 30 assemblies and doing that for each source file is quit boring. Is this setting project based or language dependent? I want to have all languages on one project and the output should be automatically recognise the active language and the create translated assemblies on the correct subdirectory. - when adding files to a project, existing and already translated files on subdirectories are recognised and the translation is added to the project. So far so good, but Sisulizer in the case ignores identical expressions and marks them as "not translated", e.g. is there a german label "Name" and the english translation is "name", then this entry does not appear in the translation list and has to be retranslated (what happens very often in our software) Thomas
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi tk, a) Sisulizer follows the needs of the .NET framework. Creating de sub-folders is the right way for top level languages. de-DE stands for a sub language like German as spoken Germany (there is also Austria, Switzerland...). If you want that you have to set these in Project - Languages. There you select German - Germany. The Sisulizer will create de-DE. Please be aware that not all languages have sub-languages e.g Finnish. Using fi-FI would be wrong and the .NET framework could not load the sattelites. b) Have you tried Project - Translate Duplicates? Double check with Tools- General... Translations - Update translations of duplicate strings. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello,Please be aware that not all languages have sub-languages e.g Finnish. Using fi-FI would be wrong and the .NET framework could not load the sattelites. Luckily Sisulizer allows you to avoid similar cases, because if you have unchecked option “Tools” menu > “General” > “Languages” tab > “Use sublanguage when a language has only one sub language”, Sisulizer during adding new languages to project doesn’t show sublanguages if language hasn’t more than one sublanguage. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Short update: fi-FI would work in .NET as well. Thanks to our R&D for the info... Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
tk Member
|
Hi, OK, I followed your instructions and it looked as if I was on a good way. One comment, I added korean language to the german / english and had to rename the output directory from ko to ko-KR, otherwise our software doesn't load the language. Maybe that is our problem but the current passolo version automatically creates ko-KR . The bigger problem appeared after I created new output files, both for english and korean and in both languages our software throws a number of exceptions when trying to open dialogs. There is not a single dialog I can open. I assume that comes from the unsolved components due to the obfuscation. If you are interested in making a test you could download a version fróm http://www.cygnicon.de . German and english language is included so you could try it out without the need to translate the software :-). Thomas
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Just to make sure: Do you use the latest build. There was a change for obfuscation in the latest build. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
tk Member
|
Build 285, Date 27.05.09
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Can you please make a test without obfuscation to find out if that is the reason? Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
tk Member
|
Hi, I have checked this. Obfuscation is not the reason. Thomas
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hmmm, The pity is, that in the moment our R&D is very busy and I can not ask them to register to your website, install your application, get it running and test with it. While your demo is so huge could you please send us the DVD with the demo on it so we have it when R&D resources become available? Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
tk Member
|
sure, will do. Postal address and receiver?
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Just send it to our sales office: Sisulizer Ltd & Co KG Graf-Salm-Str. 34 50181 Bedburg Germany Thanks in advance. I'll try it here and depending on what I find I'll bypass info to our R&D so they can look into it more quickly. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, Thanks for the DVD. To get the same environment for the tests as you: Would it possible also to get your .snk file via Private Upload? Perhaps you could also add your .slp file so I get some idea what you did. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Thank you for the files.However I coulnd not reproduce the error. Can you check that the DVD that you end use contains the same EXE and DLL files that you are using. Also can you send me your Sisulizer project file (.slp). Zip .slp, CACAD.exe and *.dll files ino a zip file and press Private Upload button. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Regarding the ko-KR: Go to Tools - General - Languages and check: Use sub language if... This will add the -KR part. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 02:07 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Some questions while evaluating Sisulizer | |
Sisulizer software localization tool - Three simple steps to localize
