|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Validation of hotkeys - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Isabella Member
|
This might actually be considered a bug; When validating a form with regard to hotkeys, the system does not take into consideration that several commands are restricted to certain menues. This means that a &e in H&elp will work even if there also is a menu choice &Module > &Edit (or something). Even so, Sisulizer reports this as errors. And then there is my wish; as one often works with one form at a time, it would be very nice to be able to validate that form only - not allways the whole project. Isabella
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Siikanen Administrator
|
That hotkeys validation was allready on my todo list. I will fix it soon. Form only validation is a good idea. I will implement that too. regards, Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Isabella Member
|
Excellent! Isabella
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Isabella Member
|
When I first wrote, I was working only with menues. Obviously, the same thing goes for forms with tabs. A hotkey somewhere on one tab does not clash with a hotkey on another tab in the same form - even if Sisulizer reports this as an error. :-) Isabella
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Siikanen Administrator
|
I fixed that too. These fixes will be included to the next build. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Siikanen Administrator
|
Now the build 183 is out. Fixes: - form only validation (there is a new button on form toolbar). - hot keys validation has been fixed for menus and tabs Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Isabella Member
|
We now have the 184 build, but Sisulizer still reports errors for hotkeys that really don't clash because they are screentexts on separate tabs. But the form validation button is good! Isabella
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Siikanen Administrator
|
Could you send your project file (.slp) to me by email, please. ilkka.siikanen (at) sisulizer.fi regards, Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Isabella Member
|
Hi, How are you doing with the duplikate hotkey validation? We now have version 1.6.23, and it still reports "duplicate" menu hotkeys that are no problem, but ignores the fact that the button &OK clashes with another &o in the form. Otherwise, this validation is very useful - especially the "available hotkeys function" :-) Regards, Isabella
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Salmenius Administrator 
|
I tested with couple of projects and the validation worked fine on them. Could you send your .SLP file to us please. And tell in which form the invalid validations occurs. I can take a look of it. support (at) sisulizer.fi best regards Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Salmenius Administrator
|
Thank you for the .SLP file. You were right. Sisulizer detected wrong duplicate hotkey violations. I will fix it. I will also fix it to find inherited hotkeys. regards Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Hotkeys validation features doesn’t work with text localizations, for example with GetText (PO/POT) and INI files. Disabling some validation features for these methods of localization is logical, for example “Duplicate form hotkey“, but it seems to me that adding to PO or INI localizations “Inconsistent hotkey” validation is good idea, because both PO and INI localizations usually use ampersand characters as hotkey symbol, and if original string e.g. “&Delete” contain ampersand, that is translated string should also contains “&” character. What do you think about adding “Inconsistent hotkey” validation to validation set for text based localizations? BTW On list in validation dialog window (select of validation types) for all supported platform are always visible all possible validation items, but not all items are available for each platform, e.g. “Duplicate hotkeys” or “Overlapping controls” are unavailable for PO or INI localization. Unfortunately, it is could sometimes to mislead some not experienced translators, e.g. translator can to use “Inconsistent hotkey” feature for PO file, and after validation tests he don’t see any results in validation results pane, even if original and translation contains different counts of hotkeys characters. What do you think about disabling in UI (invisible or greyed items in UI) unsupported for selected platform validation items? Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Isabella Member
|
Hello! I am sorry that I am not that familiar with these file types and the technicalities involved. However, I would principally support a decision to disable options that are not feasible for the platform/files/settings at hand. That way the end result would not be as confusing. Are you saying that the "duplicate hotkeys" check is not possible in my project - which is from Visual Studio and .Net? If so, that is really a shame, because checking each form manually for e.g. two or more conflicting "&S" is very time consuming, and an automatic check here would be really welcome! :-) Nevertheless, a check for "inconsistent hotkey" is also valuable. :-) Isabella
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:13 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Validation of hotkeys | |
Sisulizer software localization tool - Three simple steps to localize
