|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Clipped text validation error - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Psvahn Member 
|
I get a lot of validation errors for controls whose text are wrapped in once they are displayed in our application. Typically, long texts are wrapped for a label control if it does not use auto size and has a height that can accomodate several lines.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Could you upload to us your source file (e.g. DLL/EXE) and Sisulizer project file? We'll check this issue. BTW: You can read more about our upload system in this http://www.the-localization-tool.com/?p=808 article on our blog. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Thank you for files. I reproduced this issue and forwarded to our developers. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
You asked in email to us:Another question here: if I change the control position and size in Sisulizer, then how can I get changes to the original in VS to be propagated to one or more localizations? Changes in original source code: Sisulizer is localization tool, not standard developer tool, and for this reason it doesn't change source code. However, you can use these two solutions: - Copy changed position/size values from localized resx file e.g. from xxx.sv-SE.resx file to original resx file. - Or check "Integer number" checkbox in Sisulizer's filter panel, copy changed position/size values and use it in Visual Studio. If you change position/size values in source code, Sisulizer automatically use these changed values (after scan) for all languages, if these languages in Sisulizer don't use custom position/size values. Changes in Sisulizer project: You needn't change position/size values in source code, because you can quickly and easy re-use values from one language for other languages. Check "Integer number" checkbox in Sisulizer's filter panel, copy changed position/size values and past it to appropriated cells in other language columns (look on screenshot). In this case, all output files use identical position/size values without changes in source files. Janusz [code] Attachment: screen.png (Downloaded 12 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Psvahn Member
|
Thanks for the quick replies! My question was: if I change a control's position or size in Visual Studio, how do I make this change affect my localizations? For instance, if I typically find that a check box control was to narrow to fit all translations, then I would make it a little bit higher to allow the text to be wrapped. I thought that "Scan for changes" would do this, but it only updates the text, at least if the position or size has been changed in Sisulizer. /Peter
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Sisulizer always use existing translations (both for strings and position/size values) for changed items. For not translated items, Sisulizer use changed original values. All changed original items are marked by red dots in Flag column after scan. You can read about it in this http://www.the-localization-tool.com/?p=1565 article on our blog. After scan you need only check and optionally change translations for rows marked by red dots. Two advices: - You can use filters for displaying only changed items. It allows you quicly check and optionally edit translations for changed originals. - You can enable displaying of "Previous original" column in sheet via "View" menu -> "Sheet columns". It allows you compare previous on new values directly in Sisulizer's sheet. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Nieminen Administrator
|
Psvahn wrote: I get a lot of validation errors for controls whose text are wrapped in once they are displayed in our application. Typically, long texts are wrapped for a label control if it does not use auto size and has a height that can accomodate several lines. I fixed this in the next build (309). The problem was that Sisulizer did not correctly set word wrap to true when scanning radio button or check box that has AutoSize turned false. Thank you for pointing this out. New build will come out next week. Jaakko
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Psvahn Member
|
I think you have the same problem with labels. Please check that out too. Regards, Peter Svahn
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Nieminen Administrator
|
Hi Peter, I check labels too and they were already working properly. In what kind of settings it works incorrectly? Jaakko
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Psvahn Member
|
OK, I just wanted you make sure... /Peter
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Psvahn Member
|
OK, I just wanted you to make sure... /Peter
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:24 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 > Clipped text validation error | |
Sisulizer software localization tool - Three simple steps to localize
