ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: \sometxt bodyfontsize in staticMPfigure (2006.09.27 beta)
Date: Thu, 5 Oct 2006 09:22:02 -0400 (EDT)	[thread overview]
Message-ID: <Pine.WNT.4.63.0610050904480.2172@nqvgln> (raw)
In-Reply-To: <4524BBF6.2030606@wxs.nl>

On Thu, 5 Oct 2006, Hans Hagen wrote:

> Aditya Mahajan wrote:
>> On Thu, 28 Sep 2006, Hans Hagen wrote:
>>
>>> we can spend a lot of time to make it more advanced but within a year
>>> from now we will have mp as a library in tex which willreduce runtime to
>>> nearly zero (at least that 's what experiments show) so ....
>>>
>> Even when mp is available as a lib, it will not reduce runtime to
>> nearly zero? The time to start a mp process will be negligible, but
>> processing an mp file will still take time. In the mp diagrams that I
>> have, processing each diagram takes about 10 sec [1]. Occasionally
>>
> you mean that mp needs 10 sec per graphic? impressive

It is not just mp. It was a combination of mp ... textext ... metaobj 
... conversion to pdf. Doing some tests right now, I see that the main 
culprit was btex ... etex. Replacing all btex ... etex with \sometxt 
makes things really fast (~15 sec for 8 graphics). I just thought that 
metaobj was to blame but it is not. Maybe, I can get around without 
statics :-)

Aditya

      reply	other threads:[~2006-10-05 13:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28  4:24 Sanjoy Mahajan
2006-09-28  7:25 ` Hans Hagen
2006-09-29  0:16   ` Sanjoy Mahajan
2006-09-29  7:12     ` Hans Hagen
2006-10-04 23:14   ` Aditya Mahajan
2006-10-05  4:38     ` Sanjoy Mahajan
2006-10-05  7:08       ` Taco Hoekwater
2006-10-05  8:01     ` Hans Hagen
2006-10-05 13:22       ` Aditya Mahajan [this message]

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=Pine.WNT.4.63.0610050904480.2172@nqvgln \
    --to=adityam@umich.edu \
    --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).