From: John Culleton <john@wexfordpress.com>
Subject: Re: Typo in d-en-all.tex
Date: Wed, 15 Oct 2003 17:35:01 -0400 [thread overview]
Message-ID: <200310151735.01319.john@wexfordpress.com> (raw)
In-Reply-To: <200303171225.08140.john@wexfordpress.com>
The typo in d-en-all.tex persists. As a result the useful information
on bookmarks never makes it into the pdf file.
FYI
On Monday 17 March 2003 12:25, John Culleton wrote:
> I uncovered an ancient typo. Here is a text fragment from the above
> document:
>
> \ShowSample {001} {A simple document}
> \ShowSample {002} {Setting up the page}
> \ShowSample {003} {Using the margin}
> \ShowSample {004} {Adaptive headers and footers}
> \ShowSample {004} {Some bookmarks}
>
> The 004 file is called twice, and the 005 file is omitted.
>
> Sounds like a case for 007 :-)
>
> John Culleton
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
--
John Culleton
Able Typesetters and Indexers
http://wexfordpress.com
prev parent reply other threads:[~2003-10-15 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 17:25 John Culleton
2003-10-15 21:35 ` John Culleton [this message]
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=200310151735.01319.john@wexfordpress.com \
--to=john@wexfordpress.com \
--cc=ntg-context@ntg.nl \
/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).