Hi.
Using version 2023-10-19.19 of texinfo.tex, there is a problem if
a table inside @float goes over one page. See the attached file.
If the table is not inside @float, it formats just fine across
multiple pages.
This example is culled from a book I'm working on. I need the @float
in order to
Hi.
> http://www.docbook.org/tdg/en/html/index.html
>
> Parents
>
> These elements contain index: appendix, article, book, chapter, part,
> preface, sect1, sect2, sect3, sect4, sect5, section.
>
> is in the list so what is the problem?
>
> Is that page I linked to out-of-date? The date there is
Hi.
I agree that there's an impedance mismatch here between Texinfo
and DocBook. That makes it harder to deal with than I would like, too.
I really DON'T enjoy making the lives of the Texinfo maintainers
miserable... :-( (Yes Karl, I hear you snorting in the back there... :-)
> On 6 April 2016
I've updated the various relevant bits and pieces and pushed to Github.
Thanks,
Arnold
> Date: Sat, 20 Feb 2016 07:40:49 +
> Subject: Fwd: texindex's compiler's docs non-free
> From: Gavin Smith <gavinsmith0...@gmail.com>
> To: Aharon Robbins <arn...@skeeve.com>
&g
hen and the < sign?
Thanks,
Arnold
> Date: Thu, 8 Oct 2015 21:08:11 +0100
> Subject: Re: texinfo 6.0 texindex problem?
> From: Gavin Smith <gavinsmith0...@gmail.com>
> To: Aharon Robbins <arn...@skeeve.com>
> Cc: Texinfo <bug-texinfo@gnu.org>
>
> On 8 October 201
Hi.
Just to confirm that using the current texinfo.tex everything is fine
again. Much thanks for the help.
Arnold
Hi.
> > I think that not removing the last end of line of raw blocks would
> > probably be better, but some manuals may expect the end of line to be
> > removed. So, there is an issue of backward compatibility here.
>
> Seen in the sources of the gawk manual:
>
> @ignore
> Some comments on the
Hi.
The current texinfo.tex does not work anymore with the gawk doc. It
can be reproduced easily as follows:
wget http://ftp.gnu.org/gnu/gawk/gawk-4.1.3.tar.gz
tar -xpzvf gawk-4.1.3.tar.gz
cd gawk
./configure && make
cd doc
cp /path/to/texinfo.tex
Much thanks for the explanation and fixes. I'll try them out.
I probably won't get to this for another few days though.
Arnold
Hi.
It seems that current makeinfo --docbook just strips off the markup
for @sc{...}.
There doesn't seem to be docbook markup for small caps, so I would
suggest that it'd be better to upcase the contents of @sc{}. That
way something like
the ASCII @sc{nul} character
comes out as
Hi.
On Mon, May 12, 2014 at 10:38:18PM +0200, Patrice Dumas wrote:
On Mon, May 12, 2014 at 09:05:04PM +0300, Aharon Robbins wrote:
After a fresh checkout of the SVN trunk, autogen, configure and make,
the build dies with:
Undefined subroutine Texinfo::Structuring
Hi Karl.
We're still disagreeing, but on a more subtle point.
Not really - the translator should handle it.
I don't agree. It's the same principle that you already stated: you're
saying that Texinfo should support partintro for Docbook, but we're
saying that since it's not supported
Hi Karl.
2. For all current features of the Texinfo language, the docbook output
generated by makeinfo should be valid docbook. I think we all agree
on this as a principle.
Agreed.
If we accept this, then for makeinfo --docbook, any text
following @part
Hi Karl.
I'm sorry, but what you want for @part is something completely different
than what I intended. Oddly enough, I implemented what I intended :),
which was essentially just standalone part pages that bear no
relationship to the rest of the document.
OK. We have a bad confluence of
Hi Karl and Patrice.
How about:
@part Part Title
@docbook
partintrointro to part blah blah/partintro
@end docbook
Does that work? That seems to me to best reflect the reality of the
situation, which is that partintro text is a Docbook feature, not
supported in Texinfo.
It probably
Hi Karl et al,
Using latest gendocs from gnulib, I'm getting:
...
Generating monolithic html... (env LANG= LC_MESSAGES= LC_ALL= LANGUAGE=
makeinfo --no-split --html -o gawk.html /tmp/gawk-4.1.1/doc/gawk.texi)
gendocs.sh: gawk.html: cannot find image general-program.png
END failed--call
Hi Patrice.
Me:
Right now if I use @docbook, I'm getting:
part
introductory blah blah here
/section these are from what came before the part
/preface
chapter ...
/part
Patrice:
That looks like a bug, the DocBook produced does not
Hi.
The @part command is somewhat mismatched with how docbook works. In
particular, parts include chapters, so for correct generation of the
docbook tags, we should really have
@part label
@parttitle Title Of The Part Here
@chapter ...
@chapter ...
@end
Hi Karl.
So, Texinfo @parts do not map to Docbook. Not surprising. Such is
life. To get parts in your Docbook output, all I can think of is the
useless hack it in by hand approach (e.g., throw comments into the
source and post-process them to create the necessary part/related
elements).
Hi Karl.
Current makeinfo when processing @docbook ... @end docbook leaves off
the trailing newline.
I can't tell you how much hassle that the trailing newline before @end is.
In some cases it is absolutely neeeded. In other cases it absolutely
needs to be ignored. I see no way to
Hi.
Current makeinfo when processing @docbook ... @end docbook leaves off
the trailing newline. For example:
@docbook
emphasissim; Cnsuperscript2/superscript/emphasisthinsp;
@end docbook
peformance, while
This is wrong. I have to add the thinsp; at the end so
Hi All.
The -o option in texindex.c is fundamentally broken. The arg_index
variable has already been incremented upon entry to the relevant bit of
code; it should be incremented again at the end. The diff below fixes it.
It is not clear how this option is meant to be used. From the code it
looks
The fact that no-one has reported this bug for who knows how many
years would seem to argue that it isn't used.
Agreed.
I suggest simply nuking it.
Agreed. Your reimplementation can just skip it :).
Thanks. Done.
Next question. Can I use { and } hard-wired? At the moment
Much thanks. I'll update my copy.
Arnold
Date: Sun, 9 Feb 2014 23:58:24 GMT
From: k...@freefriends.org (Karl Berry)
To: arn...@skeeve.com
Cc: bug-texinfo@gnu.org
Subject: Re: texinfo.tex: @cartouche kills indentation
In the current texinfo.tex, if you wrap stuff in @cartouche,
Hi.
As a hypothetical question, if I rewrote texindex in awk and it
functioned as a drop-in replacement, would you take it?
I don't see why not. It would surely be easier to maintain.
If you go that route, one thing I would really like to do is change the
.?? index files to use @
Hi Karl.
Hi Arnold,
@cindex main topic, secondary point, tertiary point
...
indextermprimarymain topic/primarysecondarysecondary
point/secondarytertiarytertiary
point/tertiary/secondary/primary/indexterm
Well, as you know, support for the usual index features has
Hi.
It's me again.
The last time I converted a book from Texinfo to Docbook for book
production, I enhanced the C makeinfo to use commas in @cindex to
separate the primary, secondary, and tertiary terms in an index entry.
There could be up to two commas, leading to three cases:
@cindex
Hi.
A real bug. @math{whatever} is getting turned into
inlineequationmathphrasewhatever/mathphrase/inlineequation
The problem is that the mathphrase tag appears to no longer be valid
docbook. Xmllint chokes on it on my Ubuntu 12.04 system.
Thanks,
Arnold
Hi Karl.
Thanks for the explanations.
Arnold
Date: Fri, 31 Jan 2014 22:09:28 GMT
From: k...@freefriends.org (Karl Berry)
To: arn...@skeeve.com
Cc: bug-texinfo@gnu.org
Subject: Re: texinfo macro names don't allow digits
Hi Arnold,
I admit to not checking, but if this isn't
[ PLEASE cc me on all replies, as I'm not subscribed to this group. ]
Hello all.
It looks like I'm going to need to exercise the conversion of Texinfo
to docbook, so you can expect to start hearing from me. :-)
The first issue has to do with nesting. Texinfo, like TeX, is quite
general about
Hi. Something like
@cindex @r{@{foo@}} program
Which should be indexed under { ends up being indexed under |
This is with the latest SVN version of texinfo.tex, and also earlier ones.
Thanks,
Arnold
Hi Karl.
Is it a bug or a feature that the Texinfo 5.2 tarball extracts with
directories being world writable?
Feature. Well, at least it's intentional.
Anyone who cares should set umask before unpacking, as usual.
Seems to me.
Something's messed up somewhere. Ubuntu 12.04:
Just to close the loop...
Date: Tue, 16 Apr 2013 22:24:54 +0300
From: Eli Zaretskii e...@gnu.org
Subject: Re: out of directory formats?
To: Aharon Robbins arn...@skeeve.com
Cc: bug-texinfo@gnu.org
From: Aharon Robbins arn...@skeeve.com
Date: Tue, 16 Apr 2013 22:06:36 +0300
If I
Hi Karl.
Separate from what you're actually reporting ...
@c FIXME: One day, it should not be necessary to have two cases,
@c but rather just the one without the txt final argument.
I remember talking about this with you before, but not what the
conclusion was (as
Hi Karl.
Arnold,
I just updated texinfo.tex
(http://ftpmirror.gnu.org/texinfo/texinfo.tex, etc.) so that
multiple-line @titles work. They're broken automatically if needed, or
you can use @* to choose the breakpoints.
Excellent. Works like a charm!
Thank you for the quick response. I
Hi Eli.
Long time ago, I had the same problem, and solved it thusly:
@titlepage
@titlefont{GNU Software for MS-Windows,}
@sp 1
@title MS-DOS, and Compatible Systems
@subtitle Edition @value{edition}
@author by Daniel Hagerty, Melissa Weisshaus
@author and Eli Zaretskii
36 matches
Mail list logo
