ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: metafun not working
Date: Wed, 29 Jun 2005 14:47:06 +0200	[thread overview]
Message-ID: <6faad9f0050629054765191fa2@mail.gmail.com> (raw)
In-Reply-To: <42C28C39.3060103@logosrl.it>

luigi.scarso wrote:
> Hans Hagen wrote:
> > Mojca Miklavec wrote:
> >
> >> I tried it out before reading that paragraph and I can approve: unless
> >> you have an ancient GS, it doesn't work at all. 3.40 at least does
> >> something even though it crashes.
> >
> >
> > but i have no problems here with gs 8.51 (all 8 versions worked ok) 
> > and pstoedit 3.33, so how recent is your gs?
> 
> Confirm : under linux MP.tex works with pstoedit 3.33 , gs 8.51 and even 
> ESP Ghostscript 7.07;
> pstoedit 3.40 does not works correctly with gs 8.51 and 7.07
> 
> luigi

I believe that the version 3.33 works, but I can't find it anywhere.
Even 3.40 is difficult to download. Usually only some polite
"bandwidth exceeded" message appears. I don't know if the development
of the program is stil in progress, but they could switch to
sourceforge.

The version on CTAN is 3.31 - this is the one which doesn't work even
for simple conversions outside ConTeXt. The paragraph I posted to the
list was taken from "New or changed in 3.32". This means that version
3.31 can't cope with the old GS.

pstoedit 3.40 seems to work as well. I can make conversions from
postscript to metapost outside ConTeXt without any problem. Also the
posted example with metafun trickery works somehow. It crashes the
pstoedit program, but obviously pstoedit manages to produce the proper
output before crashing.

I sent a short email to the email mentioned on the webpage - I hope
they will answer.

Mojca

  reply	other threads:[~2005-06-29 12:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 20:42 piskala upendran
2005-06-28 21:01 ` Taco Hoekwater
2005-06-29  7:18   ` luigi.scarso
2005-06-29  7:34     ` Taco Hoekwater
2005-06-29  8:15       ` luigi.scarso
2005-06-29  9:04         ` Wolfgang Zillig
2005-06-29  9:21           ` luigi.scarso
2005-06-29 10:43             ` Mojca Miklavec
2005-06-29 10:56               ` Hans Hagen
2005-06-29 11:55                 ` luigi.scarso
2005-06-29 12:47                   ` Mojca Miklavec [this message]
2005-06-29 17:22                     ` Hans Hagen
2005-06-29  7:59     ` Hans Hagen
2005-06-29  8:57       ` luigi.scarso
2005-07-07 12:38     ` Mojca Miklavec
2005-07-07 15:44       ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2005-07-04  4:34 piskala upendran
2005-06-30  6:44 piskala upendran
2005-06-29 16:00 piskala upendran
2005-06-29 16:52 ` Wolfgang Zillig
2005-06-28 16:18 piskala upendran
2005-06-28  8:19 piskala upendran
2005-06-28  8:17 piskala upendran
2005-06-28  9:31 ` Nikolai Weibull
2005-06-28  8:17 piskala upendran
2005-06-28  8:35 ` Taco Hoekwater
2005-06-27 11:00 [Fwd: metafun not working] Hans Hagen
2005-06-27 14:08 ` Taco Hoekwater
2005-06-28 19:49   ` Mojca Miklavec
2005-06-28 20:52     ` Hans Hagen
     [not found]       ` <6faad9f00506281432696c63f0@mail.gmail.com>
2005-06-28 21:37         ` metafun not working Mojca Miklavec

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=6faad9f0050629054765191fa2@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).