From: "Cho, Jin-Hwan" <chofchof@ktug.or.kr>
Subject: Testing a sample in details.pdf
Date: Wed, 19 Feb 2003 14:30:37 +0900 [thread overview]
Message-ID: <3E53167D.72706E07@ktug.or.kr> (raw)
[-- Attachment #1: Type: text/plain, Size: 2149 bytes --]
While I'm testing some examples in details.pdf (http://www.pragma-ade.com/temp/details.pdf),
a curious thing happened.
Let me assume that I have the following test file (test.tex) which was extracted
from details.pdf (p.13) I generated two PDF files, test-1.pdf and test-2.pdf,
by the following ways, respectively.
1. The first way
Just ran "texexec --pdf test", and got the attached PDF file, test-1.pdf.
(Please see the attached file test-1.log too.)
2. The second way (step by step)
(a) "texexec --pdf --once test"
(b) "texutil --references test"
(c) "texexec --pdf --once test"
(d) "mpost mpgraph"
(e) "texexec --pdf --once test"
The curious thing was that the two PDF files were different, especially
the embedded MetaPost graphics were different. In my opinion, test-2.pdf
seemed to be the right result.
=== BEGIN test.tex ===
\setupcolors[state=start]
\definecolor[infogray][darkgray]
\definecolor[textgray][lightgray]
\definetextbackground[intro]
[backgroundcolor=infogray,
backgroundoffset=.25cm,
offset=.5cm,
frame=off,
location=paragraph,
color=white]
\definetextbackground[subintro]
[backgroundcolor=textgray,
backgroundoffset=0pt,
offset=0pt,
frame=off,
location=text,
color=blue]
\starttext
\starttextbackground[intro]
A rather common way to draw attention to a passage, is to add
a background. In this chapter we will therefore discuss how
to enhance your document with \starttextbackground [subintro]
colorful areas that either or not follow the shape of your
paragraph. \stoptextbackground\ Be warned: this chapter has
so many backgrounds that you should consider wearing sunglasses.
\stoptextbackground
\stoptext
=== END test.tex ===
Best, ChoF.
--
*** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ***
^ ^ | ChoF := Jin-Hwan Cho | *^ ^*
o | chofchof@ktug.or.kr | * o *
*** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ***
*^ ^* | Project Manager of | ^ ^
* O * | DVIPDFMx and MiKTeX-KTUG | O
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Research Fellow, School of Mathematics |
| Korea Institute for Advanced Study |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[-- Attachment #2: test-1.pdf --]
[-- Type: application/pdf, Size: 8772 bytes --]
[-- Attachment #3: test-2.pdf --]
[-- Type: application/pdf, Size: 8776 bytes --]
[-- Attachment #4: test-1.log --]
[-- Type: application/x-unknown-content-type-txtfile, Size: 9246 bytes --]
next reply other threads:[~2003-02-19 5:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 5:30 Cho, Jin-Hwan [this message]
2003-02-19 11:02 ` Hans Hagen
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=3E53167D.72706E07@ktug.or.kr \
--to=chofchof@ktug.or.kr \
--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).