Texinfo.tex, problem with too-long table inside @float
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 be able to use an @ref to the table from the inline prose. Much thanks! Arnold float-problem.texi Description: TeXInfo document
Re: makeinfo --docbook bug with index
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 2002; if it's > no longer valid is there another reference I can refer to? Grrr. I just figured this out. :-) If we have: tail: cannot open '*.xml' for reading: No such file or directory Index ---> It becomes valid. I use xmllint --noout --postvalid --xinclude to validate docbook. You have to look closely at what it's telling you, which I didn't before. Thanks, Arnold
Re: makeinfo --docbook bug with index
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 at 22:00, Karl Berry wrote: > > > > > > How can it be correct to omit output from the @node and @unnumbered? If I wrapped them in @ifnotdocbook ... :-) > > Docbook cannot know the name I want to give to my index. And the whole > > node tree would be screwed up. And what if there is other text in the > > node besides the @printindex? I don't get it. Not that it's my > > business any more ... -k > > That's exactly what I thought. > > > @node Concept Index > @unnumbered Index > > a > > @printindex cp > > b > > @bye > > What should the output be? Three separate chapters? Beats me. I understand the issue. > Does invalid DocBook output cause problems with validation? Yes. The comes out inside a chapter and the docbook doesn't validate. > Would it be better to remove the output completely and have no > output for an index? Most likely. The needs to be after the previous closing tag and I don't see any way to force that. I can think of something ugly like: @ifnotdocbook @node Concept Index @unnumbered Index @printindex cp @end ifnotdocbook @ifdocbook @bookcontentdone @c flush out chapters and appendices @printindex cp @end ifdocbook @bye Hmm... That's almost reasonable. :-) Thanks, Arnold
Re: Fwd: texindex's compiler's docs non-free
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 > To: Aharon Robbins > Content-Type: text/plain; charset=UTF-8 > > Forwarded because I don't know if you've read it. > > -- Forwarded message -- > From: Norbert Preining > Date: 20 February 2016 at 00:43 > Subject: Re: texindex's compiler's docs non-free > To: Gavin Smith > Cc: csh , Texinfo > > Hi Gavin, > > On Fri, 19 Feb 2016, Gavin Smith wrote: > > Attention all: the software author (Arnold Robbins) has moved all of > > the sources under the GPL, so it's a moot point now. > > > > https://github.com/arnoldrobbins/texiwebjr/blob/master/README > > Good to hear. Thanks. Maybe the LICENSE statement can be changed, too? > It still says:: > The explanatory prose and text in texiwebjr.twjr are Copyright (C) 2013, > 2014 > by Arnold David Robbins. All rights reserved. Verbatim copying is > permitted but it may not be otherwise modified. > > Norbert > > > PREINING, Norbert http://www.preining.info > JAIST, Japan TeX Live & Debian Developer > GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 >
Re: texinfo 6.0 texindex problem?
Hi. THanks for the mail. I moved to current development code for
texindex and braces are working. I note that hyphens and < signs
also get removed from the key for the index. Is that on purpose?
I can go ahead and add @sortas, but I'm wondering if I need to do
that also for the hyphen and the < sign?
Thanks,
Arnold
> Date: Thu, 8 Oct 2015 21:08:11 +0100
> Subject: Re: texinfo 6.0 texindex problem?
> From: Gavin Smith
> To: Aharon Robbins
> Cc: Texinfo
>
> On 8 October 2015 at 20:06, Aharon Robbins wrote:
> > Hi.
> >
> > I added
> >
> > @tex
> > \global\usebracesinindexestrue
> > @end tex
> >
> > to gawktexi.in in the gawk dist and built a pdf with the tools from
> > texinfo 6.0. Something's weird. First, there is no initial for \.
> > Second, braces come out under backslash.
> >
> > Did I do something wrong? Index files attached.
> >
> > Thanks,
> >
> > Arnold
>
> It appears that the texinfo.tex version from Texinfo 6.0 is not the
> one that's being used here, but one more recent. However, the version
> of texindex being used likely is the one from Texinfo 6.0. If you used
> the current development version of texindex (or possibly the texindex
> from an earlier release than 6.0), then I expect the braces coming out
> under backslash problem would be resolved.
>
> The lack of initial for \ is expected. This is due to a change in
> index sorting where backslash is ignored for the purposes of
> generating a sort key, along with a few non-alphabetic characters. So
> many manuals have indexed items starting with a backslash that are
> better indexed under a letter following the backslash (an example from
> Texinfo's manual is \mathopsup, better indexed under "M"). Admittedly,
> sometimes a backslash on it's own is indexed (I see the gawk manual
> has many occurrences of this), but this is likely the rarer case.
> There is a new syntax for specifying an explicit sort key that was
> introduced after the Texinfo 6.0 release. It looks like
>
> @cindex @sortas{\ escape sequence} \ (backslash), escape sequence
>
> Here "\ (backslash), escape sequence" is the text that will be output
> in the index, and "\ escape sequence" is the sort key.
>
Re: Inconsistent space after raw regions
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 layout for TeX. > 1. Use at least texinfo.tex 2014-01-30.15 > 2. When using @docbook, if the last line is part of a paragraph, end > it with a space and @c so that the lines won't run together. This is a > quirk of the language / makeinfo, and isn't going to change. > @end ignore > > One "data point" of the current meaning being a problem. I think this is using the gawk doc as evidence for a proposed change, whereby the workaround cited above would not be necessary. This sounds positive. If it happens, I can change the gawk doc. I suspect that I may be the only one who's really stumbled across this, anyway. So I'm OK with this change, as long as someone tells me about it once it happens. :-) Thanks! Arnold
Re: Current texinfo.tex breaks gawk doc
Hi. Just to confirm that using the current texinfo.tex everything is fine again. Much thanks for the help. Arnold
Re: Current texinfo.tex breaks gawk doc
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
Current texinfo.tex breaks gawk doc
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 .
make gawk.pdf
I have attached the result of 'make pdf' for your review; it looks like
a macro inside a multitable is throwing things off. This has worked
for a long time.
Please fix. :-)
Thanks,
Arnold
P.S. Please cc me on replies; I'm not subscribed to bug-texinfo. Thanks.
TEXINPUTS=".:$TEXINPUTS" \
MAKEINFO='/bin/bash /tmp/gawk-4.1.3/missing makeinfo --no-split --force
-I .' \
texi2dvi --pdf --batch --build-dir=gawk.t2p -o gawk.pdf \
gawk.texi
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
restricted \write18 enabled.
entering extended mode
(/tmp/gawk-4.1.3/doc/./gawk.texi (/tmp/gawk-4.1.3/doc/texinfo.tex
Loading texinfo [version 2015-09-23.01]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.) [1{/var/lib/t
exmf/fonts/map/pdftex/updmap/pdftex.map}] [2] [3] [4]
Overfull \hbox (11.92378pt too wide) detected at line 400
@textit To my wife, Miriam, for making me complete.Thank you for building your
life together with me.
Overfull \hbox (32.22017pt too wide) detected at line 402
@textit To our children, Chana, Rivka, Nachum, and Malka, for enrichening our
lives in innumerable ways.
[1] [2] (./gawk.toc
Underfull \hbox (badness 1) in paragraph at lines 12--12
@defbf guage
Underfull \hbox (badness 1) in paragraph at lines 201--201
@shortconttt awk[]
Underfull \hbox (badness 1) in paragraph at lines 250--250
[] @defbf Part III: Mov-ing Be-yond Stan-dard @shortconttt awk[] @defbf with @s
hortconttt gawk[]
Underfull \hbox (badness 1) in paragraph at lines 359--359
@defbf dices
) [-1] [-2] (./gawk.toc
Underfull \hbox (badness 1) in paragraph at lines 12--12
@secrm guage
[-3] [-4] [-5] [-6]
Underfull \hbox (badness 1) in paragraph at lines 201--201
@sectt awk[]
[-7] [-8] [-9] [-10]
Underfull \hbox (badness 1) in paragraph at lines 359--359
@secrm dices
[-11]) [-12] (./gawk.toc) (./gawk.toc) (Foreword to the Third Edition)
(./gawk.aux) [1] (Foreword to the Fourth Edition) [2] (Preface) [3] [4]
[5] [6] [7] [8] l.1762: Undefined cross reference `Notes-snt'.
l.1762: Undefined cross reference `Notes-snt'.
l.1762: Undefined cross reference `Notes-title'.
l.1762: Undefined cross reference `Notes-pg'.
l.1768: Undefined cross reference `Basic Concepts-snt'.
l.1768: Undefined cross reference `Basic Concepts-snt'.
l.1768: Undefined cross reference `Basic Concepts-title'.
l.1768: Undefined cross reference `Basic Concepts-pg'.
l.1772: Undefined cross reference `Glossary-snt'.
l.1772: Undefined cross reference `Glossary-snt'.
l.1772: Undefined cross reference `Glossary-title'.
l.1772: Undefined cross reference `Glossary-pg'.
l.1777: Undefined cross reference `Copying-snt'.
l.1777: Undefined cross reference `Copying-snt'.
l.1777: Undefined cross reference `Copying-title'.
l.1777: Undefined cross reference `Copying-pg'.
l.1778: Undefined cross reference `GNU Free Documentation License-snt'.
l.1778: Undefined cross reference `GNU Free Documentation License-snt'.
l.1778: Undefined cross reference `GNU Free Documentation License-title'.
l.1778: Undefined cross reference `GNU Free Documentation License-pg'.
l.1: Undefined cross reference `@gobblespaces Other Versions-snt'.
l.1: Undefined cross reference `@gobblespaces Other Versions-snt'.
l.1: Undefined cross reference `@gobblespaces Other Versions-title'.
l.1: Undefined cross reference `@gobblespaces Other Versions-pg'. [9]
l.1972: Undefined cross reference `Copying-snt'.
l.1972: Undefined cross reference `Copying-snt'.
l.1972: Undefined cross reference `Copying-title'.
l.1972: Undefined cross reference `Copying-pg'.
l.1997: Undefined cross reference `Glossary-snt'.
l.1997: Undefined cross reference `Glossary-snt'.
l.1997: Undefined cross reference `Glossary-title'.
l.1997: Undefined cross reference `Glossary-pg'.
l.2008: Undefined cross reference `GNU Free Documentation License-snt'.
l.2008: Undefined cross reference `GNU Free Documentation License-snt'.
l.2008: Undefined cross reference `GNU Free Documentation License-title'.
l.2008: Undefined cross reference `GNU Free Documentation License-pg'. [10]
[11] [12] [13] [14] [15] [16] [17] [18] Chapter 1 [19] [20] [21] [22] [23]
[24] [25] [26] [27] [28] [29] [30]
l.3615: Undefined cross reference `Glossary-snt'.
l.3615: Undefined cross reference `Glossary-snt'.
l.3615: Undefined cross reference `Glossary-title'.
l.3615: Undefined cross reference `Glossary-pg
makeinfo --docbook and @sc
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
the ASCII NUL character
instead of
the ASCII nul character
I can work around this for the moment, but I thought I'd mention it.
Much thanks!
Arnold
Re: can't make current SVN trunk
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::warn_non_empty_parts called > > > at ../tp/texi2any line 1272. > > > > A possible fix would be, when calling texi2any (and not texi2any.pl), to > > try the directory relative to @datadir@ last in the search path. > > This should be fixed in svn. Thanks for the report! It's working great! Much thanks for the help! Arnold
can't make current SVN trunk
After a fresh checkout of the SVN trunk, autogen, configure and make, the build dies with: Undefined subroutine &Texinfo::Structuring::warn_non_empty_parts called at ../tp/texi2any line 1272. I was hoping to try out the fixes for @part... :-) Thanks, Arnold
Re: @part command and docbook
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 for Docbook, but we're > saying that since it's not supported for any other format, that is not, > in theory, what we'd like. I think you've not understood what I meant. I am saying that Texinfo, *at the markup level*, should not have commands that are of benefit only to Docbook. E.g., @sidebar. However, for commands already in the markup language, AND for which makeinfo is already generating Docbook, my contention is that it should be generating docbook that is valid. Were it true that @part was not already in the markup language, and not already supported by makeinfo, you would have a stronger case to say that makeinfo should not be supporting , or even supporting . But I think that at this point, where de facto both things are already there, the translator should be supporting . Let's pretend that for @section, makeinfo was generating incorrect docbook, and a tag was needed, that makeinfo didn't generate. Would you still argue that makeinfo should not be enhanced to produce the right output? That's the exact situation right now with @part. > In the specific case of I'm willing to make an exception > since it is easy to do (right, Patrice?) and basically harmless given > the warning for other output formats. But that doesn't alter the > principle. > > What if goes away > in some subsequent docbook revision? > > In my view, that is docbook's (and docbook users') problem. What if HTML suddenly changes and some tags go away, or are added? Is that HTML's and HTML users' problems? > - I am opposed (in principle) to continually tweaking things in Texinfo > that only benefit Docbook output. Like the full-on part feature in all > its glory. Again - as long as you're talking AT THE MARKUP LEVEL, I agree with you. But, if makeinfo is not generating valid docbook, that's a bug, exactly the same as makeinfo not generating valid HTML, or LaTeX (if and when) or Info that an Info reader can't read. > That doesn't mean that, in practice, I'm not amenable to the > occasional exception, like . Which I do appreciate. :-) Thanks, Arnold
Re: @part command and docbook
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 and preceding the first @chapter should be >wrapped in tags, and Patrice should fix this. > >I am fine for makeinfo to issue a warning about such text if not >in docbook mode. > >Karl, do you approve this docbook-specific fix? > > I guess I'm ok with both parts of this (the and the > non-docbook warning), Much thanks. I will try in the future to stick to real bugs w.r.t. docbook generation. > but ... > > wrapping tags in @docbook works > > .. that actually seems cleaner to me. Not really - the translator should handle it. What if goes away in some subsequent docbook revision? Such things have been known to happen. > Thanks, and sorry to be such a curmudgeon about it all. It's OK. Welcome to the curmudgeon club. (Can we get our own mascot? Maybe an aging GNU with a cane. :-) I think we all have our whiny users; I just hope that I'm on the low end of the "whiny" scale. :-) Thanks, Arnold
Re: @part command and docbook
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 names. > (Aside: in general, I can't see how you're *ever* going to get the exact > output you want, in every detail, through two different markup systems, > each with their own crazy limitations. When I want to control my > output, which I very often do, I use TeX directly ... screw everything > else. Oh well. I know O'Reilly doesn't believe in TeX.) The languages are are not all that far apart, actually. What I want is valid docbook. (Well, there are times when I want to control my output, but that's not the main issue here.) OK. Let's retrench a bit. There are two orthogonal issues. 1. Karl is opposed to continued stretching of the language, including texinfo.tex, to provide features that map directly to Docbook but are of little or no value to TeX/HMTL/Info. Examples are full-fledged "part" pages and sidebars. (And better indexing, to be complete. :-) So, I finally get this and will do my best to stop asking for such. 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. If we accept this, then for makeinfo --docbook, any text following @part and preceding the first @chapter should be wrapped in tags, and Patrice should fix this. I am fine for makeinfo to issue a warning about such text if not in docbook mode. Karl, do you approve this docbook-specific fix? wrapping tags in @docbook works, and I will do that for now so that I won't be blocked. But given #2, I would hope that it will be fixed in makeinfo. The other stuff I need/want I'll either make do with macros (not Karl's favorite thing, but it's my book, not his) or with pre- and post-processing scripts. Thanks, Arnold
Re: @part command and docbook
Hi Karl and Patrice.
> How about:
>
> @part Part Title
> @docbook
> intro to part blah blah
> @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 works, but it means I have to write all the
text in docbook instead of in Texinfo. I tried various bits
with @inlinefmt but then the got wrapped inside
tags and that was totally wrong.
I have been using @ifdocbook. Right now I have to conditionalize
it anyway, since texinfo.tex doesn't supply the "Part I". It looks
like this at the moment:
--
@iftex
@part Part I:@* The @command{awk} Language
@end iftex
@ifdocbook
@part The @command{awk} Language
Part I describes the @command{awk} language and @command{gawk} program
in detail. It starts with the basics, and continues through all of
the features of @command{awk}. Included also are many, but not all,
of the features of @command{gawk}. This part contains the
following chapters:
@itemize @bullet
@item
@ref{Getting Started}.
.
@end itemize
@end ifdocbook
@node Getting Started
@chapter Getting Started with @command{awk}
--
Is it reasonable to require that text after @part and before @chapter be
wrapped in @ifdocbook and then makeinfo can supply the tags?
W.R.T. to TeX, it'd be better if texinfo.tex didn't issue the page
break until the @chapter, and then text after an @part would work there.
(It'd also be nice if it would supply the "Part I", "Part II", and so
on, but that could be worked around with, gasp, macros.) It seems like
Info is the main hassle here. Not sure what to do about that, although
perhaps we could instead require that @part and following text simply
be wrapped in @ifnotinfo.
Overall, it'd be nice to have this feature instead of having to hack it
with scripts. But OTOH, I don't want to be to become (too much of) a whiny
user. :-)
So, here's my proposal / wish list, but I'll live with whatever you (plural)
decide.
1. Require and document that @part and following text be wrapped
in @ifnotinfo.
2. texinfo.tex supplies "Part I", "Part II", automatically.
3. texinfo.tex doesn't start a new page, but lets @chapter, @appendix
and @unnumbered do it.
4. makeinfo --docbook supplies tags.
Thanks again for listening and for the willingness to discuss.
Arnold
having problems with gendocs.sh
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 queue aborted, <> line 42670. The general-program.png file is present. I'm using the perl makeinfo. Help? Thanks, Arnold
Re: @part command and docbook
Hi Patrice. Me: > > Right now if I use @docbook, I'm getting: > > > > > > introductory blah blah here > > > > < these are from what came before the part > > > > > > ... > > Patrice: > That looks like a bug, the DocBook produced does not even seem to be > valid? I am missing something? So, I misspoke. I get the above if I manually insert the docbook. But, if I use @part, makeinfo does produce mostly correct docbook. There is one issue, which is the lack of tags. I had to manually insert them around all the text between the @part and the first @chapter. If makeinfo would insert them for me, I would be set. So, we might be able to have a happy ending after all. :-) Thank you both! Arnold
Re: @part command and docbook
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 /related > elements). Sorry. Actually, @docbook would mostly solve this. But I would need a way to tell makeinfo "close off any open sections / chapters that you have, NOW". Right now if I use @docbook, I'm getting: introductory blah blah here < these are from what came before the part ... > I created the Texinfo @part command as independent from the sectioning > structure because it had to be that way for compatibility, etc. > Creating a second kind of part command that *is* part of the sectioning > structure sounds like an awful lot of work for no essential gain. Suppose we don't include it in the structure and just add some commands that are mostly "noise"? @partnum I @part Title For Part I @partend texinfo.tex would print "Part I" using the argument to @partnum, and ignore @partend. makeinfo upon seeing @partnum or @part would close off whatever is open and generate the right tags; @partend generates . That seems straightforward to me, doesn't break any backward compatibility, and I hope doesn't impinge too much on the structure of the document or what makeinfo has to do when generating docbook. Worst case, I can live with the manual stuff. I prefer to have as much smarts as possible in the tools instead of in hacked-together scripts. And if DocBook is to be supported, this would help. And, since I'm asking, makeinfo should generate ... tags around any material after the part title and the first . Once again, thanks for listening. I appreciate both that and the current, much more advanced, state of DocBook generation in the texinfo tools. Arnold
@part command and docbook
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 @parttitle Title Of The Part Here @chapter ... @chapter ... @end part The would go into the docbook opening tag: Title ... Typically the labels are capital roman numerals: I, II, III etc. Perhaps a better alternative would be @partnode @part Title Here @end part I know it's a little weird. I'm trying to figure out how to work around the inherent impedance mismatch between the two markup languages in as least-intrusive a way as possible... So. There's the problem statement. Thoughts on how to deal with it would be welcome. Please cc me on answers as I'm not subscribed to the list. Much thanks, Arnold
Re: makeinfo --docbook should include a newline in @docbook
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 get it right. (It's even worse > with @macro.) OK. I didn't appreciate the depth of the problem. > It seems that, in practice, newlines are not ignored at the end of > @if... conditionals, but are ignored at the end of raw conditionals. I guess so. But for my uses of @docbook, I need the newline. > would be a true no-op, if that's what you want. > > Another approach is apparently to use an empty comment: > @docbook > stuff where you want the newline... > @c > @end docbook OK, I'll try some of these kinds of things and see what I end up with. > peformance, while > > peformance -> performance Thanks! (This may have been a manual typo, I'll check.) Thanks for the feedback. Arnold
makeinfo --docbook should include a newline in @docbook
Hi. Current makeinfo when processing @docbook ... @end docbook leaves off the trailing newline. For example: @docbook ∼ Cn2 @end docbook peformance, while This is wrong. I have to add the at the end so that the result doesn't run together with the following line: ∼ Cn2 performance, while Much thanks, Arnold
Re: texindex.c -o option doesn't work
> 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
I'm using variables everywhere, but I'm wondering if that isn't overkill.
> Thanks for the fix, too.
You're welcome. :-)
Thanks,
Arnold
texindex.c -o option doesn't work
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 like the idea is:
texindex foo.cp -o foo.out bar.cp -o bar.out ...
This seems kinda bogus.
The fact that no-one has reported this bug for who knows how many
years would seem to argue that it isn't used. At all. I suggest simply
nuking it. If not, at least please apply the fix below. :-)
Thanks,
Arnold
Index: util/texindex.c
===
--- util/texindex.c (revision 5417)
+++ util/texindex.c (working copy)
@@ -314,9 +314,9 @@
{
if (argv[arg_index] != (char *)NULL)
{
- arg_index++;
if (op > outfiles)
*(op - 1) = argv[arg_index];
+ arg_index++;
}
else
usage (EXIT_FAILURE);
Re: texinfo.tex indexing bug
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 @ as the escape character instead of \. So it > would be great if a new texinfo could accept either one, could simply > detect from the first line, I think. No problem. > I already changed the aux and toc, but not the index, precisely because > tinkering with texindex is not on my list of Fun Things To Do. > > If so, would you require fully portable awk, or could I take > advantage of stuff that is only in gawk? > > I wish I could say yes to gawk-only, but I think fully-portable is the > way to go. Texinfo gets installed on old systems, I know to my sorrow, > and if it only worked with gawk (even old gawk), that would just raise a > furor. Just don't want to go down that road. I was guessing as much, which is why I asked. For my definition, "fully portable" still means "new" awk - with functions, etc, as described by the 1988 awk book. I have some old versions of BWK awk that can be used for testing. (I think as far back as ~ 1993; I'd have to check.) To that end, can I assume that there will never be both \primary and \entry for the same key in a texindex input file? It looks like texinfo.tex defines a @cindexsub command, but this is undocumented? How would it be used? Thanks, Arnold
Re: texinfo.tex: @cartouche kills indentation
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, anything > that is embedded, like @quotation or @example, loses the indentation that > should be added, and is instead formatted flush left. > > Apparently it was an intentional change made years ago (by Stepan Kasal). > I think it was because people didn't have enough room for their examples > otherwise. But ok, I undid it: > > --- texinfo.tex (revision 5410) > +++ texinfo.tex (working copy) > @@ -6423,8 +6423,6 @@ > % side, and for 6pt waste from > % each corner char, and rule thickness >\normbskip=\baselineskip \normpskip=\parskip \normlskip=\lineskip > - % Flag to tell @lisp, etc., not to narrow margin. > - \let\nonarrowing = t% >% >% If this cartouche directly follows a sectioning command, we need the >% \parskip glue (backspaced over by default) or the cartouche can > > > We'll see. > > Best, > Karl
Re: texinfo to docbook - enhancement request
Hi Karl.
> Hi Arnold,
>
> @cindex main topic, secondary point, tertiary point
> ...
> main topicsecondary
> pointtertiary
> point
>
> Well, as you know, support for the usual index features has been on the
> todo list forever. I can't imagine having the time and energy to deal
> with them in the foreseeable future. (Maybe some new person would like
> to drive Texinfo?)
That's OK. I'm looking just for a makeinfo change.
> Anyway, as a workaround for your immediate needs, maybe Patrice can
> point you to a hook into the Docbook output where you can tinker with
> the index output easily enough. Patrice?
I'm willing - although hoping that Patrice could tackle it for me. :-)
> (BTW, if it were me, I would not use commas, because commas are often
> used in index entries without any desire for subterms. Even when the
> index does support subterms.
This is why we invented @comma{} way back when. :-)
> Some magic character like | seems like it
> would be better. But of course for real support one would want
> @commands anyway.)
Yes. I have thoughts about what kind of "real support" is needed but
I can do without it for now. Having commas in @cindex do primary,
secondary and tertiary would really help, though.
Thanks,
Arnold
bug in texinfo to docbook conversion
Hi.
A real bug. @math{whatever} is getting turned into
whatever
The problem is that the tag appears to no longer be valid
docbook. Xmllint chokes on it on my Ubuntu 12.04 system.
Thanks,
Arnold
texinfo to docbook - enhancement request
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 main topic @cindex main topic, secondary point @cindex main topic, secondary point, tertiary point Translating into main topic main topicsecondary point main topicsecondary pointtertiary point respetively. (See why I hade doing docbook by hand? :-) There is a similar need for adding tags but that is much less important at the moment. Can makeinfo be enhanced to do this? Thanks, Arnold
texinfo to docbook conversion - @r{} is not
Hi.
This returns to the idea of context awareness. Right now, @r{} is turned into
. This is totally wrong. The gawk manual has a
number of instances like this:
@table @code
@item -d@r{[}@var{file}@r{]}
@itemx --dump-variables@r{[}=@var{file}@r{]}
This gets turned into:
-d[file]
The general fix is context awareness. The short term fix is probably to
output the contents of @r{} without any markup and to issue a warning
to do the formatting differently in the texinfo source. I suspect that
this is what I need to do for the tables like this, anyway.
Thanks,
Arnold
Re: texinfo macro names don't allow digits
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 documented, it should be. > > It is. Along with approximately two zillion other caveats about @macro > usage :). > > Also, I would suggest that makeinfo be modified to enforce this > restriction as well. > > Historically, makeinfo's @macro has always accepted lots of things that > texinfo.tex's @macro doesn't. This was construed (not by me) to be a > feature, and I believe some documents rely on it (i.e., use texi2dvi -E > or have different definitions), so I don't much want to change it now. > > Best, > Karl
docbook conversion issue: nesting of formatting
[ 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 letting you nest one thing inside another. Docbook,
on the other hand, is quite picky and context sensitive. For example,
something like
The term @dfn{@command{awk} program} refers ...
produce this:
The term awk program refers
...
The problem is that ... is not allowed to appear
inside
The best way to fix this is to start teaching makeinfo what is
allowed and not allowed where, but to do that fully it would probably
have to start parsing the docbook DTD, and that's overkill.
Is it possible to simply "pull out" embedded items so that for
something like this we get
The term awk program ...
Much thanks,
Arnold
texinfo macro names don't allow digits
Hi All. I recently discovered that texinfo macros should not have digits in their names, since texinfo.tex chokes on them. I admit to not checking, but if this isn't documented, it should be. Also, I would suggest that makeinfo be modified to enforce this restriction as well. Much thanks, Arnold
texinfo.tex indexing bug
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
Re: texinfo 5.2 dist creates directories that are 777
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: $ umask 022 $ tar -xpzf /usr/local/src/Gnu/texinfo-5.2.tar.gz $ ls -ld texinfo-5.2 drwxrwxrwx 15 arnold arnold 4096 Sep 27 02:06 texinfo-5.2 "Surprise, surprise, surprise!" Besides, haven't the Autconf / Automake guys been making releases that change the default permissions on directories in tar balls to avoid this? (I admit I haven't followed in close detail.) Thanks, Arnold
Re: docbook generation problem with @image
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 usual). If you're willing to assume current > makeinfo, it should work, that is, presuming the behavior is acceptable > to you (from the Image Syntax node in the manual): > > In Info output, 'makeinfo' writes a reference to the binary image file > (trying FILENAME suffixed with 'EXTENSION', '.EXTENSION', '.png', or > '.jpg', in that order) if one exists. It also literally includes the > '.txt' file if one exists. This way, Info readers which can display > images (such as the Emacs Info browser, running under X) can do so, > whereas Info readers which can only use text (such as the standalone > Info reader) can display the textual version. We did discuss it, and the new makeinfo and info behave well. The catch is the "If you're willing to assume current makeinfo", which, sadly, I'm not. The new makeinfo is considerably slower, and for straight Info generation I prefer the old one, which is what's in /usr/bin on my Ubuntu dist. At some point, I'll move to a dist which ships Texinfo 5.x and then I'll simplify the gawk doc. For now I can live with it. Thanks, Arnold
Re: out of directory formats?
Just to close the loop... > Date: Tue, 16 Apr 2013 22:24:54 +0300 > From: Eli Zaretskii > Subject: Re: out of directory formats? > To: Aharon Robbins > Cc: bug-texinfo@gnu.org > > > From: Aharon Robbins > > Date: Tue, 16 Apr 2013 22:06:36 +0300 > > > > If I configure gawk from a directory different than where the > > source code is, and I want to make a PDF file, pdftex uses its installed > > texinfo.tex instead of the one in the gawk doc directory. > > > > Is there a way to make it get the version there? > > Setting TEXINPUTS should do that, I'd expect. Something was weird, but in any case I got it to work, and along the way I found two places in the makefile where I needed to set TEXINPUTS but had not (running dvips). Thanks, Arnold
out of directory formats?
Hi. If I configure gawk from a directory different than where the source code is, and I want to make a PDF file, pdftex uses its installed texinfo.tex instead of the one in the gawk doc directory. Is there a way to make it get the version there? Thanks, Arnold
docbook generation problem with @image
Hi. I have:
@float Figure,load-extension
@caption{Loading The Extension}
@c FIXME: One day, it should not be necessary to have two cases,
@c but rather just the one without the "txt" final argument.
@c This applies to the other figures as well.
@ifinfo
@center @image{api-figure1, , , Loading the extension, txt}
@end ifinfo
@ifnotinfo
@center @image{api-figure1, , , Loading the extension}
@end ifnotinfo
@end float
The generated docbook is:
*** contents of text file here ***
gawk Main Program Address Space
Extension
This is clearly wrong. It should only include one of the s, not
all of the possible ones. I would think PDF would be the right one.
Thanks,
Arnold
Re: Very long document title is not broken on title page
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 appreciate it. Arnold
Re: Very long document title is not broken on title page
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
>
> Maybe newer versions of Texinfo have a better solution, I never tried.
Thanks, this works. At the moment I have
@titlefont{AWK As A Major Systems Programming @*}
@title Language---Revisited
which errs the other way, not quite enough space between the two lines.
Karl - can we get
@title AWK As A Major Systems Programming
@titlex Language---Revisited
?
Thanks,
Arnold
indexing bug
Get the current standards.texi, format it with version 1999-04-25.15 and look at the index. It seems that `@setchapternewpage off' is in effect. The index starts in the middle of page 59, and is about 1/3 of the page in size. Subsequent index pages only use 1/3 the page! See pages 59-64. Arnold -- Aharon (Arnold) Robbins --- Pioneer Consulting Ltd. [EMAIL PROTECTED] P.O. Box 354Home Phone: +972 8 979-0381Fax: +1 603 761-6761 Nof Ayalon Cell Phone: +972 51 297-545(See www.efax.com) D.N. Shimshon 99784 Laundry increases exponentially in the ISRAEL number of children. -- Miriam Robbins
Re: weirdness with texi2dvi
> Date: Mon, 11 Oct 1999 16:30:06 +0200 (IST)
> From: Eli Zaretskii <[EMAIL PROTECTED]>
>
> On Mon, 11 Oct 1999, Aharon Robbins wrote:
>
> > Like a good boy, I later switched to texi2dvi, but at least at one time,
> > it would only run tex twice, thus in gawk's doc/Makefile.in, I now have:
> >
> > gawk.dvi: gawk.texi
> > -TEXINPUTS=$$TEXINPUTS:$(srcdir) $(TEXI2DVI) $(srcdir)/gawk.texi
> > texindex gawk.??
> > TEXINPUTS=$$TEXINPUTS:$(srcdir) $(TEX) $(srcdir)/gawk.texi
>
> Sorry, I missed this. I think this is wrong: $(srcdir) must come first
> in TEXINPUTS, not last. Otherwise, you might be using the wrong version
> of texinfo.tex.
You are correct, but I believe that this is an independent bug, as
there is no texinfo.tex file in my $TEXINPUTS directory.
> Date: Mon, 11 Oct 1999 16:28:36 +0200 (IST)
> From: Eli Zaretskii <[EMAIL PROTECTED]>
>
> If this doesn't help, post the last portion of TeX's log file.
Here it is:
\openout3 = `gawk.cp'.
\openout4 = `gawk.fn'.
\openout5 = `gawk.vr'.
\openout6 = `gawk.tp'.
\openout7 = `gawk.ky'.
\openout8 = `gawk.pg'.
] [2]
[1] [2] (Preface)
\openout0 = `gawk.toc'.
[1] [2] [3] Chapter1 [4] [5] [6] [7] Chapter2 [8] [9]
[10] [11] [12] [13] [14] [15] [16] [17] [18] Chapter3 [19] [20] [21] Chapter4
[22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] Chapter5
[35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49]
[50] [51] [52] [53] [54] [55] [56] [57] [58] Chapter6 [59] [60] [61] [62]
[63] [64] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] Chapter7 [75]
[76] [77] [78] [79] [80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90]
[91] [92] [93] [94] Chapter8 [95] [96] [97] [98] [99] [100] [101] [102]
Chapter9 [103] [104] [105] [106] [107] [108]
! Too many }'s.
l.8058 @samp{@@end ignore}
. Here is a program that strips out lines between
? x
Output written on gawk.dvi (112 pages, 296672 bytes).
---
Arnold
--
Aharon (Arnold) Robbins [EMAIL PROTECTED] [ <<=== NOTE: NEW ADDRESS!! ]
P.O. Box 354Home Phone: +972 8 979-0381Fax: +1 603 761-6761
Nof Ayalon Cell Phone: +972 51 297-545(See www.efax.com)
D.N. Shimshon 99784 Laundry increases exponentially in the
ISRAEL number of children. -- Miriam Robbins
weirdness with texi2dvi
Greetings. Here is a slightly bizarre bug report. Lo these many years ago, 'twas my habit to run: tex gawk.texi texindex gawk.?? tex gawk.texi texindex gawk.?? tex gawk.texi This was to make sure that all the cross references were right. (First pass the dvi file has unknown xrefs, but the .aux file then gets created for the next pass to read. Second pass has xrefs, but the page numbers can potentially be off. But it creates a .aux file with the right page numbers. Third pass gets it all correct.) Like a good boy, I later switched to texi2dvi, but at least at one time, it would only run tex twice, thus in gawk's doc/Makefile.in, I now have: gawk.dvi: gawk.texi -TEXINPUTS=$$TEXINPUTS:$(srcdir) $(TEXI2DVI) $(srcdir)/gawk.texi texindex gawk.?? TEXINPUTS=$$TEXINPUTS:$(srcdir) $(TEX) $(srcdir)/gawk.texi I manually run tex one more time to use the correct cross-references. This is fine and dandy, except that when I do something like this: mkdir /tmp/foo cd /tmp/foo /path/to/gawk-dist/configure make cd doc make dvi the last run of `tex' craps out in the middle. So, my question is why, and is it safe these days to just use texi2dvi? Will the xrefs always come out right? Thanks, Arnold -- Aharon (Arnold) Robbins [EMAIL PROTECTED] [ <<=== NOTE: NEW ADDRESS!! ] P.O. Box 354Home Phone: +972 8 979-0381Fax: +1 603 761-6761 Nof Ayalon Cell Phone: +972 51 297-545(See www.efax.com) D.N. Shimshon 99784 Laundry increases exponentially in the ISRAEL number of children. -- Miriam Robbins
