NVDA translation system was: RE: [nvda-addons] NVDA Core dev docs: you can now build it locally via Sphinx
zvonimir stanečić, 9a5dsz
toggle quoted messageShow quoted text
Hi to all!
Let’s give my arguments on the matter
I am against using gettext for translating NVDA documentation, that is user guide and changes.
First of all, In the past I was able to choose which parts of the documentation I wanted to translate, that is: I was able to exclude changes for developers from this translation.
In my opinion, changes for developers firstly should be separated, if we want to to do such a thing.
I want to hear from Reef, Joseph, Michael and/or Quentin on this matter.
From: email@example.com <firstname.lastname@example.org> On Behalf Of dingpengyu
Sent: Tuesday, January 12, 2021 6:48 AM
Subject: Re: [nvda-addons] NVDA Core dev docs: you can now build it locally via Sphinx
It would be nice if we could use gettext to make NVDA documents translatable.