From: "John R. Culleton" <john@wexfordpress.com>
Cc: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Problem with \typefile
Date: Wed, 19 Jul 2006 19:05:38 -0400 [thread overview]
Message-ID: <200607191905.38561.john@wexfordpress.com> (raw)
In-Reply-To: <44BE4DFF.3060905@elvenkind.com>
On Wednesday 19 July 2006 11:21, Taco Hoekwater wrote:
> John R. Culleton wrote:
> > The document compiles fine and displays fine in xpdf or kpdf
> > (Linux).
> > But Acrobat Reader 7.0 (Linux) comes up with the message "there was a
> > problem with this document" and displays two blank pages instead.
> > It will however display the rest of the document if the \stoptext
> > statement above is removed.
>
> I cannot reproduce that problem. I guess the exact contents of
> samp.tex is a key ingredient so if it is not too big ...
>
> (and check your log for font mapping issues)
>
> Success, Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
This was truly a wierd one. Way back in my subfile "macros.tex" I
had an erroneous statement:
\setuptyping [option=tex]
This compiled clean and the resulting pdf could be read in xpdf.
But Acrobat Reader didn't like it.
I have no memory of when or how I came up with that option.
To find the problem first I commented out
\input macros.tex
which identified where the problem was. Then
I commented out the whole macros.tex file (128 lines),
and uncommented it block by block until I found the culprit.
Whew!
--
John Culleton
Able Indexing and Typesetting
Precision typesetting (tm) at reasonable cost.
Satisfaction guaranteed.
http://wexfordpress.com
prev parent reply other threads:[~2006-07-19 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 14:54 John R. Culleton
2006-07-19 15:21 ` Taco Hoekwater
2006-07-19 23:05 ` John R. 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=200607191905.38561.john@wexfordpress.com \
--to=john@wexfordpress.com \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.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).