Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread David Cousens
David, I also subscribe to your manifesto: I agree that the Concept guide should be just that. Not how to specifically do something using Gnucash 1. A minimal set of basic accounting concepts with reference perhaps to more detailed material. 2. Some discussion how GnuCash implements these:

Re: [GNC-dev] Autogenerated GUI description? was: Long Term Documentation Directions

2018-09-10 Thread John Ralls
> On Sep 10, 2018, at 2:41 PM, Frank H. Ellenberger > wrote: > > > > Am 10.09.2018 um 13:46 schrieb Geert Janssens: >> Op zondag 9 september 2018 12:21:08 CEST schreef Frank H. Ellenberger: > : >>> ?: Usability: Will F1 or pressing the Help button still deliver the >>> right content? I know

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread Frank H. Ellenberger
Hi David Cousens, I opened Bug 796852 - Context sensitive Help broken. Can you add the details there? TIA Frank Am 11.09.2018 um 04:13 schrieb David Cousens: > Geert, > > No, my mistake in thinking it was in yelp Geert. I was looking into > something else at the time and just noticed that the

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread David Cousens
Geert, It can process HTML but I haven't yet put other markup through it. I am not sure how to batch it but there is an interface which will up load a file and translate it and presumably allow you to save it back. I doubt if you would use it if you have an active translator available for a

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread David Cousens
Geert, No, my mistake in thinking it was in yelp Geert. I was looking into something else at the time and just noticed that the context Help did not come up in passing yesterday. Imentioned it in the post last night without having checked it out fully. My apologies for that. When it happened I

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread David Cousens
Chris, It maybe worth pursuing if libwebkit can support context sensitive help. It HTML Help on Windows I believe a set of aliases mapped onto URLs for the appropriate section of HTML help files from the help file is generated by the processor and then used to pull up the appropriate section of

[GNC-dev] Autogenerated GUI description? was: Long Term Documentation Directions

2018-09-10 Thread Frank H. Ellenberger
Am 10.09.2018 um 13:46 schrieb Geert Janssens: > Op zondag 9 september 2018 12:21:08 CEST schreef Frank H. Ellenberger: : >> ?: Usability: Will F1 or pressing the Help button still deliver the >> right content? I know it is aslo now not always th case. >> > If I read David's proposal carefully

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread Frank H. Ellenberger
Am 10.09.2018 um 00:32 schrieb D: > Frank, > > You raise significant points about the effect that this might have on > translations. > > How would it be if these changes occurred in the course of a piecemeal > approach? In other words, if I or someone else were to essentially remove the >

Re: [GNC-dev] merging failing tests

2018-09-10 Thread Carsten Rinke
Thanks for all your comments. @John, Geert: Thanks for bringing the expectations to the point that unit tests as such and especially on master/maint always must pass. I also get the point that further refinement of the test results by utilitzing the verdicts "xpass" and "xfail" is not desired.

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread David T. via gnucash-devel
OK. In reply to my own message, I have paged through the Help and compared it to the Guide. I compiled a mapping framework from Help to the Guide, and found that this might not be as huge an undertaking as I initially thought. Here are my thoughts: 1. Introduction to GnuCash

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread David T. via gnucash-devel
Dear All, I reply to this message (even though it lacks the previous discussions for context), as it is the latest in the thread. I will, however, try to take on some of the issues that have gotten raised. I apologize for the length and density of the reply. With regard to translations, I am

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread Geert Janssens
Op maandag 10 september 2018 15:26:19 CEST schreef David Cousens: > Geert, > > Is there not perhaps a way to leverage Google translate as a first pass to > translate text. The result may not be colloquial and produce some > interesting results. I have used it for Russian to English translations

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread David Cousens
XInclude reference also modular files: http://sagehill.net/docbookxsl/ModularDoc.html. It should just require using a switch on xsltproc --xinclude when building David - David Cousens -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread David Cousens
Geert, Is there not perhaps a way to leverage Google translate as a first pass to translate text. The result may not be colloquial and produce some interesting results. I have used it for Russian to English translations and it doesn't do too bad a job.

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread David Cousens
Geert Docbook has a mechanism for including other xlm files either by declaring an ENTITY which maps on to the filename containing the snippet xml code. You can then use & to include the file contents at any point. You can also construct "header files" which contain the entity definitions which

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread Geert Janssens
Op maandag 10 september 2018 13:51:28 CEST schreef Christopher Lam: > On Mon, 10 Sep 2018 at 19:31, David Cousens > > wrote: > > One problem I see for Unix is that at present there doesn't appear to be a > > help viewer in Unix that has support for context level help. Doc books can > > obviously

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread Christopher Lam
On Mon, 10 Sep 2018 at 19:31, David Cousens wrote: > > One problem I see for Unix is that at present there doesn't appear to be a > help viewer in Unix that has support for context level help. Doc books can > obviously support defining links that can be accessed from help buttons or > a > key

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread Geert Janssens
Op maandag 10 september 2018 13:30:20 CEST schreef David Cousens: > One problem I see for Unix is that at present there doesn't appear to be a > help viewer in Unix that has support for context level help. Doc books can > obviously support defining links that can be accessed from help buttons or a

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread Geert Janssens
Op zondag 9 september 2018 12:21:08 CEST schreef Frank H. Ellenberger: > -: I18N: We will loose the current translations and probably frustrate > the last translators and loose their readers. > Absolutely true. However I don't know if that's sufficient reason to keep the less that satisfactory

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread David Cousens
Thanks Geert My apologies to David T if I misunderstood the intention re a single document. A single document with separate sections may help to reduce duplication, but that mainly requires editorial effort no matter whether it is a single document or not. it would certainly help with searches.

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread Geert Janssens
Op zaterdag 8 september 2018 16:57:52 CEST schreef David T. via gnucash-devel: > Hello, > > As I have noted in another thread recently, I am finding the process of > updating the various documentation pieces extremely challenging—due in > large part to the fragmented nature of this documentation.

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread Geert Janssens
Op maandag 10 september 2018 10:11:11 CEST schreef David Cousens: > David, > > As well as Frank's objections to rewriting, why does having one massive file > necessarily improve the structure or maintainability. This is not the case > with programming code. Docbook can include files in a far more

Re: [GNC-dev] Long Term Documentation Directions

2018-09-10 Thread David Cousens
David, As well as Frank's objections to rewriting, why does having one massive file necessarily improve the structure or maintainability. This is not the case with programming code. Docbook can include files in a far more structured manner than the gnucash xml sources do at the moment. I would