From: David Arnold <dwarnold45@cox.net>
Subject: Figure [left]
Date: Tue, 21 Mar 2006 17:54:02 -0800 [thread overview]
Message-ID: <EC1CF1D5-0519-46FF-BFC4-1895D5A306E5@cox.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
All,
Both this:
%output=pdf
\starttext
We use the notation $(2,4)$ to denote what is called an {\em ordered
pair}. If you think of the positions taken by
\placefigure
[left][fig:ordpair]
{}{\externalfigure[section1figs-mpgraph.1]}
ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
(see \in{Figure}[fig:ordpair]), then it is immediately apparent why
order is important. The ordered pair $(4,2)$ is simply not the same as
the ordered pair $(2,4)$.
\stoptext
And this:
%output=pdf
\starttext
We use the notation $(2,4)$ to denote what is called an {\em ordered
pair}. If you think of the positions taken by
\placefigure
[left][fig:ordpair]
{}{\externalfigure[section1figs-mpgraph.1]}
ordered pairs $(4,2)$ and $(2,4)$ in the coordinate plane
(see \in{Figure}[fig:ordpair]), then it is immediately apparent why
order is important. The ordered pair $(4,2)$ is simply not the same as
the ordered pair $(2,4)$.
\stoptext
Lead to the same attached result. This is not the behavior expected.
Any ideas?
[-- Attachment #2: section1figs-mpgraph.1 --]
[-- Type: application/octet-stream, Size: 2972 bytes --]
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: -9 -11 82 83
%%HiResBoundingBox: -8.853 -10.7044 81.65207 82.47198
%%Creator: MetaPost 0.901
%%CreationDate: 2006.03.21:1720
%%Pages: 1
%%DocumentFonts: CMMI12 CMR12
%%BeginProlog
/cmmi12 /CMMI12 def
/cmr12 /CMR12 def
/fshow {exch findfont exch scalefont setfont show}bind def
%%EndProlog
%%Page: 1 1
%%HiResBoundingBox: -8.853 -10.7044 81.65207 82.47198
0.85 setgray 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
[] 0 setdash 1 setlinecap 1 setlinejoin 10 setmiterlimit
newpath 0 0 moveto
0 71.99997 lineto stroke
0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 0 moveto
71.99997 0 lineto stroke
0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 14.4 0 moveto
14.4 71.99997 lineto stroke
0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 14.4 moveto
71.99997 14.4 lineto stroke
0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 28.79999 0 moveto
28.79999 71.99997 lineto stroke
0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 28.79999 moveto
71.99997 28.79999 lineto stroke
0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 43.19998 0 moveto
43.19998 71.99997 lineto stroke
0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 43.19998 moveto
71.99997 43.19998 lineto stroke
0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 57.59998 0 moveto
57.59998 71.99997 lineto stroke
0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 57.59998 moveto
71.99997 57.59998 lineto stroke
0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 71.99997 0 moveto
71.99997 71.99997 lineto stroke
0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 0 71.99997 moveto
71.99997 71.99997 lineto stroke
0 setgray
newpath 0 0 moveto
71.99997 0 lineto stroke
newpath 68.30437 -1.5308 moveto
71.99997 0 lineto
68.30437 1.5308 lineto
closepath
gsave fill grestore stroke
0.5 0 dtransform exch truncate exch idtransform pop setlinewidth
newpath 0 0 moveto
0 71.99997 lineto stroke
0 0.5 dtransform truncate idtransform setlinewidth pop
newpath 1.5308 68.30437 moveto
0 71.99997 lineto
-1.5308 68.30437 lineto
closepath
gsave fill grestore stroke
74.99997 -2.5737 moveto
(x) cmmi12 11.95517 fshow
-3.0683 77.32458 moveto
(y) cmmi12 11.95517 fshow
69.07347 -10.7044 moveto
(5) cmr12 11.95517 fshow
-8.853 68.14777 moveto
(5) cmr12 11.95517 fshow
30.89998 62.68877 moveto
(\(2) cmr12 11.95517 fshow
41.30528 62.68877 moveto
(;) cmmi12 11.95517 fshow
46.54948 62.68877 moveto
(4\)) cmr12 11.95517 fshow
0 3 dtransform truncate idtransform setlinewidth pop
newpath 28.79999 57.59998 moveto 0 0 rlineto stroke
29.44519 17.7336 moveto
(\(4) cmr12 11.95517 fshow
39.8505 17.7336 moveto
(;) cmmi12 11.95517 fshow
45.0947 17.7336 moveto
(2\)) cmr12 11.95517 fshow
newpath 57.59998 28.79999 moveto 0 0 rlineto stroke
showpage
%%EOF
[-- Attachment #3: Type: text/plain, Size: 2 bytes --]
[-- Attachment #4: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2006-03-22 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 1:54 David Arnold [this message]
2006-03-22 2:18 ` Aditya Mahajan
2006-03-22 2:33 ` Matthias Weber
2006-03-22 8:03 ` David Arnold
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=EC1CF1D5-0519-46FF-BFC4-1895D5A306E5@cox.net \
--to=dwarnold45@cox.net \
--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).