Update and migrate translating page from wiki #16577
Conversation
| The current process for translation is split between multiple processes: | ||
| - Crowdin for the NVDA interface | ||
| - The legacy SVN translation system for the User Guide and Changes files | ||
| - GitHub for Character Descriptions, Symbols and Gestures |
There was a problem hiding this comment.
This is a new process. This has not been communicated to translators on the list.
And actually some symbols are being translated on SVN during current beta period...
Symbols are translated regularly. The process to translate the changes from the English symbol file modifications should be clarified IMO:
- when and how are translators notified of changes in the English symbol file
- will translators need to do GitHub PRs? Note that some of them may not be familiar with GitHub PRs.
- until when will these PRs be accepted? Will they be accepted during translation freeze?
There was a problem hiding this comment.
@michaelDCurran communicated that these files should be updated via GitHub PRs in #15014
@michaelDCurran - can you confirm that we no longer support updating these files in SVN?
As mentioned further down, the guides for translating files need to be updated.
This PR is just refreshing the overall wiki page.
The wiki pages for translating these files will be updated and migrated after this PR.
There was a problem hiding this comment.
I never specifically removed support for those files from the system, I was more just uncertain how that worked / if that code still functioned. I think technically they could still be submitted that way. But as soon as we move userGuide / changes to po files, then I would not want to keep the system around only for symbols / gestures. Thus as recommended they should be now submitted in PRs.
There was a problem hiding this comment.
First of all, I confirm that symbol translation through SVN still works.
Second, if your intention was that translators rather use PRs to translate symbols during 2024.2 translation period, please be aware that this message does not seem to have been received correctly:
- no PR has been received yet during this dev cycle for symbol translation in other languages
- at least 5 languages have translated the new "padding dot" symbol through SVN (da, uk, ru, ta and fr at least)
It seems to me that translating symbols through PRs has actually been planned in #15014, but the actual switch time from SVN to GitHub PRs has not been announced, on contrary to what has been done for interface (nvda.po) switch to CrowdIn, as well as t2t to md switch.
Personally, I understand that you do not plan to use SVN anymore for NVDA translation after the user guide and the change log have switched to CrowdIn. And I agree that it makes sense.
Thought I insist again on the fact that the new process should be documented in NVDA dev doc when possible, i.e. when it is definitive. And during the transition period when no definitive documentation can be written, a good communication on the translators mailing list is needed.
IMO, the process could be the following:
- When the translation freeze period begins, NV Access sends a message to the translators mailing list with the diff in the English symbol file between release N-1 and last beta of release N.
- Localized symbol files are updated through PRs during translation freeze period. If translators are uncomfortable with GitHub / PRs, we may imagine alternative / complementary solutions such as NV Access or experimented people gathering updated files and making a common PR on behalf of translators.
- During translation freeze period, no PR is accepted on symbol file, unless you extend the freeze period.
- When the translation freeze period is over and the PRs are merged, the RC can be released.
The same process can be used for gesture changes, even if they are much less frequent. There cannot be diffs for gestures, but making an announcement when new/modified gestures are likely to receive a localized translation can be done manually, as I have already done for ultimate such changes.
Cc @gerald-hartig for awareness and opinion.
seanbudd
added
the
conceptApproved
|
In that case, for 2024.2, we should continue to use svn for symbols
/gestures as that is what translators are continuing to do.
We'll consider your further ideas on how to manage them via PRs once
they become the only things left in svn.
Message ID: ***@***.***>
|
|
Hi Michael,
How do you want to move symbols via the Pull requests?
These are the locale specific things, and they differ in information
they have, respectively..
for example, № is the symbol which is locale specific, and which is not
in the main symbols file.
IF you move symbols from svn to pull requests,, we will not have a way
to track these i.e what's changed there, thus we will be forced to
follow informations which can be completelly unrelated to our work.
|
|
I'd say that we should continue discussing elsewhere than in this closed PR now; else the discussion will be lost. I suggest to continue #15014 or to open a new GitHubdiscussion. |
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
In order to start the process of updating and migrating the translating documentation, the first page was moved from the wiki:
The following changes were made to update the contents:
Future work
On merge, this wiki page should be updated to link to this doc.
Moving and updating the rest of the translating wiki pages.