Re: documentation bug 687820

Op dinsdag 7 februari 2017 18:50:16 CET schreef David T.: > Once again, Geert, you come to clarify. Indeed, I was not aware that this > was a comma-delimited list. With only one dependency, that is not clear > from the page. > > Once again, I prove that there is nothing too simple that I can’t scr

Re: documentation bug 687820

Once again, Geert, you come to clarify. Indeed, I was not aware that this was a comma-delimited list. With only one dependency, that is not clear from the page. Once again, I prove that there is nothing too simple that I can’t screw up. David > On Feb 7, 2017, at 3:40 PM, Geert Janssens wrot

Re: documentation bug 687820

Op dinsdag 7 februari 2017 10:17:38 CET schreef David T. via gnucash-devel: > Frank, > I'm pretty sure those features are not opened to mere mortals, at least, I > can't see them. That's what I meant when I said I could only edit an > existing dependency entry. David T. > When I open bugs, I see

Re: documentation bug 687820

Frank,  I'm pretty sure those features are not opened to mere mortals, at least, I can't see them. That's what I meant when I said I could only edit an existing dependency entry.  David T. On Tue, Feb 7, 2017 at 10:50, Frank H. Ellenberger wrote: Davids, Am 07.02.2017 um 03:16 schrieb d

Re: documentation bug 687820

Davids, Am 07.02.2017 um 03:16 schrieb david.carlson@gmail.com: > Sounds Like we need clarification on how to use those fields to best > advantage. David C Sent from my LG G Pad 7.0 LTE, an AT&T 4G LTE > tablet > > > > -- Original message--From: DavidDate: Mon, Feb 6, 2017 7:53 > PM

Re: documentation bug 687820

To: "Frank H. Ellenberger" > Cc: "gnucash-devel@gnucash.org" > Subject: Re: documentation bug 687820 OK. I did not know about the histroy link, but the See Also reference and the Depends on changes are not appearing where they are supposed to even if I refresh my view of the b

Re: documentation bug 687820

17 To: "Frank H. Ellenberger" Cc: "gnucash-devel@gnucash.org" Subject: Re: documentation bug 687820 OK. I did not know about the histroy link, but the See Also reference and the Depends on changes are not appearing where they are supposed to even if I refresh my view of the

Re: documentation bug 687820

Now I see in that history that David T removed those changes and I missed those changes. So I am just not up to date. I am curious though, How does one find related bugs if those fields are not used? David C On Mon, Feb 6, 2017 at 5:12 PM, David Carlson wrote: > OK. I did not know about the

Re: documentation bug 687820

OK. I did not know about the histroy link, but the See Also reference and the Depends on changes are not appearing where they are supposed to even if I refresh my view of the bug, Do I have to log out and log back in to refresh my view of the summary box at the top of the bug report? David C On

Re: documentation bug 687820

Hi David, Am 06.02.2017 um 23:15 schrieb David Carlson: > David, > > I received two emails from Gnucash saying that you added references to bug > 778254 to bug 687820, but when I opened bug 687820 I could not find those > references. > > FYI. > > David C In the upper right corner behind Modifi

Re: Documentation Docbook Question

Op zaterdag 28 januari 2017 15:26:29 CET schreef David T. via gnucash-devel: > Hello, > > In working on Bug 777318, I noticed some small issues with the > recently-added glossary (which is all my creation). > > First, I noticed that it lacks the appropriate section name (“gnc-gloss”). > > Next,

Re: Documentation Update Instructions

Chris,  I explained my reasoning behind that on the other thread.  On Thu, Jan 26, 2017 at 11:00, Chris Good wrote: Hi David,   Re http://wiki.gnucash.org/wiki/Documentation_Update_Instructions#Step_1_Create_a_Bugzilla_Bug_for_the_Documentation_Change   I think you should leave in

Re: Documentation translators: Changed para in ch_oview

On Thursday 11 August 2016 21:19:31 David T. wrote: > Geert, > > I truly appreciate your reasonable and reasoned reply. It makes clear > even to the densest of us (me). I was not aware of Frank’s > longstanding and ongoing contributions to GnuCash, and for that I > also apologize. > > I have sinc

Re: Documentation translators: Changed para in ch_oview

Geert, I truly appreciate your reasonable and reasoned reply. It makes clear even to the densest of us (me). I was not aware of Frank’s longstanding and ongoing contributions to GnuCash, and for that I also apologize. I have since seen Frank’s explanation as well, and I appreciate his work to

Re: Documentation translators: Changed para in ch_oview

HI, Am 10.08.2016 um 18:29 schrieb Geert Janssens: > And I can't tell why Frank chose to push this commit rather than following > your suggestion in > bug 743672. He can explain that himself if he cares to. By the way, I believe > you were on the > right track and agree even more with John we

Re: Documentation translators: Changed para in ch_oview

On Tuesday 09 August 2016 21:22:36 David T. wrote: > > I think also of concern to me here is that there are now two > recommended methods for suggesting and making changes, and as I noted > here, with two avenues for change, there is the increasing likelihood > that bugs will languish in one or th

Re: Documentation translators: Changed para in ch_oview

Am 09.08.2016 um 13:59 schrieb Pedro Albuquerque: > Às 12:10 de 09/08/2016, Frank H. Ellenberger escreveu: : >> Run >> LANG=pt_BR gnucash >> >> F1 opens "Manual de ajuda do GnuCash" >> Ctrl+H opens "GnuCash Tutorial and Concepts Guide" >> instead of "Tutorial e guia de conceitos do GnuCash", >> whi

Re: Documentation translators: Changed para in ch_oview

> On Aug 9, 2016, at 7:23 PM, Geert Janssens wrote: > > On Tuesday 09 August 2016 16:59:10 David T. wrote: > > Geert, > > > > > > Ok, I had to re-read this a couple of times to get your point. > > > > > > For some time now we are accepting changes in two ways: either as an > > > attachment in

Re: Documentation translators: Changed para in ch_oview

On Tuesday 09 August 2016 16:59:10 David T. wrote: > Geert, > > > > Ok, I had to re-read this a couple of times to get your point. > > > > For some time now we are accepting changes in two ways: either as an > > attachment in bugzilla or as a pull request in github. The > > submitter can choose f

Re: Documentation translators: Changed para in ch_oview

> On Aug 9, 2016, at 4:59 AM, David T. via gnucash-devel > wrote: > > As for the modification that Frank is offering, I will note that there is a > bug that I filed in bugzilla (743672) proposing that this section be moved in > its entirety to an appendix. Perhaps now would be the time to con

Re: Documentation translators: Changed para in ch_oview

Geert, > On Aug 9, 2016, at 2:19 PM, Geert Janssens wrote: > > On Tuesday 09 August 2016 13:37:02 David T. wrote: > > Geert and Frank, > > > > I understand that these aspects of software development are clear and > > easy for you; suffice to say they are not for me. I do not wish to > > start a

Re: Documentation translators: Changed para in ch_oview

Às 12:10 de 09/08/2016, Frank H. Ellenberger escreveu: > Hi Pedro, > > Am 09.08.2016 um 11:24 schrieb Pedro Albuquerque: >> Hi Frank, all. >> >> Yes, there is a reason. *pt_PT* is the country code for Portugal, *pt* >> is the generic code for Portuguese, which means my translation could be >> confu

Re: Documentation translators: Changed para in ch_oview

Às 11:03 de 09/08/2016, Geert Janssens escreveu: > On Tuesday 09 August 2016 10:28:04 Pedro Albuquerque wrote: >> Às 05:46 de 09/08/2016, David T. via gnucash-devel escreveu: >>> Frank, >>> >>> As a git-challenged documentation contributor (I imagine my >>> git-clutziness is well-documented), is th

Re: Documentation translators: Changed para in ch_oview

Às 11:01 de 09/08/2016, Geert Janssens escreveu: > > On Tuesday 09 August 2016 10:24:30 Pedro Albuquerque wrote: > > > Hi Frank, all. > > > > > > Yes, there is a reason. *pt_PT* is the country code for Portugal, *pt* > > > is the generic code for Portuguese, which means my translation could > > > b

Re: Documentation translators: Changed para in ch_oview

Hi Pedro, Am 09.08.2016 um 11:24 schrieb Pedro Albuquerque: > Hi Frank, all. > > Yes, there is a reason. *pt_PT* is the country code for Portugal, *pt* > is the generic code for Portuguese, which means my translation could be > confused, for example, with Brazilian Portuguese whose country code i

Re: Documentation translators: Changed para in ch_oview

On Tuesday 09 August 2016 10:28:04 Pedro Albuquerque wrote: > Às 05:46 de 09/08/2016, David T. via gnucash-devel escreveu: > > Frank, > > > > As a git-challenged documentation contributor (I imagine my > > git-clutziness is well-documented), is there a non-git way you > > could present your change

Re: Documentation translators: Changed para in ch_oview

On Tuesday 09 August 2016 10:24:30 Pedro Albuquerque wrote: > Hi Frank, all. > > Yes, there is a reason. *pt_PT* is the country code for Portugal, *pt* > is the generic code for Portuguese, which means my translation could > be confused, for example, with Brazilian Portuguese whose country > code

Re: Documentation translators: Changed para in ch_oview

Às 05:46 de 09/08/2016, David T. via gnucash-devel escreveu: > Frank, > > As a git-challenged documentation contributor (I imagine my git-clutziness is > well-documented), is there a non-git way you could present your change, so > that I might examine it and maybe comment? > > To the list: > Is

Re: Documentation translators: Changed para in ch_oview

Hi Frank, all. Yes, there is a reason. *pt_PT* is the country code for Portugal, *pt* is the generic code for Portuguese, which means my translation could be confused, for example, with Brazilian Portuguese whose country code is *pt_BR* but is also Portuguese. Let's assume someone in Brasil decid

Re: Documentation translators: Changed para in ch_oview

On Tuesday 09 August 2016 13:37:02 David T. wrote: > Geert and Frank, > > I understand that these aspects of software development are clear and > easy for you; suffice to say they are not for me. I do not wish to > start any long discussion about the mechanisms for implementing > changes to GnuCas

Re: Documentation translators: Changed para in ch_oview

Geert and Frank, I understand that these aspects of software development are clear and easy for you; suffice to say they are not for me. I do not wish to start any long discussion about the mechanisms for implementing changes to GnuCash’s code and documentation; they have been hashed out many t

Re: Documentation translators: Changed para in ch_oview

On Tuesday 09 August 2016 09:46:00 David T. via gnucash-devel wrote: > Frank, > > As a git-challenged documentation contributor (I imagine my > git-clutziness is well-documented), is there a non-git way you could > present your change, so that I might examine it and maybe comment? Can you read a

Re: Documentation translators: Changed para in ch_oview

Frank, As a git-challenged documentation contributor (I imagine my git-clutziness is well-documented), is there a non-git way you could present your change, so that I might examine it and maybe comment? To the list: Is the group hoping to move away from bugs on Bugzilla in favor of an all-git

Re: Documentation Distribution

Geert, John, Thank you both for discussing this issue at length. I appreciate both your perspectives on this. With your further input, I humbly withdraw my immediate concern, with the following observations: 1) Not all documentation is equal. The Help files, as you’ve mentioned, only take 1-2

Re: Documentation Distribution

On Thursday 03 March 2016 08:45:29 John Ralls wrote: > > On Mar 3, 2016, at 8:13 AM, Geert Janssens > > wrote:> > > On Sunday 28 February 2016 09:40:49 John Ralls wrote: > > > For the guide I don't think it's unreasonable to remove it from > > > the > > > Help menu and simply direct people to www

Re: Documentation Distribution

> On Mar 3, 2016, at 8:13 AM, Geert Janssens wrote: > > On Sunday 28 February 2016 09:40:49 John Ralls wrote: > > For the guide I don't think it's unreasonable to remove it from the > > Help menu and simply direct people to www.gnucash.org > > to download it > > or rea

Re: Documentation Distribution

On Sunday 28 February 2016 09:40:49 John Ralls wrote: > For the guide I don't think it's unreasonable to remove it from the > Help menu and simply direct people to www.gnucash.org to download it > or read it online. That is of course an argument to keep help and guide two separate documents, so o

Fwd: Re: Documentation Distribution

Feb 2016 23:11:39 -0800 (PST) Subject: Re: Documentation Distribution To: John Ralls References: <2a66a063-963e-4c26-9bab-12c262f36...@yahoo.com> From: Frank H. Ellenberger X-Enigmail-Draft-Status: N1110 Message-ID: <56d3ef23.3050...@gmail.com> Date: Mon, 29 Feb 2016 08:11:31 +010

Re: Documentation Distribution

> On Feb 28, 2016, at 7:14 AM, David T. wrote: > > In looking at some documentation issues, I began to look at the package I > installed on my machine. I noticed that GnuCash ships with all four > documentation sets: English, German, Italian and Japanese. These > documentation sets take up a

Re: Documentation Regarding GnuCash Import Features

> On Aug 28, 2015, at 10:56 AM, Geert Janssens > wrote: > > On Friday 28 August 2015 09:07:09 David T. wrote: > > > On Aug 28, 2015, at 4:54 AM, John Ralls wrote: > > >> On Aug 28, 2015, at 9:03 AM, Geert Janssens > > >> mailto:geert.gnuc...@kobaltwit.be>> > > >> wrote: > > >> > > >> That's in

Re: Documentation Regarding GnuCash Import Features

On Friday 28 August 2015 09:07:09 David T. wrote: > > On Aug 28, 2015, at 4:54 AM, John Ralls wrote: > >> On Aug 28, 2015, at 9:03 AM, Geert Janssens > >> mailto:geert.gnuc...@kobaltwit.be>> > >> wrote: > >> > >> That's interesting: your focus appears to be on the "Concepts" > >> aspect of "Tutor

Re: Documentation Regarding GnuCash Import Features

> On Aug 28, 2015, at 4:54 AM, John Ralls wrote: > > >> On Aug 28, 2015, at 9:03 AM, Geert Janssens > > wrote: >> >> That's interesting: your focus appears to be on the "Concepts" aspect of >> "Tutorial and Concepts Guide". My focus was rather on "Tutorial".

Re: Documentation Regarding GnuCash Import Features

On Friday 28 August 2015 09:54:12 John Ralls wrote: > > On Aug 28, 2015, at 9:03 AM, Geert Janssens > > wrote: > > > > That's interesting: your focus appears to be on the "Concepts" > > aspect of "Tutorial and Concepts Guide". My focus was rather on > > "Tutorial". I guess the name itself is alre

Re: Documentation Regarding GnuCash Import Features

> On Aug 28, 2015, at 9:03 AM, Geert Janssens > wrote: > > That's interesting: your focus appears to be on the "Concepts" aspect of > "Tutorial and Concepts Guide". My focus was rather on "Tutorial". I guess the > name itself is already ambiguous. > > > There’s no chapter on Reports > > Y

Re: Documentation Regarding GnuCash Import Features

On Thursday 27 August 2015 15:28:49 John Ralls wrote: > > On Aug 27, 2015, at 11:30 AM, Geert Janssens > > wrote:> > > On Wednesday 26 August 2015 19:59:59 David T. wrote: > >> John, > >> > >> I am moving this thread to Devel, since it has moved beyond typical > >> user threads. > >> > >> Furth

Re: Documentation Regarding GnuCash Import Features

> On Aug 27, 2015, at 11:30 AM, Geert Janssens > wrote: > > On Wednesday 26 August 2015 19:59:59 David T. wrote: >> John, >> >> I am moving this thread to Devel, since it has moved beyond typical >> user threads. >> >> Further digging in the Help Manual shows section "3.3. Import QIF >> Files

Re: Documentation Regarding GnuCash Import Features

On Thursday 27 August 2015 09:30:25 John Ralls wrote: > > On Aug 27, 2015, at 12:59 AM, David T. wrote: > > > > John, > > > > I am moving this thread to Devel, since it has moved beyond typical > > user threads. > > > > Further digging in the Help Manual shows section "3.3. Import QIF > > Files

Re: Documentation Regarding GnuCash Import Features

On Wednesday 26 August 2015 19:59:59 David T. wrote: > John, > > I am moving this thread to Devel, since it has moved beyond typical > user threads. > > Further digging in the Help Manual shows section "3.3. Import QIF > Files," which explains that particular import process, but no other. > I sus

Re: Documentation Regarding GnuCash Import Features

> On Aug 27, 2015, at 12:59 AM, David T. wrote: > > John, > > I am moving this thread to Devel, since it has moved beyond typical user > threads. > > Further digging in the Help Manual shows section "3.3. Import QIF Files," > which explains that particular import process, but no other. I sus

Re: Documentation Regarding GnuCash Import Features

John, I am moving this thread to Devel, since it has moved beyond typical user threads. Further digging in the Help Manual shows section "3.3. Import QIF Files," which explains that particular import process, but no other. I suspect the interest in putting this information here has to do with

Re: Documentation: report options description place

Thank you for help! Made a pull request to gnucash-docs 2014-03-02 0:20 GMT+04:00 John Ralls : > > On Mar 1, 2014, at 12:02 PM, Dmitry Pavlov wrote: > > > Hello, > > I'm working on help documentation for budget report as an addition to my > > improvements

Re: Documentation: report options description place

On Mar 1, 2014, at 12:02 PM, Dmitry Pavlov wrote: > Hello, > I'm working on help documentation for budget report as an addition to my > improvements for it. Currently > there is no description neither in help nor in tutorial, so I want to add > it and

Re: Documentation

On Jan 7, 2014, at 4:58 AM, David Carlson wrote: > On 1/7/2014 12:11 AM, David wrote: >> John, >> >> I began looking through these bugs. The first covers documentation for >> GnuCash 1.7, and is assigned to Chris Lyttle. I don't recognize the name; >> would someone take a look at the bug ( >

Re: Documentation

On 1/7/2014 12:11 AM, David wrote: > John, > > I began looking through these bugs. The first covers documentation for > GnuCash 1.7, and is assigned to Chris Lyttle. I don't recognize the name; > would someone take a look at the bug ( > https://bugzilla.gnome.org/show_bug.cgi?id=98292) and see w

Re: Documentation

John, I began looking through these bugs. The first covers documentation for GnuCash 1.7, and is assigned to Chris Lyttle. I don't recognize the name; would someone take a look at the bug ( https://bugzilla.gnome.org/show_bug.cgi?id=98292) and see whether it can be closed, as I believe it proba

Re: Documentation file format

--On December 16, 2013 8:40:31 PM -0800 John Ralls wrote: You misunderstand: XMLEditor refuses to edit the included files from the master document. That's OK, they say that you have to load the module files separately, and provide a context menu item to do so if you load the master doc as a "d

Re: Documentation file format

On Dec 16, 2013, at 7:47 PM, David Carlson wrote: > On 12/16/2013 6:32 PM, Mike Alexander wrote: >> On Dec 16, 2013, at 5:49 PM, John Ralls wrote: >>> All of which is utterly moot, because it doesn’t work with our documents: >>> It requires that you open each file separately for editing. It wi

Re: Documentation file format

On Dec 16, 2013, at 4:32 PM, Mike Alexander wrote: > On Dec 16, 2013, at 5:49 PM, John Ralls wrote: >> >> All of which is utterly moot, because it doesn’t work with our documents: It >> requires that you open each file separately for editing. It will display the >> whole document just fine,

Re: Documentation file format

On 12/16/2013 6:32 PM, Mike Alexander wrote: > On Dec 16, 2013, at 5:49 PM, John Ralls wrote: >> All of which is utterly moot, because it doesn’t work with our documents: It >> requires that you open each file separately for editing. It will display the >> whole document just fine, but it won’t

Re: Documentation file format

On Dec 16, 2013, at 5:49 PM, John Ralls wrote: > > All of which is utterly moot, because it doesn’t work with our documents: It > requires that you open each file separately for editing. It will display the > whole document just fine, but it won’t let you edit anything that’s in a > separate f

Re: Documentation file format

On Dec 16, 2013, at 10:25 AM, Mike Alexander wrote: > On Dec 16, 2013, at 10:05 AM, John Ralls wrote: >> >> True, but it's non-obvious. The links to XMLEditor Personal Edition are on >> the download pages, linked at the bottom of this page. > > That page also says "XMLmind used to offer a Pe

Re: Documentation file format

On Dec 16, 2013, at 10:05 AM, John Ralls wrote: > > True, but it's non-obvious. The links to XMLEditor Personal Edition are on > the download pages, linked at the bottom of this page. That page also says "XMLmind used to offer a Personal Edition with version 5.3.0 and earlier, but as of Septem

Re: Documentation file format

On Dec 16, 2013, at 5:15 AM, Mike Evans wrote: > On Sun, 15 Dec 2013 14:58:21 -0500 > Mike Alexander wrote: > >> On Dec 15, 2013, at 8:13 AM, Geert Janssens >> wrote: >>> >>> Or if we want to stick with docbook, I searched for docbook wysiwyg. Most >>> editors are >>> proprietary and pric

Re: Documentation file format

On Sun, 15 Dec 2013 14:58:21 -0500 Mike Alexander wrote: > On Dec 15, 2013, at 8:13 AM, Geert Janssens wrote: > > > > Or if we want to stick with docbook, I searched for docbook wysiwyg. Most > > editors are > > proprietary and pricey. But there is also serna-free [1], which claims to > > be

Re: Documentation file format

On Dec 15, 2013, at 11:58 AM, Mike Alexander wrote: > On Dec 15, 2013, at 8:13 AM, Geert Janssens wrote: >> >> Or if we want to stick with docbook, I searched for docbook wysiwyg. Most >> editors are >> proprietary and pricey. But there is also serna-free [1], which claims to be >> a near w

Re: Documentation file format

Partially answering my own question: Am 15.12.2013 20:43, schrieb Frank H. Ellenberger: > Does or could this also work on other OSes than Linux with Yelp? we have in packaging/win32/install-impl.sh: make_chm ... So we have also compiled Windows Help files. ___

Re: Documentation file format

On Dec 15, 2013, at 8:03 AM, John Ralls wrote: > > I'll take a look at serna-free after I finish the release, which > unfortunately didn't get tagged last night because of problems with > code.gnucash.org. Which I’ve now done. Serna Free is free-as-in-beer. It was a free limited-feature ver

Re: Documentation file format

On Dec 15, 2013, at 8:13 AM, Geert Janssens wrote: > > Or if we want to stick with docbook, I searched for docbook wysiwyg. Most > editors are > proprietary and pricey. But there is also serna-free [1], which claims to be > a near wysiwyg > editor that can handle docbook 4 (according to a nab

Re: Documentation file format

Hi, I am still researching a few aspects. Am 13.12.2013 08:26, schrieb Christian Stimming: > I know I'm jumping in rather late in this thread, but here's my take on > the ever-long question of our documentation file formats: > > I think the priority of the documentation file format should be: >

Re: Documentation file format

On Dec 15, 2013, at 5:13 AM, Geert Janssens wrote: > On Saturday 14 December 2013 23:05:14 Christian Stimming wrote: > > Am Samstag, 14. Dezember 2013, 13:58:43 schrieb John Ralls: > > > Well, the friendliest format for documenters is Microsoft Word, > > > since pretty much any word processor wi

Re: Documentation file format

On Saturday 14 December 2013 23:05:14 Christian Stimming wrote: > Am Samstag, 14. Dezember 2013, 13:58:43 schrieb John Ralls: > > Well, the friendliest format for documenters is Microsoft Word, > > since pretty much any word processor will read it. We’ll get a lot > > of noise from the Open Source

Re: Documentation file format

Am Samstag, 14. Dezember 2013, 13:58:43 schrieb John Ralls: > Since no-one has mentioned it yet, what about asciidoc? It's much > simpler that the xml we have now, is very easy to learn, it is plain > text, it handles multi-part books, and AFAIK the current docbook can be > con

Re: Documentation file format

On Dec 14, 2013, at 1:32 PM, Christian Stimming wrote: > Am Freitag, 13. Dezember 2013, 15:47:18 schrieb Mike Evans: > Given these priorities, I think both our current documentation file > format and also a potential wiki workflow might not be the best > solution. Instead of the curr

Re: Documentation file format

Am Freitag, 13. Dezember 2013, 15:47:18 schrieb Mike Evans: > > >> Given these priorities, I think both our current documentation file > > >> format and also a potential wiki workflow might not be the best > > >> solution. Instead of the current file format (docbook xml, split into > > >> several f

Re: Documentation file format

On Fri, 13 Dec 2013 07:03:26 -0800 John Ralls wrote: > > On Dec 13, 2013, at 2:41 AM, Mike Evans wrote: > > > On Fri, 13 Dec 2013 08:26:42 +0100 > > Christian Stimming wrote: > > > >> I know I'm jumping in rather late in this thread, but here's my take > >> on the ever-long question of our

Re: Documentation file format

On Dec 13, 2013, at 2:41 AM, Mike Evans wrote: > On Fri, 13 Dec 2013 08:26:42 +0100 > Christian Stimming wrote: > >> I know I'm jumping in rather late in this thread, but here's my take >> on the ever-long question of our documentation file formats: >> >> I think the priority of the documen

Re: Documentation file format

On Fri, 13 Dec 2013 08:26:42 +0100 Christian Stimming wrote: > I know I'm jumping in rather late in this thread, but here's my take > on the ever-long question of our documentation file formats: > > I think the priority of the documentation file format should be: > - to generate HTML and PDF o

Re: Documentation file format

I know I'm jumping in rather late in this thread, but here's my take on the ever-long question of our documentation file formats: I think the priority of the documentation file format should be: - to generate HTML and PDF output from it - and to make it easy for documentation writers to edit th

Re: Documentation

On Dec 12, 2013, at 4:50 PM, David T. wrote: > F > John-- > I have moved the bar ever so slightly: I see that I can browse the Branch > Files and view the XML content of the guide. So somehow, I actually have > gotten the source onto my own computer. > > Actually editing stuff is another thin

Re: Documentation

From: John Ralls To: David T. Cc: Frank H. Ellenberger ; GnuCash development list Sent: Wednesday, December 11, 2013 7:47 PM Subject: Re: Documentation On Dec 11, 2013, at 1:29 PM, David T. wrote: Um, yeah. My point is that the developer pool would like help with documentation, and

Re: Documentation

On 12/11/2013 9:47 PM, John Ralls wrote: > On Dec 11, 2013, at 1:29 PM, David T. wrote: > >> Um, yeah. My point is that the developer pool would like help with >> documentation, and most users would be happy to do that, if it matched their >> mental model on how to edit documents. For most of us

Re: Documentation

On 12/11/2013 9:47 PM, John Ralls wrote: On Dec 11, 2013, at 1:29 PM, David T. wrote: >Um, yeah. My point is that the developer pool would like help with >documentation, and most users would be happy to do that, if it matched their >mental model on how to edit documents. For most of us (even m

Re: Documentation

On Dec 11, 2013, at 2:41 PM, Robert Ratliff wrote: > One suggestion: > > 1. Create a new page on the wiki, and paste in a chapter's worth or a > section's worth of documentation into the page. Save the page. Be sure > to refer to what version you're pasting in there as the "base version." > >

Re: Documentation

On Dec 11, 2013, at 1:29 PM, David T. wrote: > Um, yeah. My point is that the developer pool would like help with > documentation, and most users would be happy to do that, if it matched their > mental model on how to edit documents. For most of us (even more advanced > types with years of pr

Re: Documentation

id T. ; John Ralls Cc: GnuCash development list Sent: Wednesday, December 11, 2013 11:37 AM Subject: Re: Documentation Hi David, Am 11.12.2013 19:22, schrieb David T.: John— I’ll note that the GnuCash website Writing Documentation page, and it still includes all the information that scared David C

Re: Documentation

Wednesday, December 11, 2013 11:37 AM Subject: Re: Documentation Hi David, Am 11.12.2013 19:22, schrieb David T.: > John— > > I’ll note that the GnuCash website Writing Documentation page, and it > still includes all the information that scared David C. away (me too, > I’ll a

Re: Documentation

Hi David, Am 11.12.2013 19:22, schrieb David T.: > John— > > I’ll note that the GnuCash website Writing Documentation page, and it > still includes all the information that scared David C. away (me too, > I’ll add). Moreover, the directions there are all svn-based. Is there > a clear and simple o

Re: Documentation

On Dec 11, 2013, at 10:22 AM, David T. wrote: > John— > > I’ll note that the GnuCash website Writing Documentation page, and it still > includes all the information that scared David C. away (me too, I’ll add). > Moreover, the directions there are all svn-based. Is there a clear and simple >

Re: Documentation

John— I’ll note that the GnuCash website Writing Documentation page, and it still includes all the information that scared David C. away (me too, I’ll add). Moreover, the directions there are all svn-based. Is there a clear and simple outline of the git process for documentation that us non-pro

Re: Documentation

On Dec 11, 2013, at 7:01 AM, Martin Mainka wrote: > Hi, > i tried OO and ended up with a damaged xml file (changed tagnames, > different handling of pictures etc.) > Bummer. I wonder if the OO macros are set up for DocBook 5. Looks like the wiki is it, then. Regards, John Ralls

Re: Documentation

On Dec 11, 2013, at 6:05 AM, David Carlson wrote: > On 12/10/2013 10:27 PM, John Ralls wrote: >> On Dec 10, 2013, at 6:48 PM, David Carlson wrote: >> >>> 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 documentati

Re: Documentation

Am 11.12.2013 15:05, schrieb David Carlson: > On 12/10/2013 10:27 PM, John Ralls wrote: >> On Dec 10, 2013, at 6:48 PM, David Carlson wrote: >> >>> 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. Y

Re: Documentation

On 12/10/2013 10:27 PM, John Ralls wrote: > On Dec 10, 2013, at 6:48 PM, David Carlson wrote: > >> 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;

Re: Documentation

Hi David, 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

Re: Documentation

On Dec 10, 2013, at 6:48 PM, David Carlson wrote: > 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 t

Re: Documentation

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 con

Re: Documentation

Hallo Frank, Am 10.12.2013 22:26, schrieb Frank H. Ellenberger: > Hallo Johannes, > > Am 10.12.2013 20:25, schrieb Johannes Kapune: >> Hi, >> >> I can't see the list. I get an server error: >> >> >> "Internal Server Error >> >> The server encountered an internal error or misconfiguration and was

Re: Documentation

Hallo Johannes, Am 10.12.2013 20:25, schrieb Johannes Kapune: > Hi, > > I can't see the list. I get an server error: > > > "Internal Server Error > > The server encountered an internal error or misconfiguration and was > unable to complete your request. > > Please contact the server administr

Re: Documentation

Hi, I can't see the list. I get an server error: "Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, bugmas...@gnome.org and inform them of the time the error occurred, and anythin

Re: Documentation release

Here you can download a copy of the Japanese guide built from 2.4 branch revision 22575 https://dl.dropbox.com/u/10312034/gnucash-guide.pdf Il 19/11/2012 20:51, Geert Janssens ha scritto: The documentation has been released successfully, with one exception: I haven't been able to generate a n

  1   2   >