Ho ho, you should realise its never that simple with programmers in charge of the system cheesy grin.
toggle quoted messageShow quoted text
Sent via blueyonder.
Please address personal E-mail to:-
firstname.lastname@example.org, putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Shaun Everiss" <email@example.com>
Sent: Tuesday, January 12, 2021 6:57 AM
Subject: Re: NVDA translation system was: RE: [nvda-addons] NVDA Core dev docs: you can now build it locally via Sphinx
I don't see any reason on compiling the documentation in the first place.
Why can't the documentation be on the website and such.
I guess for source and alphas/ snapshots/ betas I guess I could
understand but for stable versions, or such who knows.
Either that or something that will compile the latest documentation and
previde snapshots online of the latest documentation.
For betas and stable releases, documentation should be on the website or
a one for that sort of thing.
At any rate once you have documentation which is the latest without any
changes you should just be able to get it.
On 12/01/2021 7:07 pm, zvonimir stanečić, 9a5dsz wrote:
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.
<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