listen at kapune.de
Wed Dec 11 05:24:15 EST 2013
Am 11.12.2013 03:48, schrieb David Carlson:
> On 12/10/2013 12:40 PM, John Ralls wrote:
>> As we get down to the wire for releasing GnuCash 2.6, we still have 45 open documentation bugs. You can see the list at http://tinyurl.com/q6y4jvt; each bug on that list is a clickable link to the details.
>> If you’ve been looking for a way to contribute to Gnucash (or even if you haven’t ;-) ) but can’t contribute code for whatever reason, working on the documentation would be an excellent way to help.
>> Following the Gnome practice we use DocBook. Gnome has a nice manual for writing documentation, including DocBook, at https://developer.gnome.org/gdp-handbook/stable/.
>> John Ralls
>> gnucash-devel mailing list
>> gnucash-devel at gnucash.org
> I just took another look at that DocBook reference and got overwhelmed
> again by references to using multiple programs that do not run in
> Windows, SVN, stylesheets, XML, etc., which reminds me of why I have
> been submitting my documentation requests (several of those 45) in plain
> text. That seems to be where they end, because I am not ready to spend
> several weeks learning how to get those programs running, etc. If
> someone knows how to convert text into appropriate XML with valid tags,
> etc., I wish they would go ahead and do it. Then I could let loose with
> a whole bunch of additional documentation bugs.
> David C
for me it is often very helpful to read some documents to find a
possible solution for one of my questions and I don't care if it is well
formatted or plain text.
If the information itself is written down someone else who is not very
well in formulations could format this texts later.
More information about the gnucash-devel