-
-
Notifications
You must be signed in to change notification settings - Fork 655
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
Update and migrate translating dic/ini files from wiki #16627
Conversation
Might it be better to create a "Translating guide", to go along with the Developer Guide and User Guide?
It seems like there would be enough material.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is my review.
Though, I agree with @XLTechie: sooner or later, a separate translation guide would be more than helpful.
If this is part of the developer guide, then in my view it becomes even more relevant to deploy the developer guide via SVN or Crowdin for tranlsation to every language, so #13333 should definitely not cause the developer guide to be removed. |
Co-authored-by: Cyrille Bougot <[email protected]>
Co-authored-by: Cyrille Bougot <[email protected]>
Summary of the issue:
NV Access is intending to move most of the wiki into the repository, so changes are tracked better and easier to propose.
The documentation for translating NVDA is very dated, particularly since the update of the translation system.
Description of user facing changes
The following pages were already mirrored in the developerGuide.
The developerGuide sections were reviewed and updated.
This wiki page was moved and updated in the developerGuide
The following changes were made to update the contents:
Future work
These wiki pages will be removed/deprecated when the updated developerGuide is released in 2024.3
Moving and updating the rest of the translating wiki pages.