From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: Any interest in using HTML for locally-installed Texinfo documentation? Date: Wed, 06 Nov 2019 22:49:26 +0100 Message-ID: <87ftj0vfo9.fsf@gnu.org> References: <87a7h8u4r4.fsf@gnu.org> <20190402150245.GA30067@darkstar> <256d60e8-0148-1dd3-4c9d-86e14b42060b@bothner.com> <20190407162804.GA28500@darkstar.example.net> <87k1g4v8dq.fsf@gnu.org> <20190413162121.GA28137@darkstar.example.net> <87eez8tr33.fsf@gnu.org> <87imo16opg.fsf@gnu.org> <20191103153725.GA29886@mintstar> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20191103153725.GA29886@mintstar> (Gavin Smith's message of "Sun, 3 Nov 2019 15:37:25 +0000") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-texinfo-bounces+gnu-bug-texinfo2=m.gmane.org@gnu.org Sender: "bug-texinfo" To: Gavin Smith Cc: guix-devel@gnu.org, Texinfo List-Id: guix-devel.gnu.org Hello, Gavin Smith skribis: > On Sun, Nov 03, 2019 at 03:04:27PM +0100, Ludovic Court=C3=A8s wrote: [...] >> Does the reader fall back to an on-line copy of manuals that are >> unavailable locally? That would be nice, though it should probably >> first ask for user consent. > > It doesn't do that yet. It would have to look at an htmlxref.cnf file or= =20 > equivalent, as the URL for the remote manual should not be in the locally= =20 > installed documentation. Sounds like a plan. >> I=E2=80=99d love to see an appropriate CSS applied by default to all the= locally >> installed manual. Perhaps the WebKitGTK code could =E2=80=9Cforce=E2=80= =9D a CSS to >> each HTML page? > > It is possible using webkit_web_view_new_with_user_content_manager. Neat. >> In the future, it=E2=80=99d be great to have syntax highlighting like we= have at >> , >> but=E2=80=A6 I guess that=E2=80=99s another story. :-) > > How is that done? Are the HTML file post-processed somehow? Yes, it=E2=80=99s a bit ugly: we post-process the HTML in search of 

blocks (which correspond to @lisp) pass them through
guile-syntax-highlight.  There=E2=80=99s a bit of CSS for the rainbow
parentheses.  See
.

>> What would be the next steps for you?  Do you plan to have this new
>> reader released as part of the next Texinfo release, or as a separate
>> package?
>
> It would probably be for a separate package.  At the moment the program=20
> is called "infog" standing for "Info GTK".

OK.

> There are various things that need to be done before it is ready for=20
> release:
> * Allow installing the program, so that it can be run via PATH
> * Handle external links in a web browser (using some kind of user=20
> desktop default)
> * I'd like to make the index search completions in a separate pane=20
> rather than a pop-up menu, as in the "devhelp" program.
> * Perhaps support for tabs
> * The program uses a deprecated API in the WebKitGTK library to access=20
> the DOM of pages.  Allegedly it is possible to use JavaScript to do the=20
> same thing, but the documentation is not that helpful on how to do this.
> * There is no text search facility in pages
> * Standardize a location for installing HTML manuals.  What the GNU=20
> Coding Standards currently says about "htmldir" is insufficient, as a=20
> manual may have a different name to the package it is part of.
> * It would be nice if the text input for a new window could be done as=20
> some kind of pop-over widget rather than in a separate dialog box.

Good.  I don=E2=80=99t think any of these are a showstopper, except perhaps=
 the
bit about standardizing HTML installation (and getting distros to
actually do that!).  Other than that, your program is already useful as
it is, IMO.

> I only have a few hours a week to spend on this, so it could take me=20
> some time to get through it.
>
> I have been looking at tweaking the output of texi2any so the HTML looks=
=20
> better in this browser, including using mini-tables of contents instead=20
> of menus, and the table of contents linking to the top of a page rather=20
> than to an anchor a little down the page.

Nice.

Ludo=E2=80=99.