Skip to content

Fixes some links in the dev guide#14633

Merged
seanbudd merged 3 commits into
nvaccess:masterfrom
XLTechie:fix14632
Feb 14, 2023
Merged

Fixes some links in the dev guide#14633
seanbudd merged 3 commits into
nvaccess:masterfrom
XLTechie:fix14632

Conversation

@XLTechie

@XLTechie XLTechie commented Feb 13, 2023

Copy link
Copy Markdown
Collaborator

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:

  • 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:

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:

  • Pull Request description:
    • description is up to date
    • change log entries
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • API is compatible with existing add-ons.
  • Documentation:
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English
  • Security precautions taken.

@XLTechie XLTechie marked this pull request as ready for review February 13, 2023 08:31
@XLTechie XLTechie requested a review from a team as a code owner February 13, 2023 08:31
@Brian1Gaff

Brian1Gaff commented Feb 13, 2023 via email

Copy link
Copy Markdown

@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit 14e9d76b94

@XLTechie

Copy link
Copy Markdown
Collaborator Author

@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.
Same for the translation wiki entries I fixed, or the link to the changes file I linked. You don't come to this document to find the changes file link--you already have that file.
I did, in fact, notice that last before now, it just wasn't important enough to care about, since it would be highly improbable that anyone reading this guide, needed this guide in order to find the changes file.

@XLTechie XLTechie closed this Feb 13, 2023
@XLTechie XLTechie reopened this Feb 13, 2023
@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit 865280a82e

@seanbudd seanbudd merged commit e86614f into nvaccess:master Feb 14, 2023
@nvaccessAuto nvaccessAuto added this to the 2023.2 milestone Feb 14, 2023
seanbudd added a commit that referenced this pull request Sep 4, 2023
Follow up to #14633

Summary of the issue:
The internal link to the nvdaHelper readme was removed from the developerGuide in favour of a static link to the GitHub repository in #14633

The relevant code in the sconscript for the developerGuide can be safely removed.
@XLTechie XLTechie deleted the fix14632 branch April 7, 2024 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants