From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/26458 Path: news.gmane.org!not-for-mail From: David Arnold Newsgroups: gmane.comp.tex.context Subject: Re: Figure [left] Date: Wed, 22 Mar 2006 00:03:34 -0800 Message-ID: <68B01D2B-F2A8-4625-842E-2C490EA4C361@cox.net> References: Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: multipart/mixed; boundary="===============0989663726==" X-Trace: sea.gmane.org 1143015005 8508 80.91.229.2 (22 Mar 2006 08:10:05 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 22 Mar 2006 08:10:05 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Wed Mar 22 09:10:02 2006 Return-path: Envelope-to: gctc-ntg-context-518@gmane.org Original-Received: from mail-relay.eunet.no ([193.71.71.242]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FLyPm-0003CG-Bb for gctc-ntg-context-518@gmane.org; Wed, 22 Mar 2006 09:09:58 +0100 Original-Received: from ronja.ntg.nl (ronja.vet.uu.nl [131.211.172.88]) by mail-relay.eunet.no (8.13.1/8.13.1/GN) with ESMTP id k2M89wQ7095483 for ; Wed, 22 Mar 2006 09:09:58 +0100 (CET) (envelope-from ntg-context-bounces@ntg.nl) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 917D512788; Wed, 22 Mar 2006 09:04:56 +0100 (CET) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 29561-01; Wed, 22 Mar 2006 09:04:52 +0100 (CET) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 7C5DF12780; Wed, 22 Mar 2006 09:04:51 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id EA7C712780 for ; Wed, 22 Mar 2006 09:04:49 +0100 (CET) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 29057-02 for ; Wed, 22 Mar 2006 09:04:48 +0100 (CET) Original-Received: from fed1rmmtao01.cox.net (fed1rmmtao01.cox.net [68.230.241.38]) by ronja.ntg.nl (Postfix) with SMTP id 39DE812778 for ; Wed, 22 Mar 2006 09:04:47 +0100 (CET) Original-Received: from [10.0.1.2] (really [70.191.56.23]) by fed1rmmtao01.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060322080446.SPMJ15695.fed1rmmtao01.cox.net@[10.0.1.2]> for ; Wed, 22 Mar 2006 03:04:46 -0500 In-Reply-To: Original-To: "mailing list for ConTeXt users" X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.7 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl X-Virus-Scanned: amavisd-new at ntg.nl Xref: news.gmane.org gmane.comp.tex.context:26458 Archived-At: --===============0989663726== Content-Type: multipart/alternative; boundary=Apple-Mail-2--648826167 --Apple-Mail-2--648826167 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Aditya, Thanks, this worked. On Mar 21, 2006, at 6:18 PM, Aditya Mahajan wrote: > <--- On Mar 21, David Arnold wrote ---> > > > 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? > > I am not sure on what you want to achieve, but does this look better? > > \starttext > \placefigure > [left][fig:ordpair] > {}{\externalfigure[section1figs-mpgraph.1]} > We use the notation $(2,4)$ to denote what is called an {\em ordered > pair}. If you think of the positions taken by > 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 > > > HTH, > Aditya > > -- > Aditya Mahajan, EECS Systems, University of Michigan > http://www.eecs.umich.edu/~adityam || Ph: 7342624008 > _______________________________________________ > ntg-context mailing list > ntg-context@ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-context > --Apple-Mail-2--648826167 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 Aditya,

Thanks, this = worked.

On Mar 21, 2006, at 6:18 PM, Aditya Mahajan = wrote:

<--- On Mar 21, David Arnold = wrote --->

> All,
>
> Both this: =
>
> = %output=3Dpdf
>
> \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=3Dpdf
>
> \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? =

I am not sure on what you want to achieve, but = does this look better?

\starttext =
\placefigure
[left][fig:ordpair]
{}{\externalfigure[section1figs-mpgraph.1]}
We use the notation $(2,4)$ to denote what is called an {\em = ordered
=A0=A0 pair}. If you think of the = positions taken by
=A0 ordered pairs $(4,2)$ = and $(2,4)$ in the coordinate plane
=A0 (see = \in{Figure}[fig:ordpair]), then it is immediately apparent why =
=A0 order is important. The ordered pair $(4,2)$ is = simply not the same
as
=A0 the ordered pair $(2,4)$.

=A0= \stoptext


HTH,
Aditya

--
Aditya Mahajan, EECS Systems, University of Michigan =
http://www.eecs.umich.edu/~adi= tyam || Ph: 7342624008
_______________________________________________ =
ntg-context mailing list
ntg-context@ntg.nl =
http://www.ntg.nl/= mailman/listinfo/ntg-context

=

= --Apple-Mail-2--648826167-- --===============0989663726== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context --===============0989663726==--