Skip to content

/nvda

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 the keyboard settings dialog, the content of the "keyboard layout" list is not translatable #558

Closed
nvaccessAuto opened this issue Feb 13, 2010 · 4 comments

Comments

Assignees

@jcsteh jcsteh

Labels
Localisation enhancement
Projects
None yet
Milestone
  2011.1
2 participants
@nvaccessAuto @jcsteh
@nvaccessAuto
Copy link

commented Feb 13, 2010

Reported by msuch on 2010-02-13 09:43
In the keyboard settings dialog, words "desktop" and "laptop" in the keyboard layout list should be translatable
Blocked by #601
@nvaccessAuto

This comment has been minimized.

Sign in to view
Copy link
Author

commented Feb 15, 2010

Comment 1 by jteh on 2010-02-15 00:34
Changes:
Milestone changed from 2010.1 to 2010.2
@nvaccessAuto

This comment has been minimized.

Sign in to view
Copy link
Author

commented Jul 15, 2010

Comment 2 by jteh on 2010-07-15 00:43
Done as part of input framework.
Changes:
Milestone changed from 2010.2 to 2010.3
@nvaccessAuto

This comment has been minimized.

Sign in to view
Copy link
Author

commented Oct 14, 2010

Comment 3 by jteh on 2010-10-14 08:16
Actually, this isn't quite done. The GUI still doesn't use the layout list provided by !KeyboardInputGesture.
@nvaccessAuto

This comment has been minimized.

Sign in to view
Copy link
Author

commented Oct 26, 2010

Comment 4 by jteh on 2010-10-26 11:46
Fixed in a6827cb.
Changes:
State: closed

@nvaccessAuto nvaccessAuto added enhancement Localisation labels Nov 10, 2015

@nvaccessAuto nvaccessAuto assigned jcsteh Nov 10, 2015

@nvaccessAuto nvaccessAuto added this to the 2011.1 milestone Nov 10, 2015

@nvaccessAuto nvaccessAuto closed this Nov 10, 2015

@nvaccessAuto nvaccessAuto referenced this issue Nov 10, 2015

Closed

New input handling framework #601

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.