From: Hans Hagen <pragma@wxs.nl>
Subject: Re: ConTeXt + asymptote
Date: Thu, 29 Jun 2006 20:05:04 +0200 [thread overview]
Message-ID: <44A41650.6050009@wxs.nl> (raw)
In-Reply-To: <20060629134039.12300.qmail@wizard.math.ualberta.ca>
John Bowman wrote:
> In regard to adding support for ConTeXt or plain TeX to Asymptote, it
> should be no problem to do this, but perhaps someone on this list can help
> provide some preliminary information, particularly regarding item 1 below
> on how best to rotate text at an arbitrary angle. Also, since I am not sure
> what the precise planned use of a plain tex/ConTeXt engine here is, it isn't
> clear to me whether the miniltx solution below would be an acceptable solution.
>
i cannot answer for other users but i guess that they want a more
integrated approach, i.e. include a code in the doc source, write style
info at runtime, etc
latex and context differ too much
from what users wrote to this list, i understood that much tex related
stuff in asymptote is hard coded, so it's probably enough when all the
strings (in the c source) that now contain latex code can be configured;
there is no need for you to look into context, when things can be
configured, the users will do that for you
> Perhaps someone can also explain why so many context users are interested in
> this feature? Why exactly can't they let Asymptote do its typesetting with
> latex behind the scenes and then import the resulting ps or pdf files in
> context? Is the issue just that latex might not be installed? If so, the
>
indeed, esp when they use the so called minimal distributions;
> miniltx style file (which appears to be part of plain tex) seems like a
> viable and simple solution.
>
> In regard to the remark I saw posted about "monster eps" files, use the
> -aZ option and you will see that Asymptote output files are as compact as
> those of MetaPost. If you want tex labels, you have to process MetaPost output
> through dvips, etc. Asymptote simply does this automatically, perhaps giving
> some users the illusion that Asymptote files are bigger. In other words, you
> should compare the final postscript files that MetaPost produces, not the
> intermediate ones (I recall that there is a MetaPost command for running
> MetaPost output through dvips too).
>
in context dvips is not used for mp graphics; context comes with an
integrated mp output parser; this means that integration is also
efficient (handy when you have a couple of hundred mp graphics) esp with
regards to resources
i suppose that others can comment on the rest of your mail
Hans
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-06-29 18:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 13:40 John Bowman
2006-06-29 18:05 ` Hans Hagen [this message]
2006-06-30 1:12 ` Sanjoy Mahajan
2006-06-30 8:16 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2006-10-15 5:04 John Bowman
2006-04-21 15:49 Renaud AUBIN
2006-04-21 16:17 ` Renaud AUBIN
2006-04-21 16:45 ` Hans Hagen
2006-04-21 18:29 ` Jilani Khaldi
2006-04-21 18:52 ` Renaud AUBIN
2006-04-21 19:11 ` Hans Hagen
2006-04-21 19:13 ` Hans Hagen
2006-04-21 19:25 ` Renaud AUBIN
2006-04-22 8:38 ` Hans Hagen
2006-04-22 9:16 ` andrea valle
2006-04-21 19:10 ` Hans Hagen
2006-04-21 19:20 ` Renaud AUBIN
2006-04-21 19:52 ` Hans Hagen
2006-04-23 18:51 ` Renaud AUBIN
2006-04-23 20:28 ` Hans Hagen
2006-04-23 21:02 ` Renaud AUBIN
2006-04-23 21:50 ` Hans Hagen
2006-04-23 22:33 ` Renaud AUBIN
2006-04-24 0:54 ` Sanjoy Mahajan
2006-04-24 7:33 ` Hans Hagen
2006-04-25 4:36 ` Sanjoy Mahajan
2006-04-25 7:04 ` Hans Hagen
2006-04-25 8:02 ` Taco Hoekwater
2006-04-25 15:17 ` Sanjoy Mahajan
2006-04-21 19:37 ` Sanjoy Mahajan
2006-04-21 23:30 ` Mojca Miklavec
2006-04-25 7:52 ` Taco Hoekwater
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=44A41650.6050009@wxs.nl \
--to=pragma@wxs.nl \
--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).