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

Invalid (depricated) link in documentation. #4176

Closed
nvaccessAuto opened this issue Jun 5, 2014 · 6 comments
Closed

Invalid (depricated) link in documentation. #4176

nvaccessAuto opened this issue Jun 5, 2014 · 6 comments

Comments

@nvaccessAuto
Copy link

Reported by DebeeArmstrong on 2014-06-05 16:51
User guide for 2014-2:
In Section 11.15 on BrlTTY:

Following are the BRLTTY command assignments for NVDA. Please see the

BRLTTY button tables documentation

for information about how BRLTTY commands are mapped to controls on braille displays.

That link goes to:
http://mielke.cc/brltty/doc/drivers/
which gives an  HTTP 404 error.

@nvaccessAuto
Copy link
Author

Comment 1 by nvdakor on 2014-06-05 17:17
Hi,
What is the correct link for the same document? The one I found is:
http://mielke.cc/brltty/doc/KeyTables/
Is this correct and the one you're looking for? If so, we'll update the user guide.

@nvaccessAuto
Copy link
Author

Comment 2 by DebeeArmstrong on 2014-06-06 04:57
I believe that indeed is the correct link. I am somewhat unsure of what Brltty documentation the NVDA user manual writer was referring to, but this also was the only relevant thing in the collection of Brltty and Brlapi documentation. Unfortunately it refers to the key names with a bias towards how they are defined to work in Linux, but I believe that's the best we can get for key names documentation at this time. For what it's worth, I tested under Linux and the document you pointed me to, which is the help screens built in to Brltty for each display under Linux, does behave as documented. In other words, for Linux, this document is totally accurate.

@nvaccessAuto
Copy link
Author

Comment 3 by nvdakor on 2015-01-06 03:25
Hi,
Coming back to this ticket...
If the link I found a few months ago is indeed authoritative, then we do need to update the user guide (unless @jteh did it a few months ago). Thanks.

@nvaccessAuto
Copy link
Author

Comment 5 by James Teh <jamie@... on 2015-02-02 06:04
In [2e445c5]:

User Guide: Minor fixes.

Fixes #4506, #4513, #3775, #4176, #4123.

Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2015-02-02 06:05
Changes:
Milestone changed from None to 2015.1

@nvaccessAuto
Copy link
Author

Comment 7 by jteh on 2015-02-02 06:30
No idea why I added that keyword...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant