Please use po file to make documentation translation.

[vgjh2005]

Hi all:
I think all translators know when they were making document translation, They must looked for all subversion to find what paragraph had been changed. It is waste all translator's time. Please use po file to replace txt2tag and to allow more and more translator to join our team. NVDA addon community is the best demo site to let us know that it is a good solution. Please all translators come out to discuss this. Thanks!

[gregjozk]

inside revision folder is also file, where differences between previous and current version of original documentation has been listed. it is enough for me. moreover, when working with longer text, I prefer to work with Notepad++ instead of poedit.
another suggestion, could be this discussion moved to translation mailing list?

best regards,
Jožef

[bdorer]

I disregard. If you use userGuide-structureDifferences and you sync userguide with original the you see very quickly where changes are in userGuide-newRevisions\revisionNumber\differences.txt so I wote for closing.

[cary-rowen]

If you use po files, it may be easier for novices to learn, because not everyone is technically proficient, but their translation skills may be great.
Regarding the detailed changes in the long text, it is undeniable that git diff has its advantages, but I hope that more people will participate in the translation, and I hope it will be more friendly to novices.

[vgjh2005]

Hi:
@bdorer
@gregjozk
Had you made NVDA addon comunity site translation? We just need to press down arror to look for what it is then translate it to our language. Now, we need to open the diff file , open the t2t file, then jump to the specific position then select some thing to define ether delete or change them.
The second, because of upgrade process, some content need to be changed one more time. So, diff file isn't a convinient way for all translator members.
If it is a po file, we just need to change it at once in the end of the translation deadline.
We needn't to open more file, we needn't to open different files for the whole translate process, we needn't to jump to the different place all the time. Our time is most valued.
So please reconsider this resolution. Thanks!

[dpy013]

I support using .po to replace txt2tags.
On the other hand, .po can reduce the size of the translation repository.

[ehollig]

What is the status of this? It sounds as this issue should be discussed and resolved on the translators mailing list

[Adriani90]

I think a solution for this needs to come from the community, every string has to be defined with _() and this means NV Access has to define the string length and so on every time a new release of NVDA is planed. For GUI translations .po files are nice, but for user guides and so on this might mean a pain for developers.

[ruifontes]

And why not create a script to transform t2t files in po files?
It is not the way community uses to translate the add-ons readme.md files?
I, not a programer, have wrote a small add-on to transform readme.md in nvda.po files to strongly speed up translation using the automatic translation and suggestions of POEdit...

[Adriani90]

@ruifontes the userguide, changes file and keycommands file are formated in git flavour markdown while the addon documentation is not. This means every NVDA core doc would have to be restructured from scratch, including the automated tasks that are implemented such as synchronisation between userguide and keycommands document etc.
For more details see the discussion in #8734, #9840 and #9968.

[Adriani90]

I would rather say before re-structuring all the documents, find an alternative translation system which displays the t2t files into a web based module or something like that. In that case even .po files could be transfered in a web based module and you wouldn't need any external software on your PC to translate NVDA. The problem is, most of these kind of translation systems are paid solutions, none of them is completely free.

[dpy013]

I would rather say before re-structuring all the documents, find an alternative translation system which displays the t2t files into a web based module or something like that. In that case even .po files could be transfered in a web based module and you wouldn't need any external software on your PC to translate NVDA. The problem is, most of these kind of translation systems are paid solutions, none of them is completely free.

hi You can see
weblate

[zstanecic]

Hi, If you, as an open source developer provide the story behind NVDA, thy are happy to give the open source license for such a big project. Weblate is somewhat not intuitive, when it comes to accessibility Problems when translating are some licales, which refuse to translate the developer changes ti their language, these are for example croatian and polish. We don’t want to translate these, as we come out of philosophy, that developers use English, and before restructurizing, we should stop giving to the user’s changelog the changes for developers. From: xingkong ***@***.***> Sent: Wednesday, March 1, 2023 11:53 AM To: nvaccess/nvda ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [nvaccess/nvda] Please use po file to make documentation translation. (#12576) I would rather say before re-structuring all the documents, find an alternative translation system which displays the t2t files into a web based module or something like that. In that case even .po files could be transfered in a web based module and you wouldn't need any external software on your PC to translate NVDA. The problem is, most of these kind of translation systems are paid solutions, none of them is completely free. hi You can see weblate <https://github.com/WeblateOrg/weblate> — Reply to this email directly, view it on GitHub <#12576 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVCDE56QXHEE6CR6NYWQDLWZ4TB5ANCNFSM47FUHHAQ> . You are receiving this because you are subscribed to this thread. <https://github.com/notifications/beacon/ACVCDE526HKV5ODSLZ4IFC3WZ4TB5A5CNFSM47FUHHA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOKZVTPXQ.gif> Message ID: ***@***.*** ***@***.***> >