|
|||
|
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) > Usage - Three simple steps to localize > Reuse of form properties (coordinates) across languages
|
|
|||
|
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) > Usage - Three simple steps to localize > Reuse of form properties (coordinates) across languages
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Reuse of form properties (coordinates) across languages - Usage - Three simple steps to localize - 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 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Pam S Member
|
I have several .NET forms that look wonderful in English, but have no room for localization. There is a refusal to make any adjustments to the English and it takes great effort each time they must be resized, which occurs for every language. What is seen in Sisulizer is not what happens at runtime so there are many iterations to the resizing efforts needed to get it right. A solution would be to create a resized form that will work for most languages and import the coordinates across all languages as a starting point. Hopefully, there would be little need for subsequent changes. I cannot figure out how to import coordinates of a form from one language to many. It seems that an import/leverage can only work within the same language.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, I’m not .NET localization expert, and maybe other members of our team will find better solutions, but I could to suggest you following idea: If you will check “Integer number” in filter panel (look on screenshot) you will see also in translation sheet all values of form components sizes. Now you can in easy way change value, and then you can simple copy & paste this value to appropriated cells in other language columns. Next you could fine tune size values for selected languages. BTW: Screenshot was done from binary .NET localization Sisulizer project. Attachment: screen.png (Downloaded 16 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
You can also export these values e.g. to TMX file, and next import this file to selected languages of your project, but of course you need check “Integer number” data type in export wizard. During import I suggest for you set up “By context” value for “Import method” option of Import Wizard. Below is screenshot from Export Wizard. BTW: Export/Import feature is available in Sisulizer Professional and Sisulizer enterprise editions. Best, Janusz Attachment: screen1.png (Downloaded 14 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Pam S Member
|
Hello Janusz. Thank you for your suggestions. The second sugestion using Export/Import will not work because you still must select the language that you will import. Coordinates from the German form will not import into the French form. The first suggestion is a winner. The copy/paste method is a workable option because there are not a lot of forms that will require this treatment. I wouldn't want to try it with many forms 
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Janusz Grzybek Super Moderator
|
I’m glad my suggestion was helpful for you. You can also streamline your work by using Sheet filters, e.g. you could to mark (blue icon with exclamation mark on sheet toolbar) all necessary size values, and next use following filter: Sheet filters (icon on sheet toolbar and filter panel toolbar or menu View > Sheet Filters > Edit) > Other > Marked > True. It allows you to see in translation sheet only your selected size values. After edit all these values in one language column you could select column (column header context menu > Select column) and copy/paste at once all necessary cells to next language columns instead separately cope/paste operation for every column cell.The second sugestion using Export/Import will not work because you still must select the language that you will import.Yes I know. You can import e.g. German language entries only to German column, but I pointed it, because this feature allows you create several different versions (or backups) of your forms layout, and next in easy way replace all items at once, if you would like change it (or revert previous version). Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 05:42 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) > Usage - Three simple steps to localize > Reuse of form properties (coordinates) across languages | |
Sisulizer software localization tool - Three simple steps to localize
