Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

У уто, 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.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.