|
|||
|
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) > Wish list for software localization tool > Multi-Modifications of Controls in FORMS for MULTI LANGUAGES
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Multi-Modifications of Controls in FORMS for MULTI LANGUAGES - Wish list for software localization tool - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
DREYFUS Member
|
OBJECT : Multi-Modifications of Controls in FORMS for MULTI LANGUAGES Probably as many users of SIZULIZER I am doing multi languages (12) translations of applications : So the problem is going to be the SAME for most of us .... HOW to do ONLY ONCE the enlargement of Text zones in FORMS when you have NUMEROUS Forms (over 60 for me) with MANY controls per Form (average 100 for me with often multi Tabs/Pages inner controls ...) ???? Which would create 12*60*100=72000 controls (6000 strings) to RESIZE ...IMPOSSIBLE BY HAND !!!!! The idea is to have a MODEL with the largest zone : German Translated Version for example and use THAT MODEL for ALL OTHER Forms , ... but HOW ??? : Hypothesis : Create an EXE version in german becoming the ORIGINAL of a NEW project and automaticaly KEEP IDENTICAL FORMS in every languages without doing any thing ??? Problems INDUCED : 1 - Then the TRUE original source is not IDENTICAL (sizes and strings).... This require to RE-GENERATE the ORIGINAL FORMS files from german version (*. DFM for me with BCBUILDER ++ V5) BUT SIZULIZER cant generate the DFM source files (???) for replacement of the true originals ....and ALSO to Translate BACK all 6000 strings from GERMAN NEW ORIGINAL to the true original language(English).....and other 11 Languages TOO..... 2- The AutoTranslations (of 12 languages) with the "Translation Memory" option create more work ....because the auto translations are FAR FROM PERFECT (for some unclear reasons the TM cant find back the equivalent translations (well recorded) from previous original project .... only 50 % in average is found back , so with 36000/72000 with almost one hour per language for 6000 strings....12 Hours for only incomplete generations .... ) and so most have to be REDONE BY HAND !!!!! So we finish with as much hand work after than before ....if not MUCH MORE ...!!! Does any body know a practical solution ???? Jean Christian DREYFUS PARIS jeanchristiand_(at)_free.fr
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hi Jean, You would like edit all possible forms in the Sisulizer for all language versions, but it seems to me that better solution is preparing your forms for localization directly in your developer tool e.g. Delphi, Visual Studio etc. during project creation. This solution allows you avoid additional work, because your idea need two steps for creating forms layout - in first you need create project with all forms in your developer tools e.g. Delphi or Visual Studio, - in next step you would like edit all these forms in the Sisulizer What for? You could do it only in first step. Software usually is created with English language as original, and unfortunately, developers usually don’t bother other languages, I live in Poland and I know this problem, because polish words and sentence are much longer then English. For this reason we have short guide for developers how perform application for localization, you can find it here: http://www.sisulizer.com/support/developers-corner/preparing-delphi.shtml Nevertheless your idea seems to me interesting and I will ask about it our R&D. Because post is concerned to features improvements not bugs I have moved this topic to our “wishes” section. Of course, current version of the Sisulizer allows on edit sizes and location of controls in form, but Sisulizer is localization tool, not developer tools and for this reason possibility of changing sizes and position of control is rather additional feature only. You can to find below some hints how streamline already existing controls edit feature: http://forum.sisulizer.com/forum3/1026.html Hypothesis : Create an EXE version in german becoming the ORIGINAL of a NEWYes, you could create special project for your original language with original language as translation, next you can edit your forms and build output file e.g. exe. Then you could create targeted project for this output file. In this project all values changed in first project will be treat as original for all languages in second project. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
DREYFUS Member
|
Thank you for your suggestions , it is certainly the best attitude for newer project , but in my case , and probably the same for many of my collegues developers , the sources are done long before the necessity to translate ....SO I have 60 complex already written Forms/Dialog boxes in BC++ Builder V5 ...and the problem REMAIN INSOLVED ...and I need the MODIFICATIONS done by SIZULIZER for the German version to be able to MODIFY the English ORIGINAL sizes AND strings....SO WHICH SOLUTION ???? JCD
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
It seems to me that your idea about creating project (second project) based on Sisulizer output file (file build by first Sisulizer project with edited forms and controls layout) is wise solution. Of course you need change some default settings in first project if you would like to get file identical with original file e.g. if your Delphi file is EXE and you would like also to get EXE file, you must change following setting: menu “Project” > “Edit source” > “File” tab, from “Resource DLLs” to “Localized files” (Look on screenshot of Delphi source properties). If you want, you can even to keep original language of resource in output file, for example if original language of source is English, you could to add in project wizard English as translation language. Next you should edit all desired controls positions and sizes in project, and if you want you can use hints (links to article and forum topic) from my previous post for do it. BTW: In next post I will describe TM issue. janusz Attachment: screen1.png (Downloaded 29 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
If you use following operations: 1. Translate all strings in project 2. Save project to Translation Memory 3. Clear all translation from project or create new for this same sources with this same settings 4. Use Translation Memory to translate clear or new project You should to get 100% translated strings. If you don’t get 100% translated strings, it could be result of following reasons: - Your strings are longer that 512 characters. Translation memory has limitation of max string length equal 512 characters. If during saving translations to TM Sisulizer find longer string, in Output panel will be displayed message about it. This issue could to occur during saving HTML or HTML Help contents to TN, but virtually doesn’t concern applications localization. - Sisulizer saves to Translation Memory only strings with statuses equal and higher from status set in Translation Memory settings (look on attached screenshot). For example, if you have 10 000 strings in project with status “Translated”, 100 strings with status “Complete”, and in “Add string if the status greater or equal to” TM setting is set to “Complete”, Sisulizer save only 100 strings to TM! BTW: In next post I will describe translations import feature. Janusz Attachment: screen.png (Downloaded 28 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator
|
If you would like use translations from one project in second project (especially for projects with identical contents e.g. for this same source file) you can use import from project feature instead Translation Memory. This is more flexible and probably faster solution, additional import from Sisulizer project feature hasn’t limitation of max string length. If you will import translations from project based on these same source files as targeted project you could to set “Import method” option as “By context”, because this option give you guarantee very accurate import – below is short sample: Sometimes these same strings in English could be translated in different ways to other language e.g. to Polish. Original Context1=Delete Context2=Delete Context3=Delete In Polish should be: Context1=Usuń Context2=Usuwanie Context3=Usuń Delphi require unique context of strings, so if you set import method as “By context” value, Contex2 will be certainly translated as “Usuwanie” not “Usuń”. Below is screenshot from settings dialog of Sisulizer project import: Best regards, Janusz Attachment: screen2.png (Downloaded 28 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
I tested TM behavior with your project. I saved all translations from German language column to TM, and then I removed all German translations from project. Next I used “Translate Using Translation Engine" and I’ve got back all 5957 (100%) German strings to project. BTW: You have two TM with these same location path. It could sometimes generate conflicts. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 01:40 pm | |
| 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) > Wish list for software localization tool > Multi-Modifications of Controls in FORMS for MULTI LANGUAGES | |
Sisulizer software localization tool - Three simple steps to localize
