У уто, 28. 05 2013. у 13:42 +0100, Michael Bauer пише: > On the whole, I think the whole access key thing needs a more coherent, > automated approach. Or at least a codekey attached to each UI string in > the test builds you you can *easily* identify the string that needs fixing.
This is not something I do, but it may be an option if you like to have perfect hotkeys. Open a dialog and make a screenshot. Next run the keyid build, open the same dialog, make another screenshot. Now annotate hotkeys in the first screenshot taking care there is no conflict. Finally, search for strings by keyid and add hotkeys as annotated. You should be able to fix all strings in a dialog in under 30 minutes. Best, Goran -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
