From: Simon Josefsson <jas@extundo.com>
Subject: Re: Gnus docs questions/notes
Date: Fri, 28 Jan 2005 10:32:26 +0100 [thread overview]
Message-ID: <ilu3bwl7vcx.fsf@totally-fudged-out-message-id> (raw)
In-Reply-To: <m3oefav2ax.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 28 Jan 2005 01:13:10 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>>> - Page numbering is restarted somewhere in gnus-manual-standard.pdf, so
>>> that the reference on page 2 to the Terminology section points to page
>>> 113, but there's no indication of the restart. That's confusing.
>>
>> Generating the pdf is a pain, but I'll give it a go...
>
> It looks like the problem is this:
>
> @iftex
> @iflatex
> @chapter Message
> @include message.texi
> @chapter Emacs MIME
> @include emacs-mime.texi
> @chapter Sieve
> @include sieve.texi
> @chapter PGG
> @include pgg.texi
> @chapter SASL
> @include sasl.texi
> @end iflatex
> @end iftex
>
> When including external documents, LaTeX/TeXinfo starts numbering
> pages anew, which kinda makes everything yucky. Anybody know a fix?
Not a simple one, but do those manuals really have to be included in
the Gnus PDF? Can't there be one PDF per package?
OTOH, a user manual should be self contained.
OTTH, the Gnus PDF is more of a reference manual than a user manual,
though.
Just some thoughts.
next prev parent reply other threads:[~2005-01-28 9:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 23:54 David Abrahams
2005-01-20 19:53 ` David Abrahams
2005-01-27 23:55 ` Lars Magne Ingebrigtsen
2005-01-28 0:13 ` Lars Magne Ingebrigtsen
2005-01-28 9:32 ` Simon Josefsson [this message]
2005-01-28 18:30 ` David Abrahams
2005-01-28 18:28 ` David Abrahams
2006-04-15 8:29 ` Lars Magne Ingebrigtsen
2006-04-15 13:10 ` David Abrahams
2006-04-15 13:16 ` Lars Magne Ingebrigtsen
2006-04-17 19:24 ` David Abrahams
2006-04-18 16:32 ` Lars Magne Ingebrigtsen
2005-01-28 19:41 ` Reiner Steib
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ilu3bwl7vcx.fsf@totally-fudged-out-message-id \
--to=jas@extundo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).