From: John Culleton <john@wexfordpress.com>
Cc: ntg-context@ntg.nl
Subject: Re: details.pdf
Date: Thu, 11 Jul 2002 10:38:42 -0400 [thread overview]
Message-ID: <200207111038.42544.john@wexfordpress.com> (raw)
In-Reply-To: <5.1.0.14.1.20020710175951.03cfece8@server-1>
>
> >Like everyone else I would like to see more complete worked examples.
> >Sorry, that is how we learn. If we copy a code fragment and it doesn't
> >work we are lost. If we can see the complete .tex file we have a chance at
> >least of spotting the little piece of code that makes it all work. At the
> >moment it is the fancy headers example in the mmakempy.pdf manual that
> >has me stumped.
>
> you mean the chap headers? well, that piece of code *is* presented verbatim
> in that file as example
>
> Hans
>
>
Yes, you did include it, (thanks!) , and I copied it and proofread it. As a
mentioned in another post the required mpgraph* files are created but they
are devoid of meaningful content. Here is a sample:
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 0 0
%%Creator: MetaPost
%%CreationDate: 2002.05.14:1139
%%Pages: 1
%%EndProlog
%%Page: 1 1
%%HiResBoundingBox: 0 0 0 0
showpage
%%EOF
All of them are like this.
Either I have left out something vital or included something harmful.
Only by comparing my source file with your source file can I figure out
which. I tried switching to a font that I know works, changing colors etc.
In the same document the flowcharting works without flaw.
Thanks for any help!
John Culleton
__________________________________________________
D O T E A S Y - "Join the web hosting revolution!"
http://www.doteasy.com
next prev parent reply other threads:[~2002-07-11 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 15:55 details.pdf John Culleton
2002-07-10 16:02 ` details.pdf Hans Hagen
2002-07-11 14:38 ` John Culleton [this message]
2002-07-11 22:02 ` details.pdf Hans Hagen
2003-03-06 17:47 details.pdf John Culleton
2003-03-06 19:39 ` details.pdf Willi Egger
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=200207111038.42544.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).