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

Description of scripts in keyboard help are not translatable #2

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

Comments

@nvaccessAuto
Copy link

Reported by mdcurran on 2007-04-02 09:39
Because descriptions of scripts in NVDA are doc strings, it makes it very hard to allow them to be translatable for various languages. Rather than the doc string being set inside the function, it should be manually set after the function is defined, so that the string can be enclosed in _()

@nvaccessAuto
Copy link
Author

Comment 1 by mdcurran on 2007-04-02 09:42
A few scripts have already been changed in appModules/_default.py, though there are still many to go there, plus in NVDA objects and virtual Buffers.

@nvaccessAuto
Copy link
Author

Comment 3 by pvagner on 2007-11-23 09:28
BTW majority of the _doc strings is translateable now.
The related thing which bothers me currently is ability to have list of commands within the given appmodule built dynamically.
I have started working on this but the problem I am facing is I haven't got an idea how to report keyboard shortcuts and make them translateable as well.
E.G. currently it gives me clear review current word. I think we would rather like to have numpad5 listed.

@nvaccessAuto
Copy link
Author

Comment 4 by jteh (in reply to comment 3) on 2007-11-23 14:04
Replying to pvagner:

BTW majority of the _doc strings is translateable now.

Can you think of any areas where the docstrings haven't been translated? If not, this ticket can probably be closed.

The related thing which bothers me currently is ability to have list of commands within the given appmodule built dynamically.

I've been thinking about this for a while, but haven't come up with a nice way to order the scripts. Alphabetical order is not particularly useful in some cases. Also, they should probably be categorised. In any case, I think this is probably an issue for another ticket.
Changes:
Milestone changed from None to 0.6

@nvaccessAuto
Copy link
Author

Comment 5 by pvagner (in reply to comment 4) on 2007-11-24 20:59
Replying to jteh:

Can you think of any areas where the docstrings haven't been translated? If not, this ticket can probably be closed.

Yes I can find no more....

I've been thinking about this for a while, but haven't come up with a nice way to order the scripts. Alphabetical order is not particularly useful in some cases. Also, they should probably be categorised. In any case, I think this is probably an issue for another ticket.

I am thinking about adding name and category fields the same way _description is used currently and then sort by category. The categories I can think of at the moment are:

*caret navigation
*object navigation
*status reporting
*settings and toggle scripts

But sorry, we will perhaps create a seperate thread as you pointed out.

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2008-01-14 23:25
Changes:
State: closed

@nvaccessAuto nvaccessAuto added bug component/i18n existing localisations or internationalisation labels Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2009.1 milestone Nov 10, 2015
larry801 pushed a commit to larry801/nvda that referenced this issue Aug 19, 2018
LeonarddeR pushed a commit that referenced this issue Dec 27, 2018
Get rid of _resumeDetection method on the braille handler
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug component/i18n existing localisations or internationalisation
Projects
None yet
Development

No branches or pull requests

2 participants