|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Localize only strings - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
pavel Member
|
Hi  ,I want to localize .Net WinForms project (from English to Russian, but it's not important). So I included resources into Sisulizer project, translate them, and generate localized resources. Then I found expectable problem with components sizes - translated texts are too long  . So I changed them (component sizes) in localized resources directly with Visual Studio. Then I wanted to import changes back to Sisulizer. But only basic resources were imported. And when I build localized resources again I lost my design changes :/.Does it mean I have to localize all (strings and also design of components) with Sisulizer? Because it would be more comfortable for me to manage design - positions of controls, images etc. in Visual Studio. Do you have any idea how to localize strings with Sisulizer and another things like design localize elsewhere ? I will be glad for any hint. Pavel (uses Sisulizer Profi 2008 build 296)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
I recommend using of Sisulizer for size, positions changes because it allows you on using different size, positions values for each translation languages. However, of course you can also change it in Visual Studio. If you have custom (translated) sizes/positions in Sisulizer project’s, these values are used also in output files, even after changes in your source files (Visual Studio project). You can check it and optionally revert values to originals in following ways: 1. After scan for changes, keep checked "Changed" in "Row Statuses" section of Filter pane and "Integer number" in "Data Types" section of Filter panel. It gives you preview of all sizes/positions items (for changed sizes/positions items in your source files). Translated values identical with originals (not changed sizes/positions) are empty or displayed in gray color, while different are displayed in black color. Next, you can manually clear selected items or select whole column content and clear via column context menu all changed items at once. Attachment: screen.png (Downloaded 33 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
2. You can right click on changed item in visual editor and use "Restore" -> "Bounds" or "All" items from context menu. You can use "Validation" menu -> "Validate Translation" to quick searching of changed components. Simply, use "Deselect All" button in validation dialog, and next select only "Moved control" and "Resized control". When you click on displayed control item in "Validation Results" pane, Sisulizer automatically select this item in visual editor. Best regards, Janusz Attachment: screen1.png (Downloaded 33 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
3. You can go to "Project" menu -> "Edit source" -> your source -> "Excluded Types", check "Integer number" item, and re-scan project. It excludes automatically all sizes and positions items from project and Sisulizer use only original values in output files, but this solution disable possibility of controls resizing in Sisulizer. Best, Janusz Attachment: screen2.png (Downloaded 33 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
pavel Member
|
Hello, Thank you for your quick answer. I have tried it and I'm afraid it's not solve my problem. Let me give you simple example: Let's have only one component on source side with already existing resources: resx: label.Location.X = 10; label.Text = "Something"; resx.RU: label.Location.X = 20; label.Text = "Russian Something"; When I scan for changes, I receive only changes from resx (changes from last scan), but russian resources are not imported at all. Fields in Russian column in Sisu are empty with status Not Translated. Then I fill some translation into label.Text = "Russian Something nr.2" and build it. Sisu generates new resx.RU: label.Text = "Russian Something nr.2" (and my label.Location.X is gone :/). It seems to be one way system for translated resources (Sisulizer -> sources). In this case I must of course use Sisu also for positioning. But as I said before it would be helpful for me to translate positions (not only positions) elsewhere. It means Sisu would have to import also existing translated resx on "Scan for changes" or overwrite only translated records in resx on "Build" (not overwrite whole file) ... or may be there is some trick how to handle this. Let me know if you have any idea, may be I missed something. With Regards. Pavel
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Pavel, Indeed is the recommended work flow to have a single language source and do all translation and positioning only in Sisulizer. And only Sisulizer creates localized resources. You can either: a) set all positions in your source in the original language and let Sisulizer ignore all positioning. That means that all localized versions use the same positioning from the source b) set and store the positioning in Sisulizer for all languages in Sisulizer. c) Try to organize all forms in a way that no language specific positioning is needed at all. That is the most work but makes a lot of things easier. In Sisulizer localization itself we try to go that way. If there is more room needed at some dialog for e.g. German we report the clipping to the developers and they globally change the dialog a bit. It sounds a bit at the beginning. But after a while developers have a good eye for the needed space and new dialogs will be the right size right away. It is not recommended to change localized files at some place outside of Sisulizer. It must be always: - change sources in original language in your development environment - do all localization stuff in Sisulizer - use the files build by Sisulizer for distribution only. Do not try to make them part of your original project. This would be a logic recursion and could be error prone. Your life is much easier if you follow these simple recommended work flow :-) Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
pavel Member
|
Hello Markus, thank you, that's exactly what i wanted to know. no problem, i will follow recommended work flow. But anyway, i think import of existing translated resources (for language you are focused in Sisu) during "Scan for changes" command would be very useful (optional) feature. Think about it  .With regards Pavel
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
pavel wrote: But anyway, i think import of existing translated resources (for language you are focused in Sisu) during "Scan for changes" command would be very useful (optional) feature. We already have a feature that performs this. It is Project | Import Translation from Localized Files menu. Choosing this menu command makes Sisulizer to import translations from localized file. Note that localized file in the .NET project localization is the satellite assembly file and not a single .resx file. Do like this:
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
I made a change in build 297: When using Project | Import Translation from Localized Files imports existing data directory from localized .resx file (if exist) instead of localized statellite assembly files. So there is not need to build your Visual Studio project after editing localized resources. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
pavel Member
|
Ok, I see. Thank you again for your quick responses
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:55 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Localize only strings | |
Sisulizer software localization tool - Three simple steps to localize
