On 12/24/24 8:35 AM, Gavin Smith wrote:
I have raised an issue on the "yelp" bug tracker to contact
the yelp developers:
https://gitlab.gnome.org/GNOME/yelp/-/issues/220
Please let us know if anybody knows any other way that we should get in
touch with them. Also people may have other ideas to share on the best
way forward on the "HTML-Info" question.
I'm surprised you didn't mention the JavaScript info reader.
in the js directory. It has no dependency on any particular
browser, but should run fine in WebKitGTK.
I think at some point I looked at the WebKitGTK-based info reader,
but I don't remember how it compared. I think it had some niceties
compared to the pure-js version, but not enough to justify
a separate WebKitGTK code-base. It might be worthwhile for
the js reader to have some hooks that could be used by Yelp/WebKitGtk.
If Yelp uses different keybindings and other UI that traditional info, it
would be easy to modify js-info to match.
As a bonus for Yelp, js-info is not inherently restricted to
texinfo output, but can be used for any html files that
follow a reasonable set of conventions (which we should document).
There might be licensing concerns with the GPL3-only js-info;
if so re-licensing js-info might be worth considering.
--
--Per Bothner
[email protected] http://per.bothner.com/
