Re: XSParagraph build failure with static libperl

On Mon, Jun 05, 2017 at 08:50:48PM +0100, Gavin Smith wrote: > On Mon, Jun 05, 2017 at 12:14:04PM -0700, Li Er wrote: > > I tried my build with TEXINFO_XS=debug and it states 'XSParagraph.so > > loaded', > > so I think it's working well. > > > > If there's no

Re: Texinfo manual: Sentence spacing

On 16 June 2017 at 14:46, Vincent Lefevre wrote: > Hi, > > In the Texinfo manual, section on @frenchspacing: > > > https://www.gnu.org/software/texinfo/manual/texinfo/html_node/_0040frenchspacing.html > > "In American typography, it is traditional and correct to put >

texinfo-6.3.92 pretest

The next pretest for the next Texinfo release has been uploaded to http://alpha.gnu.org/gnu/texinfo/texinfo-6.3.92.tar.xz If all goes well, we hope to release this as Texinfo 6.4 in a few days' time. Please send any comments to bug-texinfo@gnu.org. Changes since last pretest: * Do not require

Re: Gavin's gpg key is not on texinfo's keyring on Savannah

On Mon, May 01, 2017 at 09:17:40PM +0200, Benno Schulenberg wrote: > > Hi, > > The keyring from > https://savannah.gnu.org/project/memberlist-gpgkeys.php?group=texinfo > contains keys for most project members except for the one who > actually makes and signs the latest releases. It would be

Re: Gavin's gpg key is not on texinfo's keyring on Savannah

On Sun, May 07, 2017 at 04:39:25PM +0200, Benno Schulenberg wrote: > > On Sun, May 7, 2017, at 13:48, Gavin Smith wrote: > > On Mon, May 01, 2017 at 09:17:40PM +0200, Benno Schulenberg wrote: > > > The keyring from > > > https://savannah.gnu.org/project/member

Re: texinfo-6.3.90 pretest

On Sat, Apr 29, 2017 at 11:25:44AM +0100, Gavin Smith wrote: > The test was introduced in SVN revision 5345 on 2013-08-27. I think > it is supposed to test that the CR characters are being ignored, but > they aren't in the macro definition, so this looks like a bug. I've committed

Re: texinfo-6.3.90 pretest

On Sun, Apr 30, 2017 at 05:37:53PM +0300, Eli Zaretskii wrote: > > Date: Sat, 29 Apr 2017 11:18:33 +0300 > > From: Eli Zaretskii <e...@gnu.org> > > Cc: bug-texinfo@gnu.org > > > > > From: Gavin Smith <gavinsmith0...@gmail.com> > > > Date:

Re: M-F passes over a node boundary, but M-B does not

On Mon, May 01, 2017 at 09:36:54PM +0200, Benno Schulenberg wrote: > > Now press until the cursor has passed the "N" of "Next", > > it doesn't matter how far. Then press until the cursor is > > exactly on the "N". Now press M-B. Now the cursor *does* pass > > over the node boundary. > > It

Re: Math styles

On Tue, May 23, 2017 at 07:10:53PM +0200, Hans Åberg wrote: > [I am not on list, so please cc me.] > >. I want to use Texinfo for a program that uses UTF-8 @code, including >math styles, and as such, the solution to that does not matter. Cf. >sample [1]. Perhaps it requires some further

Re: Math styles

I attach your input file as sample.texi. I thought I might have trouble running LuaTeX so first I tried it by deleting the lines from the file which used LuaTeX. I've attached this as sample-fixed.texi. Running TeX on this file went okay, apart from a few error messages: l.64: Unicode char

Re: some more little things about --vi-keys

On Sun, May 21, 2017 at 12:49:17PM +0200, Benno Schulenberg wrote: > Maybe bind ":1" and ":$" to beginning-of-node and > end-of-node? I am not personally interested in doing much work on --vi-keys mode other than fixing bugs or inaccuracies in the documentation. If someone sends a patch I can

Re: XSParagraph build failure with static libperl

On Mon, Jun 05, 2017 at 12:14:04PM -0700, Li Er wrote: > I tried my build with TEXINFO_XS=debug and it states 'XSParagraph.so loaded', > so I think it's working well. > > If there's no shared libperl, XS module simply uses the symbols exported > by the perl binary. I also had a look at debian's

Re: [PATCH] Prefer HTTPS to HTTP and FTP in texinfo.tex

On Sat, Sep 16, 2017 at 10:34:46AM -0700, Paul Eggert wrote: > In Gnulib, Emacs, etc. we are changing ftp: and http: URLs to use https:, to > discourage man-in-the-middle attacks when downloading software. The attached > patch propagates these changes upstream to texinfo.tex. This patch doesn't >

Re: [PATCH] Add 'pre-inst-env' wrapper script

On Sat, Aug 26, 2017 at 06:41:47PM +0200, Mathieu Lirzin wrote: > Hello, > > While hacking on 'texi2any' and testing my changes with manuals located > in various places in the filesystem, I found it cumbersome to launch the > non installed 'makeinfo' like this: > > TEXINFO_DEV_SOURCE=1

Re: [PATCH] Add 'pre-inst-env' wrapper script

On Fri, Sep 22, 2017 at 12:26:46PM +0200, Mathieu Lirzin wrote: > I think you forgot to include build-aux/pre-inst-env.in in revision > r7954. OK I have committed that file. > Additionnally some cleanups could be done such as removing the > 'top_builddir' and 'top_srcdir' environment variables

Re: texinfo-6.4.91 pretest

On Mon, Aug 28, 2017 at 06:30:28PM +0300, Eli Zaretskii wrote: > > From: Gavin Smith <gavinsmith0...@gmail.com> > > Date: Sun, 27 Aug 2017 18:58:18 +0100 > > > > The pretest for the next release of Texinfo has been updated: > > > > https://alpha

Re: texinfo-6.4.91 pretest

On Wed, Aug 30, 2017 at 10:10:22PM +0300, Eli Zaretskii wrote: > May I suggest to add your rationale to the ChangeLog entry? Because > my problem was not with finding out about the change, it was with > understanding why it was made. I thought perhaps this code got in the > way in some use case.

Re: `1 menu-digit' stopped working after upgrading to 6.x

On Tue, Aug 29, 2017 at 06:46:54PM +0800, Clark Wang wrote: > *(Sorry I forgot to write a subject in my last email. Resending...)* > > Recently I updated my Debian system and texinfo is now at 6.3. I found the > infokey program is not necessary any more and I like it. > > But the `1 menu-digit'

Re: recent debian perl tests failures without . in @INC

On Tue, Aug 29, 2017 at 11:48:17AM +0200, Patrice Dumas wrote: > Hello, > > Recent perl in debian do not have . in @INC anymore, and it will be > upstream in perl 5.26. > https://lists.debian.org/debian-devel-announce/2016/08/msg00013.html It seems very awkward. Do you know if running "make

Re: texinfo-6.4.92 pretest

On Mon, Sep 04, 2017 at 06:36:44PM -0600, Assaf Gordon wrote: > Hello, > > On 04/09/17 01:51 PM, Gavin Smith wrote: > > https://alpha.gnu.org/gnu/texinfo/texinfo-6.4.92.tar.xz > > No test failures on the following: Thanks for running these tests. > Failure to link on AI

Re: Split two-word note xref fail

On Mon, Sep 11, 2017 at 10:39:44PM -0300, Arthur Szász wrote: > For instance, in the end of the > ​ ​ > file > ​ '​ > info-stnd > ​' > node > ​ '​ > ​ > Invoking Info > ​'​ > > pasted below, > ​ ​ > the first xref to > ​ > '​ > Custom Key Bindings > ​' > ​ > ​ ​ > does not select > the node, but

Texinfo 6.5 released

We have released version 6.5 of Texinfo, the GNU documentation format. This package contains tools to produce documentation in various formats, including HTML and PDF, from source files in the Texinfo format. Texinfo is a text-based format with commands for marking text, document structuring and

Re: [PATCH] Remove encoding warning in Firefox

On Sat, Aug 26, 2017 at 05:20:59PM +0200, Mathieu Lirzin wrote: > Oops I saw you fixed some tests I missed. I didn't enable the > "--enable-tp-tests" configure option. Sorry about that. > I think you have to have some extra Perl modules installed to run those tests, which may explain why you

Re: [PATCH] Add 'pre-inst-env' wrapper script

On Sat, Aug 26, 2017 at 06:41:47PM +0200, Mathieu Lirzin wrote: > Hello, > > While hacking on 'texi2any' and testing my changes with manuals located > in various places in the filesystem, I found it cumbersome to launch the > non installed 'makeinfo' like this: > > TEXINFO_DEV_SOURCE=1

Re: [PATCH] Add 'pre-inst-env' wrapper script

On Sat, Aug 26, 2017 at 10:04:11PM +0200, Mathieu Lirzin wrote: > Gavin Smith <gavinsmith0...@gmail.com> writes: > > > On Sat, Aug 26, 2017 at 06:41:47PM +0200, Mathieu Lirzin wrote: > >> Hello, > >> > >> While hacking on 'texi2any' and testing my

Re: [PATCH] Remove encoding warning in Firefox

On Sat, Aug 26, 2017 at 07:22:23PM +0100, Gavin Smith wrote: > On Sat, Aug 26, 2017 at 05:20:59PM +0200, Mathieu Lirzin wrote: > > Oops I saw you fixed some tests I missed. I didn't enable the > > "--enable-tp-tests" configure option. Sorry about that. > > >

Re: [PATCH] Remove encoding warning in Firefox

On Sun, Aug 27, 2017 at 10:49:02AM +0100, Gavin Smith wrote: > On Sat, Aug 26, 2017 at 07:22:23PM +0100, Gavin Smith wrote: > > On Sat, Aug 26, 2017 at 05:20:59PM +0200, Mathieu Lirzin wrote: > > > Oops I saw you fixed some tests I missed. I didn't enable the > > > &q

texinfo-6.4.91 pretest

The pretest for the next release of Texinfo has been updated: https://alpha.gnu.org/gnu/texinfo/texinfo-6.4.91.tar.xz There have only been a handful of changes since the last pretest release (6.4.90). It is possible that this will be released as Texinfo 6.5 in a few days' time. This is mainly a

Re: texinfo-6.4.91 pretest

On Sun, Aug 27, 2017 at 10:32:28PM -0600, Assaf Gordon wrote: > Hello Gavin, > > > On Sun, Aug 27, 2017 at 11:58 AM, Gavin Smith <gavinsmith0...@gmail.com> > wrote: > > https://alpha.gnu.org/gnu/texinfo/texinfo-6.4.91.tar.xz > > The following 5 tests fail on s

Re: [GSoC] Javascript for info-style navigation

On Wed, Aug 23, 2017 at 05:25:03PM +0200, Mathieu Lirzin wrote: > Hello, > > Here is a report for week 12: > > http://mathieu.lirzin.emi.u-bordeaux.fr/2017/08/23/gsoc-2017-12/ > > Suggestions or comments are welcome. It's looking good; I had no problems using the online demos and it is

Re: texinfo.tex - part header in long table of contents

On Tue, Aug 22, 2017 at 10:50:34PM -0600, arn...@skeeve.com wrote: > Gavin Smith <gavinsmith0...@gmail.com> wrote: > > > On Tue, Aug 22, 2017 at 01:13:32PM -0600, arn...@skeeve.com wrote: > > > The main problem is that the the first line is outdented instead > >

Re: texinfo.tex - part header in long table of contents

On Tue, Aug 22, 2017 at 10:50:34PM -0600, arn...@skeeve.com wrote: > Gavin Smith <gavinsmith0...@gmail.com> wrote: > > > On Tue, Aug 22, 2017 at 01:13:32PM -0600, arn...@skeeve.com wrote: > > > The main problem is that the the first line is outdented instead > >

Re: makinfo (v 6.4): failure to support formats textcontent, rawtext, plaintexinfo

On Mon, Jul 31, 2017 at 06:59:53PM -0400, Randall Sawyer wrote: > Package Texinfo::Convert::Text (file Text.pm) contains this line: > > @ISA = qw(Exporter); > > which should be > > @ISA = qw(Exporter Texinfo::Convert::Converter); > > All of the other derived converter modules look complete.

texinfo-6.4.92 pretest

The pretest for the next release of Texinfo has been updated: https://alpha.gnu.org/gnu/texinfo/texinfo-6.4.92.tar.xz Changes since previous pretest: * Bug fixed that could lead to several tests of "info" failing. * "1 menu-digit" is supported in .infokey. * Attempt at getting the tests of

Re: `1 menu-digit' stopped working after upgrading to 6.x

On Thu, Aug 31, 2017 at 10:33:32AM +0800, Clark Wang wrote: > > Without `--vi-keys' I still get "Unknown command (1)" when I press `1'. > I don't know for certain why this happened, but I am guessing you had "#stop" in your .infokey file. I've made a change to the current code to support "1

Re: recent debian perl tests failures without . in @INC

On Thu, Aug 31, 2017 at 02:37:57PM +0200, Patrice Dumas wrote: > Another possibility could be to replace that line by a call to > ModulePath, like what is done in tests not depending on t/test_utils.pl, > like > > BEGIN { > require Texinfo::ModulePath; > Texinfo::ModulePath::init(undef,

Re: Broken links on https://www.gnu.org/software/texinfo/

Thank you for the report. On 22 Nov 2017 5:00 am, "Graham, Mark A" wrote: Hi, Two broken links on the Texinfo documentation page ( https://www.gnu.org/software/texinfo/) linking to the reference cards: ·

Re: prefer https over http

On Mon, Dec 11, 2017 at 10:37:37PM +0100, Bruno Haible wrote: > Hi Gavin, > > > I'll make this change and upload the new file. > > Here are more changes in the same spirit. And a few doc locations are > outdated; I could find the new location instead. > > > 2017-12-11 Bruno Haible

Re: error from pdfTeX with @var in exponent with the raw formatter command

On Sun, Dec 03, 2017 at 03:22:43PM +0100, Vincent Lefevre wrote: > Thanks. But I've noticed that the font size in exponent has changed. > In particular, this looks strange on: > > $-\int_{t=0}^{@var{op}} \log(1-t)/t\ dt$ > The change I made changed the font size in superscripts when it

Re: error from pdfTeX with @var in exponent with the raw formatter command

On Sun, Dec 03, 2017 at 03:22:43PM +0100, Vincent Lefevre wrote: > Thanks. But I've noticed that the font size in exponent has changed. > In particular, this looks strange on: > > $-\int_{t=0}^{@var{op}} \log(1-t)/t\ dt$ > Until a proper fix happens, if ever, a workaround is to use the TeX

Re: texinfo.tex problem formatting index

On Wed, Nov 15, 2017 at 09:54:06PM +0200, Arnold Robbins wrote: > Hi. > > I just saw a weird case where texinfo.tex put a blank page in > the middle of the index. To reproduce: > > git clone https://github.com/arnoldrobbins/prepinfo > cd prepinfo > make > > Look at the index

Re: texinfo.tex problem formatting index

On Thu, Nov 16, 2017 at 08:12:10PM +, Gavin Smith wrote: > I've committed a fix. I can't guarantee that it's right for all > circumstances as the implementation of the double-column index format is > a complex area. I've realised my fix is wrong and only appeared to work by ac

Re: wishlist: implicit anchor for @deffn etc

On Tue, Oct 31, 2017 at 02:18:29PM -0700, Per Bothner wrote: > An info format reader should ideally display such a link as plain NAME but > with some special > color or style to mark it as a link, but otherwise not clutter up the > display. If that is too > difficult, one just output plain NAME

Re: Updating contrib/prepinfo.awk

On Tue, Nov 07, 2017 at 09:58:49PM +0200, Arnold Robbins wrote: > I would just update the .awk file. I think I still have commit access > to the SVN repo, so I'll just do it directly, but I wanted to let > the maintainers know this is coming. OK fine, I can't see that it would do any harm.

Re: error from pdfTeX with @var in exponent with the raw formatter command

On Mon, Nov 27, 2017 at 09:52:58AM +0100, Vincent Lefevre wrote: > When @var is used in exponent with the raw formatter command, I get an > error in the PDF generation: > > @tex$2^{@var{foo}}$@end tex > > yields errors like > > ../../../.././mpfr.texi:2219: \scriptfont 5 is undefined (character

Re: prefer https over http

On 10 December 2017 at 15:43, Bruno Haible wrote: > Hi, > > The internet is moving from http:// URLs to https:// for a while already. > Therefore in HTML documentation generated from texinfo sources, I'd like to > have https:// URLs instead of http:// URLs where possible. > > In

Re: wishlist: implicit anchor for @deffn etc

On 30 October 2017 at 20:57, Per Bothner wrote: > Two related problems: > (1) It would be convenient to be able to easily reference a definition > without having to explicitly create an @anchor. For example: > > @deffn Procedure sqrt @var{z} > @end deffn > > The '@deffn

Re: Misleading Warning about Node Names

On Fri, Feb 9, 2018 at 12:15 PM, Rical Jasan wrote: > Hi, > > In the glibc manual, we have some @*refs to the GCC manual; e.g.: > > @xref{Debugging Options,, Options for Debugging Your Program or GCC, > gcc.info, Using GCC} > > When running `make info', there are the following warnings: > >

Re: Words together when translate menu

On Mon, May 28, 2018 at 1:43 AM, Jorge Maldonado Ventura wrote: > When we translate with `po4a-translate -f texinfo -m ./bashref.texi -p > ./bashref.es.po -l ./bashref.es.texi` on long lines from @menu some words > lose the separation space they had in the PO file. We're > using po4a-translate

Re: Wrong info file shown when filename has suffix

On Sat, May 12, 2018 at 7:13 PM, pelzflorian (Florian Pelz) wrote: > When I install an info file with the same filename prefix as an > existing installed info file up until the first period and then open > info and select it, then go back and select the other file, the wrong > file is shown.

Re: (texinfo) dfn - the double quotes around ``deleting'' are inconsistentwith (eintr) Complications ``variables''

On Mon, May 28, 2018 at 12:12 PM, Van L wrote: >> You are saying that the Texinfo manual uses ASCII quotes, and therefore >> the opening and closing quotes are identical? > > Yes. > >>> Hello. >>> >>> The beginning and ending double-quoting symbols are inconsistent for >>> >>> 1. (eintr)

Re: INFO Heap Crash

On Fri, Apr 13, 2018 at 7:26 AM, cabstand wrote: > On Ubuntu 16.04 TLS I have been injecting /dev/urandom data into > commands via bash. I consistently get heap crashes in info. > > It takes about 400M of regular user data to get the crash. To date I > have not isolated the random string section

Re: Infinite loop generating QEMU docs after upgrade to Perl 5.28.0

On Fri, Jun 29, 2018 at 6:46 AM, Melvin Mawhin wrote: > Also I attached the texi sources with a debug.sh script. just run the script > to reproduce the error Thank you for sending this; unfortunately I do not get the error.

Re: Infinite loop generating QEMU docs after upgrade to Perl 5.28.0

On Fri, Jun 29, 2018 at 7:41 AM, Eli Zaretskii wrote: >> From: Melvin Mawhin >> Date: Fri, 29 Jun 2018 05:46:29 + >> Cc: "bug-texinfo@gnu.org" >> >> Reading symbols from /usr/lib64/texinfo/XSParagraph.so...done. >> Reading symbols from /usr/lib64/perl5/auto/PerlIO/encoding/encoding.so...(no

Re: Infinite loop generating QEMU docs after upgrade to Perl 5.28.0

On Wed, Jun 27, 2018 at 1:46 PM, Melvin Mawhin wrote: > Since upgrading to perl 5.28 in slackware-current we ran into a bug while > generating documentation for qemu There is a message in the logs you attached: Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.32),

Re: Empty page index

On Sat, Jun 23, 2018 at 6:45 PM, Jorge Maldonado Ventura wrote: > Getting errors like: > > [194] Overfull \vbox (0.84181pt too high) has occurred while \output is > active > > Then an empty page appears. > > It also happens with GNU Bash documentation: > https://savannah.gnu.org/support/?109512

Re: Infinite loop generating QEMU docs after upgrade to Perl 5.28.0

On Fri, Jun 29, 2018 at 8:05 PM, Melvin Mawhin wrote: > I understand, I do not know where the problem lies. The Slackware maintainer > has decided to rebuild texinfo with the --disable-perl-xs flag. This solves > the immediate issue (workaround). > > > > Is there anything else I can test? I

Re: error from pdfTeX with @var in exponent with the raw formatter command

On Tue, Dec 19, 2017 at 03:35:01AM +0100, Vincent Lefevre wrote: > Not very bad with the abve example, but in > > {\log 2 \over \log \hbox{\switchtolllsize@var{b}}} > > this is worse. > I've made another attempt at adding support for @var in superscript in math mode.

Texinfo future plans

On 15 January 2018 at 17:43, Mathieu Lirzin wrote: > Sorry if I am opening a can of worm, but what about moving the main > development repository from Subversion to Git? :-) > > We could ask Eric Raymond to help with the migration if he has some time > for it. He has already

Re: stale git repository on Savannah?

On Fri, Jan 12, 2018 at 01:06:33PM -0800, Per Bothner wrote: > If I go to: https://savannah.gnu.org/projects/texinfo/ > and then click Source code -> Browse Source Repository > I get a git view that (except for the gsoc_2017 branch) doesn't > appear to have been changed since 2009. > > If I got

Re: Apparent bad choice in handling cross-references

On 30 January 2018 at 14:10, Richard Stallman wrote: > What do you think about this complaint? > Should we change the behavior of texinfo.tex about this? > > --- Start of forwarded message --- > On page 11 of the PDF version, in the last sentence of section 2.1, the >

Re: Book titles

On 31 January 2018 at 01:26, Richard Stallman wrote: > Could you change the @..ref constructs, for TeX and HTML output, > to put the name of the book into italics (when there is a book name)? I believe it already does. For example, in a cross-reference like "see User Input in The

Re: hyphenation

On Fri, Feb 09, 2018 at 09:06:16PM -0500, Richard Stallman wrote: > [[[ To any NSA and FBI agents reading my email: please consider]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > Please

Re: In an @example, @comment at EOL swallows the following newline.

On Sat, Dec 30, 2017 at 09:51:53AM +, Alan Mackenzie wrote: > Hello, texinfo. > > I'm using texinfo 6.3 on Gentoo GNU/Linux. > > I generated the file cc-mode.info using the command > > $ makeinfo cc-mode.texi > > . From the following source snippet: > > @example > @group > main (int,

Re: In an @example, @comment at EOL swallows the following newline.

On Mon, Jan 01, 2018 at 10:23:23PM +, Gavin Smith wrote: > There could be a case for changing makeinfo to be consistent with > texinfo.tex, provided we can work out what texinfo.tex is doing. > So I believe in texinfo.tex, it's impossible for a @c within a macro definition to co

Re: In an @example, @comment at EOL swallows the following newline.

On Mon, Jan 01, 2018 at 05:55:52PM +, Alan Mackenzie wrote: > The actual source in cc-mode.texi which showed up the bug was indeed in > a macro, namely: > > @macro hereFn{func} > <- @i{\func\}@c > @end macro > > . This macro was committed on 2003-05-12. The @c at EOL2 looks

Re: {every,even,odd}{head,foot}ing customization var doc

On Mon, Jul 16, 2018 at 10:44:02PM +, Karl Berry wrote: > Furthermore, it seems that specifying these config values even with > --pdf has no effect, e.g., the -c makes no difference to the output here: > makeinfo -c everyheading='lft@|ctr@|rt' --pdf hello.texi > (And I wouldn't expect this

Re: Memory leak in info man page fall back

On Thu, Jul 26, 2018 at 1:24 PM, Vitezslav Crhonek wrote: > Hi, > > This time a memory leak is within the 'get_initial_file' function > (info.c:175). Thank you for both of your reports; I've applied your fixes to the code base.

Re: recent debian perl tests failures without . in @INC

On Tue, Aug 29, 2017 at 10:48 AM, Patrice Dumas wrote: > Hello, > > Recent perl in debian do not have . in @INC anymore, and it will be > upstream in perl 5.26. > https://lists.debian.org/debian-devel-announce/2016/08/msg00013.html > > As a consequence some tests now fail, even with top_srcdir

Re: dead links in htmlxref.cnf

On Thu, Aug 23, 2018 at 11:52:53AM -0400, Ineiev wrote: > On Thu, Aug 23, 2018 at 08:13:17AM -0400, Ineiev wrote: > > > > http://ftp.gnu.org/gnu/texinfo/htmlxref.cnf (which is in sync with > > Texinfo SVN repository) has links for two absent manuals: gcj (dropped > > in GCC 7 release series [0])

Re: [bug #32416] rfe: convert from mediawiki to texinfo

On Sun, Aug 19, 2018 at 6:09 PM, Sergey Poznyakoff wrote: > Follow-up Comment #2, bug #32416 (project texinfo): > > Better late than never :) The first version is available: > https://pypi.org/project/wikitrans/#files Wow, awesome, I'll check this out when I get a chance.

Re: ePub support

On Sat, Jul 14, 2018 at 8:42 PM, Borden Rhodes wrote: > I noticed in the TODO file of texinfo that there's a job for exporting > into ePub. This would be a great feature because I've wanted to take > things like the bash and sed manuals offline to read with me. Have you tried downloading e.g.

Re: overfull lines with @url in @raggedright

On Mon, Jul 23, 2018 at 7:54 PM, Werner LEMBERG wrote: >> texinfo.tex is supposed to allow breaking at some characters but not >> the hyphen. I think breaking at "/" would be sufficient in the >> example you give. The problem is how to achieve this. I was thinking something like

Re: overfull lines with @url in @raggedright

On Mon, Jul 23, 2018 at 11:55 AM, Werner LEMBERG wrote: > shows that @url in @raggedright environments would need some > improvements. The output looks the same whether it is in @raggedright or not, so it seems that it needs improvement in both cases. > What about adding code to support

Re: Paragraph filling in texi2any

On Sat, Sep 01, 2018 at 03:23:46AM +0300, Bad Blue Bull wrote: >   27.08.2018, 19:27, "Gavin Smith" > gavinsmith0...@gmail.com: type="cite">On Mon, 27 Aug 2018, 15:51 Bad Blue Bull, href="mailto:ibmb...@yandex.ru;>ibmb...@yandex.ru > wrote:Hi, can someon

Re: ampersand issue with texi2dvi

On Wed, Sep 05, 2018 at 06:27:53PM +0200, Heiko Stamer wrote: > Dear texinfo developers, > > I run into an issue with texi2dvi (see attached example file) that > results in the following error messages: > > $ texi2dvi libTMCG_bug.texi > This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live

Re: ampersand issue with texi2dvi

On Thu, Sep 06, 2018 at 08:46:57PM +0100, Gavin Smith wrote: > > If we can distinguish & followed by a letter from everything else, > > this problem can be fixed, I think. > > perhaps there could be some preprocessing of an entire @def line at once > to repla

Re: Infinite loop generating QEMU docs after upgrade to Perl 5.28.0

On Sat, Jun 30, 2018 at 7:27 PM, Niko Tyni wrote: > I'm attaching a patch that fixes this for me, and another one for the > necessary left brace escaping. Even with this, I suppose xspara.c could > use some mbrtowc(3) return value checks. Thanks for fixing this.

Re: user-defined html in navigation header/footer?

On Mon, Jul 9, 2018 at 5:55 PM, Karl Berry wrote: > Hi Gavin and all - I suggest it would be useful to support a > user-defined navigation "button" that would appear next to [Contents] > xand [Index]. (If it's already possible, please let me know. I couldn't > find it in the doc or souces.) > >

Re: install-info --remove Leaves "dir" Unmodified

On Thu, Jul 12, 2018 at 4:16 AM, Paul Hardy wrote: > I looked at message subjects on this list from the past two years but > this does not seem to have been reported before. > > After successfully installing a Texinfo page in /usr/local/share/info > with install-info, with the "dir" info

Re: Makeinfo hangs on compiling Emacs 26.1 with texinfo 6.5, perl 5.28

On Fri, Jul 13, 2018 at 4:46 AM, wrote: > As the subject states, 'makeinfo' hangs on making elisp.info with Perl > 5.28,Texinfo 6.5. It never completes its task, no matter how long you wait. > I apologize for not having more info, but I am unskilled in Perl, and do not > know how to debug it. >

Re: When should we put @key inside @kbd?

On 6 March 2018 at 20:53, Richard Stallman wrote: > > What about a text like "Type @key{TAB} or @kbd{M-@key{TAB}}."? The > > former TAB would be unslanted, the latter slanted. It looks > > inconsistent, I would say. > > This is a miscommunication. > > Eli argued for making

Re: Possible improvement in Texinfo

On 4 March 2018 at 11:31, Richard Stallman wrote: > He was surprised, looking at a PDF file, that only the page numbers in > the table of contents were links to the chapters themselves. > > Could you make the whole title mouse-sensitive in the way he > expected? It should be

Re: @code{} inside of @math{}

On 6 March 2018 at 11:50, Hefferon, James S. wrote: > 1) If I use @math{... @code{} ...} then the HTML output does not show the > @code{} output in monospace; it is instead in italics. This can be fixed > with a line of CSS. > I run: makeinfo --html mathtest. The HTML

Re: please use before-save-hook instead of write-file-hooks

On 8 March 2018 at 00:34, Paul Eggert wrote: > The write-file-hooks feature of Emacs has been declared obsolescent since > Emacs 22.1 (2007), so it's time to use this feature's suggested replacement > in the Texinfo files that use the feature. For more details, please see this

Re: @code{} inside of @math{}

On 9 March 2018 at 22:14, Hefferon, James S. wrote: > > OK, I find that in looking at the archive for this list is says > > @address@hidden@code{bbb}} > > where my mailing system says I mailed > > @math{@code{aaa}+@code{bbb}} Don't worry about that, your mail got through

Re: Infinite loop generating QEMU docs after upgrade to Perl 5.28.0

On Wed, Jun 27, 2018 at 1:46 PM, Melvin Mawhin wrote: > Since upgrading to perl 5.28 in slackware-current we ran into a bug while > generating documentation for qemu > > The version number of Texinfo and the program(s) or manual(s) involved. > Texinfo 6.5 / Qemu 2.12.0 (docs) / Perl 5.28.0 > The

Re: Infinite loop generating QEMU docs after upgrade to Perl 5.28.0

On Thu, Jun 28, 2018 at 6:28 AM, Melvin Mawhin wrote: > Hi, > > > Same thing, the error message concerning the bracket is gone but the loop > is still there. > > > but as said before, changing the makefile like this does seem to solve the > issue: > > sed -i "s|LC_ALL=C|LC_ALL=C.UTF-8|" Makefile

Re: BROKEN: link on texinfo help page

On Thu, Oct 11, 2018 at 4:47 PM Charlie Eddy wrote: > > Hello GNU person, > > http://www2.linuxjournal.com/lj-issues/issue6/2840.html > this is broken. > https://www.linuxjournal.com/article/2840 > AFAIU this is correct. Thank you for the report, it should be fixed soon at

Re: Stand-alone release of Texinfo JS Interface?

On Tue, Oct 23, 2018 at 04:15:10PM -0700, Per Bothner wrote: > >I've added a script ("texinfo-js") to add the interface for any > >Texinfo manual > > I didn't see any such script in the svn source. There is a texinfo-js > (short) manual. I'd called the script something else but it is called

Stand-alone release of Texinfo JS Interface?

I think we should make a release of the work done to create an info-style browsing experience in HTML, by Mathieu Lirzin in 2017 as part of "Google Summer of Code". This would be separate to the main Texinfo releases. "Texinfo JS Interface" seems like a good name. Any other suggestions? I've

pretest texinfo-js-0.0.90 available

The pretest for the initial release of the Texinfo JS Interface has been uploaded to: https://alpha.gnu.org/gnu/texinfo/texinfo-js-0.0.90.tar.gz The purpose of this system is to provide an Info-like interface for reading documentation in a web browser. You can see a sample here:

Re: pretest texinfo-js-0.0.90 available

On Sat, Oct 27, 2018 at 02:27:07PM +0300, Eli Zaretskii wrote: > Thanks. Does this require anything special from the browser used to > read the resulting HTML files? Or would any Web browser do? E.g., > will Emacs's EWW do? It needs to support JavaScript, and various modern features of

Re: Adding info.vim to list of Info readers?

On Fri, Sep 28, 2018 at 01:59:53PM +0200, HiPhish wrote: > The web page for Texinfo lists two alternative readers (pinfo and tkinfo), > and > I suggest adding info.vim[1] to that list as well. Full disclosure: I am the > author of that Vim plugin and I have been using and working on it for

Re: Build fails in 'tp/tests': missing tests-parser.txt

On Tue, Sep 25, 2018 at 07:57:52PM +0200, Hans-Bernhard Bröker wrote: > Hello everyone, > > Since roughly last week, the build of SVN texinfo fails in the tp/tests > subproject, like this: > > $ LC_ALL=C make > make: *** No rule to make target 'formatting/tests-parser.txt', needed by >

Re: texi2dvi error on -recoder and \openout

On Thu, Sep 20, 2018 at 06:35:30PM +0100, Gavin Smith wrote: > Maybe the error message is misleading -- if there is no working TeX > program, texi2dvi should just say so instead of talking about -recorder > etc. which few people will have a clue about. With Texinfo 5.2: $ TEX=foo .

Re: ampersand issue with texi2dvi

On Sat, Sep 08, 2018 at 04:10:05PM +0200, Werner LEMBERG wrote: > >> It is possible, but I am not sure if it is worth it. There is too > >> much difficult-to-understand macro trickery in texinfo.tex > >> already. My favourite solution at the moment is to introduce a > >> Texinfo command @& to

Re: Bug - Warnings with newer Perl versions ("Unescaped left brace in regex is deprecated here")

On Sat, Sep 22, 2018 at 09:26:13PM +0300, kurko2...@gmail.com wrote: > This was originally noticed with Octave when using the help command, or > when entering a command with invalid or missing arguments. > > Warnings like this appear before the actual command output begins: > > Unescaped left

Re: texi2dvi error on -recoder and \openout

On Thu, Sep 20, 2018 at 05:48:19PM +0200, Mohammad Akhlaghi wrote: > make[1]: Entering directory '/home/myid/work/tmp/gnuastro-0.7/doc' > TEXINPUTS="../bootstrapped/build-aux:$TEXINPUTS" \ > MAKEINFO='/bin/bash > /home/myid/work/tmp/gnuastro-0.7/bootstrapped/build-aux/missing makeinfo -I >

Re: [help-texinfo] in multi-node HTML

On Sun, Nov 11, 2018 at 06:41:02PM +0100, Akim Demaille wrote: > The HTML reads: > > Understanding (Bison 3.2.1) > > Is there a means to use the section name rather that the node name in the > generated HTML? It???s quite common to have a very short node name, but a > fully blown section

<    3   4   5   6   7   8   9   10   11   12   >