Re: Any interest in using HTML for locally-installed Texinfo documentation?

Hello, Gavin Smith skribis: > On Sun, Nov 03, 2019 at 03:04:27PM +0100, Ludovic Courtès 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. &

Re: Any interest in using HTML for locally-installed Texinfo documentation?

Hi Gavin, Gavin Smith skribis: > On Sat, Oct 19, 2019 at 9:31 PM Ludovic Courtès wrote: >> > I started another line of development, using the WebKitGTK engine. >> > http://git.savannah.gnu.org/cgit/texinfo.git/log/?h=webkitgtk-info >> >> [...] >> >>

Re: Any interest in using HTML for locally-installed Texinfo documentation?

Hi Gavin, Gavin Smith skribis: > I started another line of development, using the WebKitGTK engine. > http://git.savannah.gnu.org/cgit/texinfo.git/log/?h=webkitgtk-info [...] > I may be able to get an initial prototype that other people could try > ready in a few days. As ever, if anyone is in

Re: htmlxref.cnf vs. manual names with a dot

Hi Gavin, Gavin Smith skribis: > On Mon, May 06, 2019 at 12:18:21PM +0200, Ludovic Courtès wrote: [...] >> In fact—but that’s another story—I’d like to suggest improvements so >> that the Info readers automatically open ‘dir.LANG’, when available, >> instead of just

Re: htmlxref.cnf vs. manual names with a dot

Hi Gavin, Gavin Smith skribis: > Hello Ludo, the extension is stripped in the _external_node_href > function in HTML.pm. I found this one-line change would give the > desired output (when I added those lines to htmlxref.cnf): > > diff --git a/tp/Texinfo/Convert/HTML.pm b/tp/Texinfo/Convert/HT

htmlxref.cnf vs. manual names with a dot

Hello! The Guix manual has this bit of text: --8<---cut here---start->8--- This manual is also available in Simplified Chinese (@pxref{Top,,, guix.zh_CN, GNU Guix参考手册}), French (@pxref{Top,,, guix.fr, Manuel de référence de GNU Guix}), German (@pxref{Top,,, gui

Re: Any interest in using HTML for locally-installed Texinfo documentation?

Hello, Gavin Smith skribis: > On Tue, Apr 02, 2019 at 09:46:05AM -0700, Per Bothner wrote: >> Both Electron and QtWebEngine have mechanisms for communicating between >> the "browser" window and the main application, which is not sandboxed. >> (For QtWebEngine the main application is regular non-

Re: Any interest in using HTML for locally-installed Texinfo documentation?

Hi Gavin, Gavin Smith skribis: > On Wed, Apr 03, 2019 at 11:11:36PM +0200, Ludovic Courtès wrote: [...] >> I was mentioning this because it’s an experiment that Andy Wingo did >> about 15 years (?!) ago. Andy wrote the Texinfo parser that’s now part >> of Guile, and

Re: Any interest in using HTML for locally-installed Texinfo documentation?

Hi Per, Per Bothner skribis: > On 4/2/19 2:37 AM, Ludovic Courtès wrote: >> Yet I’m not completely sold to the everything in the browser approach, >> and everything in JavaScript. In an ideal world (for me), we’d rather >> provide a local documentation viewer > >

Re: Any interest in using HTML for locally-installed Texinfo documentation?

Gavin Smith skribis: > On Tue, Apr 02, 2019 at 11:37:51AM +0200, Ludovic Courtès wrote: >> (For some reason ‘i’ does open the index search box for me, but then >> hitting enter doesn’t produce any effect. The other navigation commands >> work fine, though.) > > It wo

Re: Any interest in using HTML for locally-installed Texinfo documentation?

Hello Gavin, Gavin Smith skribis: > Documentation for GNU packages and others is often installed in the > Info format, a plain text format. Using a plaintext based format for > documentation does not take advantage of bitmapped displays that have > been available for decades. It does not allow

Re: "Up (dir)" HTML link is 404

Hi, Gavin Smith skribis: > The way to deal with this broken link at the moment is to use the > TOP_NODE_UP customization variable, like > > makeinfo --html -c TOP_NODE_UP_URL=/manual/ ... > > https://www.gnu.org/software/texinfo/manual/texinfo/html_node/First-Node.html#First-Node That sounds g

"Up (dir)" HTML link is 404

Hello, Following the “Up (dir)” from: https://www.gnu.org/software/guix/manual/html_node/index.html#Top leads to: https://www.gnu.org/software/guix/manual/dir/index.html which is 404. Can htmlxref.cnf specify what the “dir” URL should be? If so, what about hosting a “dir” somewhere on gn

Re: 'info -k' segfaults

Gavin Smith skribis: > On 24 November 2015 at 20:10, Ludovic Courtès wrote: >> Gavin Smith skribis: >> >>> On 24 November 2015 at 09:50, Ludovic Courtès wrote: >>>> After some testing, I found that the segfault happens specifically when >>>>

Re: 'info -k' segfaults

Gavin Smith skribis: > On 24 November 2015 at 09:50, Ludovic Courtès wrote: >> After some testing, I found that the segfault happens specifically when >> gdbm.info is installed (from gdbm 1.11); other manuals seem to be OK. > > > I have a gdbm.info file but don't g

'info -k' segfaults

‘info -k’ reproducibly crashes here: --8<---cut here---start->8--- $ valgrind info -k grep ==6618== Memcheck, a memory error detector ==6618== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==6618== Using Valgrind-3.11.0 and LibVEX; rerun with -

Re: Info reader fails to follow xrefs to anchors

Gavin Smith skribis: > On 13 July 2015 at 21:21, Ludovic Courtès wrote: >> File attached. As an example: Go to “Substitutes” and try to follow the >> anchors ‘daemon-substitute-urls’ and ‘client-substitute-urls’ (see >> <http://git.savannah.gnu.org/cgit/guix.git/

Re: Info reader fails to follow xrefs to anchors

Gavin Smith skribis: > On 13 July 2015 at 15:24, Ludovic Courtès wrote: >> The standalone Info reader in Texinfo 6.0 fails to follow >> cross-references to anchors: Following such a link leads to an unrelated >> place in the document. This is a regression compared to Texi

Re: Info reader fails to follow xrefs to anchors

Eli Zaretskii skribis: >> From: l...@gnu.org (Ludovic Courtès) >> Date: Mon, 13 Jul 2015 16:24:33 +0200 >> >> Unfortunately the Emacs Info reader has had the same problem for a long >> time, but I suppose this one should go to bug-emacs? > > Yes, but what Ema

Info reader fails to follow xrefs to anchors

Hello, The standalone Info reader in Texinfo 6.0 fails to follow cross-references to anchors: Following such a link leads to an unrelated place in the document. This is a regression compared to Texinfo 5.2 (guix.texi is one example that illustrates the bug.) Unfortunately the Emacs Info reader h

Re: Who owns dir and {standards,configure}.info?

Hi, Brandon! Brandon Invergo skribis: >> Seems to me that {configure,standards}.info should be installed >> exclusively by Autoconf. > > These files have been automatically blocked in GSRC since its original > GAR days. By the way, another problem file is libiberty, which is > installed by a co

Re: Who owns dir and {standards,configure}.info?

k...@freefriends.org (Karl Berry) skribis: > As far as I know, configure.texi does not exist in autoconf and never > has. It was written by Cygnus (hence gdb/binutils) and doesn't seem to > have been updated in many years. Much of it still looks somewhat > meaningful, other parts look obsolete.

Re: Who owns dir and {standards,configure}.info?

Eli Zaretskii skribis: >> From: l...@gnu.org (Ludovic Courtès) >> Cc: bug-texinfo@gnu.org >> Date: Fri, 13 Dec 2013 12:05:33 +0100 >> >> > 'dir' should not be installed, it should be updated by running >> > install-info. I suggest to file

Re: Who owns dir and {standards,configure}.info?

Eli Zaretskii skribis: >> From: l...@gnu.org (Ludovic Courtès) >> Date: Fri, 13 Dec 2013 10:34:50 +0100 >> >> Several Info files have been distributed and installed by several >> packages for a long time, notably: >> >> dir – installed by Emacs, GCC,

Re: [PATCH] Add URLs for the dmd, Guix, and lsh manuals

k...@freefriends.org (Karl Berry) skribis: > Thanks Ludo. Installed and updated on ftp.gnu.org. Thanks. > Unfortunately, I see that the lsh manual > (http://www.lysator.liu.se/~nisse/lsh/lsh.html) does not follow the node > naming conventions (real spaces instead of - in multiword node names, a

Who owns dir and {standards,configure}.info?

Hi, Several Info files have been distributed and installed by several packages for a long time, notably: dir – installed by Emacs, GCC, GDB configure.info – installed by GDB and Binutils standards.info – installed by GDB, Binutils, Autoconf The problem is that it makes it difficult as a us

[PATCH] Add URLs for the dmd, Guix, and lsh manuals

Hi, The patch below against adds a few URLs. Thanks, Ludo’. --- htmlxref.cnf.orig 2013-12-11 23:37:41.0 +0100 +++ htmlxref.cnf 2013-12-11 23:56:22.0 +0100 @@ -1,6 +1,6 @@ # htmlxref.cnf - reference file for free Texinfo manuals on

Re: makeinfo swallows page breaks

l...@gnu.org (Ludovic Courtès) skribis: > Alternately, would you suggest using a different approach? Attached is a patch to use Guile’s Texinfo support [0] to build said file. Guile’s Texinfo parser is incomplete but sufficient to handle those docstrings. It solves an actual bug for any

makeinfo swallows page breaks

Hello, Guile (ab)uses ‘makeinfo’ to generate a file, guile-procedures.txt, from Texinfo. That file is then read at run-time to get docstrings for Guile’s primitives. The input looks like this (note the page breaks, aka. ^L): --8<---cut here---start->8--- ac

Typographical glitch in cross-references

Hi, In TeX output, cross-references to external documents yield something like "see section XX of YY", while it should really be "see Section XX of YY". Thanks, Ludovic.