Op dinsdag 6 september 2022 19:00:47 CEST schreef Frank H. Ellenberger: > Am 06.09.22 um 06:01 schrieb john: > >> On Sep 5, 2022, at 2:01 PM, Frank H. Ellenberger > >> <frank.h.ellenber...@gmail.com> wrote: > >> > >> Hi, > >> > >> Am 05.09.22 um 22:27 schrieb Geert Janssens: > >>> Op maandag 5 september 2022 19:09:06 CEST schreef john: > >>>> This is https://bugs.gnucash.org/show_bug.cgi?id=798612 > >>>> > >>>> I discovered while researching this that yelp v.42 just dropped support > >>>> for > >>>> the ghelp: scheme. help:gnucash-help and help:gnucash-guide are able to > >>>> find the GnuCash docs > >>> > >>> I'm surprised the help: scheme finds the documentation in the old ghelp > >>> locations, but that's good news really. > >>> I think we best add this in for gnucash 4.12 then, and conditional on > >>> the yelp version. > >> > >> Why conditional, IIRC help: is defined in yelp for about a decade. > > > > Because yelp v3.x (and maybe v40 and v41, I didn't have those handy to > > test) can't find the GnuCash docs in /usr/share/docs/gnucash-docs with > > help: so we have to use ghelp: on distros that are still shipping older > > versions of yelp. > > > > Regards, > > John Ralls > > From https://gitlab.gnome.org/GNOME/yelp/-/blob/master/NEWS > > > Changes in 2.31.5: > > ------------------ > > * New "Read Later" feature > > * Support for proposed XDG help: URI scheme > > They should find /usr/share/help/{lang}/… > > Why do you want to unstall into /usr/share/docs/? > Also ghelp: did not recognitze that. > It used /usr/share/gnome/help/… > > Regards > Frank
I've explained the difference in my other reply. I think this is a bug in ubuntu packaging; they seem to ship our html format and no longer our docbook format. Regards, Geert _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.