Fixes some links in the dev guide#14633
Conversation
… was written in Markdown instead of T2T.
… wiki page were not previously styled as clickable links.
|
Comment:
The fact that nobody has mentioned this until now would perhaps indicate
this is not the way those interested access the guide.
Brian
…--
***@***.***
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
***@***.***, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Luke Davis" ***@***.***>
To: "nvaccess/nvda" ***@***.***>
Cc: "Subscribed" ***@***.***>
Sent: Monday, February 13, 2023 8:29 AM
Subject: [nvaccess/nvda] Fixes some links in the dev guide (PR #14633)
### Link to issue number:
Fixes #14632
### Summary of the issue:
The link to the NVDA Helper README in the Development Guide did not work.
### Description of user facing changes
Fixed that link per suggested alternative given by @michaelDCurran in
[#14632
(comment)](#14632 (comment)).
While doing that, I noticed and fixed:
* A couple links to the Translating NVDA wiki page, which had no link
markup at all.
* One case of a link which was written in markdown style instead of T2T
style.
### Description of development approach
* Searched file for the helper readme reference, and replaced the broken
file reference with the link given by @michaelDCurran .
* Searched for other occurrences of "http", and verified that
they were all in validly formatted link markup, and fixed them where found
not to be.
### Testing strategy:
None; will wait for build and check links in result. Will update if any
broken.
### Known issues with pull request:
This PR does not address @michaelDCurran's suggestion in [this
comment](#14632 (comment)).
### Change log entries:
None needed.
### Code Review Checklist:
- [X] Pull Request description:
- description is up to date
- change log entries
- [X] Testing:
- Unit tests
- System (end to end) tests
- Manual testing
- [X] API is compatible with existing add-ons.
- [X] Documentation:
- User Documentation
- Developer / Technical Documentation
- Context sensitive help for GUI changes
- [X] UX of all users considered:
- Speech
- Braille
- Low Vision
- Different web browsers
- Localization in other languages / culture than English
- [X] Security precautions taken.
You can view, comment on, or merge this pull request online at:
#14633
-- Commit Summary --
* Fixed broken NVDA Helper Readme link in devDocs/developerGuide.t2t.
* Fixed a link to the changes file in devDocs/developerGuide.t2t, which
was written in Markdown instead of T2T.
* In devDocs/developerGuide.t2t, a couple links to the Translating NVDA
wiki page were not previously styled as clickable links.
-- File Changes --
M devDocs/developerGuide.t2t (9)
-- Patch Links --
https://github.com/nvaccess/nvda/pull/14633.patch
https://github.com/nvaccess/nvda/pull/14633.diff
--
Reply to this email directly or view it on GitHub:
#14633
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
See test results for failed build of commit 14e9d76b94 |
|
@Brian1Gaff it is more likely that few people access the development guide at all (the ratio of developers to users), and that, of those, there are relatively few who need to follow the link to the C-related code (as opposed to those who are there to read about developing in the Python portions of NVDA). Of that subset of a subset of the set of NVDA users, most who need to know about the linked file, likely know, or can easily figure out, where else to get it. |
See test results for failed build of commit 865280a82e |
Link to issue number:
Corrects the exact problem mentioned in #14632, but may not solve it ultimately in the desired way. See the known issues section below. This is both a stop-gap while the ultimate solution is decided, and fixes some moderate errors found while working on it.
Summary of the issue:
The link to the NVDA Helper README in the Development Guide did not work.
Description of user facing changes
Fixed that link per suggested alternative given by @michaelDCurran in #14632 (comment).
While doing that, I noticed and fixed:
Description of development approach
Testing strategy:
Checked links generated in PR build. All changed links are clickable, and go to the expected destinations.
Known issues with pull request:
This PR does not address @michaelDCurran's suggestion in this comment.
Change log entries:
None needed.
Code Review Checklist: