Date: prev next · Thread: first prev next last

Re: [libreoffice-accessibility] Display bindings


Hi :)
L10n lists are currently having a massive argument/discussion (discussion
is more accurate tbh) right now about the disruptive effect of minor
changes.

I'm not sure but i suspect that getting such a UI change within the next
couple of days might play out ok and catch the translators before they have
put too much time into too many strings and then finding they need to
repeat the work.

If it's not likely to be just a couple of days then it'd probably be better
for them if this sort of change didn't happen for a few months - or
longer.  There might be a chance of them automating something like this but
it'd take ages to set something up and they haven't agreed on getting the
automation bit sorted.
Regards from
Tom :)



On 12 December 2014 at 17:00, V Stuart Foote <VStuart.Foote@utsa.edu> wrote:

@Tom, *,

No, you're asking the right question.  But you do need to look under the
bonnet from time to time.

Within the LibreOffice code there are two broad classes of keyboard
accelerators.   One is associated with the .uno action associated with each
object in the user interface.  The other are specific key functions defined
globally.

Most of the current implementation can be reviewed here:
Other than the GenericCommands.xcu, different modules assign "access keys"
as needed

http://opengrok.libreoffice.org/xref/core/officecfg/registry/data/org/openoffice/Office/UI/

These are the "global"  "keyboard accelerator/short-cut keys" and each
LibreOffice module responds in some fashion to them.  The KEY_MOD1 and
KEY_MOD2 differ depending on OS.
http://opengrok.libreoffice.org/xref/core/vcl/source/window/keycod.cxx

The native accessibility bridges handle only the first, the "access keys".
But does so pretty effectively at this point.

Enhancement would be to do as Mozilla and Adobe (and I assume Google) have
done,  and simply label each menu item (or button) with its "keyboard
accelerator/short-cut key" as appropriate for the function.   The rub would
come with needing to accommodate keys for each OS and possibly  UI issues
with the  l10n/i18n support.



--
View this message in context:
http://nabble.documentfoundation.org/libreoffice-accessibility-Display-bindings-tp4131697p4132420.html
Sent from the Accessibility mailing list archive at Nabble.com.

--
To unsubscribe e-mail to: accessibility+unsubscribe@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/accessibility/
All messages sent to this list will be publicly archived and cannot be
deleted



-- 
To unsubscribe e-mail to: accessibility+unsubscribe@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/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.