Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In some applications, particular NVDA shortcuts should be localized #810

Closed
nvaccessAuto opened this issue Aug 5, 2010 · 5 comments
Closed
Assignees
Labels
component/i18n existing localisations or internationalisation enhancement
Milestone

Comments

@nvaccessAuto
Copy link

Reported by msuch on 2010-08-05 06:25
This is not for default key commands but for key commands applying, for example to browsers.
When using Firefox or IE, we have shortcuts to go to headers etc.
In english, this is generally the first letter of what you want to get to (h for header).
In this case, in french, we would prefer to ha "t" (for titre). H has no particular meaning for us.
So these particular shortcuts should be localized I think.
Blocked by #194

@nvaccessAuto
Copy link
Author

Comment 2 by orcauser on 2010-08-07 13:57
Hi,
I think localizing these might be a bad idea.
It is true that modifying the bindings would make sence to that language for initial users, but it would introduce the following issues:

  1. Translators would be responsible for making sure the mapping for their language is logical and is consistent (not an easy task if people have limited time and resources), and if they end up doing it badly, this would reflect negatively on NVDA.
  2. Maintaining/cross-referencing to make sure that the commands are correct throughout all types of documentation, more time, more unnecessary work for translators, i.e. in one version h is for header, and in another version t, and in a third l was found to be the best.
  3. If a person is using a particular locale, and they want some help to get to something, a more knowledgeable user of NVDA using a diffrent locale cant tell them press this and press that to achieve their task.

I believe the only keys that should be localized are the mnemonic keys for nvda menues and dialogues, and getting that right is a task on its own.

@nvaccessAuto
Copy link
Author

Comment 3 by RamboUdin on 2010-08-21 08:41
hi,Why do you need to do that?
it will be confusing users?

@nvaccessAuto
Copy link
Author

Comment 4 by msuch on 2010-08-21 09:12
I don't see why it should be confusing users. Most of them would prefer t use shortcuts which are mnemonic in their language rather than in English provided that most of them don't even speak English.

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2010-11-26 01:31
Done as part of http://bzr.nvaccess.org/nvda/gestureMapping/

@nvaccessAuto
Copy link
Author

Comment 7 by jteh on 2010-11-26 05:05
Merged in 8ecfad4.Merged in 8ecfad4.
Changes:
State: closed

@nvaccessAuto nvaccessAuto added enhancement component/i18n existing localisations or internationalisation labels Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2011.1 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/i18n existing localisations or internationalisation enhancement
Projects
None yet
Development

No branches or pull requests

2 participants