ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "George N. White III" <gnwiii@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: makempy (pstoedit <-> gs) hangs
Date: Mon, 30 Jul 2007 12:54:08 -0300	[thread overview]
Message-ID: <22af238a0707300854k6af19acv71d0c8028b49c798@mail.gmail.com> (raw)
In-Reply-To: <20070730130357.GA23971@phare.normalesup.org>

On 7/30/07, Arthur Reutenauer <arthur.reutenauer@normalesup.org> wrote:

> > I have patched 'pstoedit.dll' version 3.44 (0x6B674: 0x20 --> 0x25)
> > and so it works with gs 8.57 for me!
>
>   (Yes, that 2-bit patch ;-)
>
>   Great! In the mean time I exchanged mail with the author of pstoedit
> (thanks to someone who forwarded my previous mail to him ;-) and it
> should be fixed in the next release of pstoedit (3.45). Actually the
> problem was (of course) a bit more complicated than what I first
> described and there was a reason why getorigfont should call itself
> recursively; and why it wouldn't work with newer versions of gs (I can
> explain it in case anyone is interested).

I'm interested, but it is good to post the explanation so it becomes
part of the public record google can find.  Problems like this have a
way of cropping up many times -- it will be a few years before all linux
distros have updated to the new version, and some will make backports
of the patch.  The next people who encounter this will benefit from seeing
the explanation so they can make the fix in somewhat different versions
of pstoedit..

-- 
George N. White III <aa056@chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2007-07-30 15:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1185789602.14300.ntg-context@ntg.nl>
2007-07-30 12:30 ` Wolfgang Werners-Lucchini
2007-07-30 13:03   ` Arthur Reutenauer
2007-07-30 13:46     ` luigi scarso
2007-07-30 15:54     ` George N. White III [this message]
2007-07-30 21:52       ` Bug in pstoedit 3.44 (was: makempy (pstoedit <-> gs) hangs) Arthur Reutenauer
2007-07-31  8:07         ` luigi scarso
2007-07-30 22:42   ` makempy (pstoedit <-> gs) hangs luigi scarso
2007-07-31 20:02 ` itemize with zero start Wolfgang Werners-Lucchini
2007-07-31 20:36   ` Hans Hagen
     [not found] <mailman.2244.1185265633.2368.ntg-context@ntg.nl>
2007-07-28 18:35 ` makempy (pstoedit <-> gs) hangs Wolfgang Werners-Lucchini
2007-07-29 12:52   ` George N. White III
2007-07-29 23:37     ` Arthur Reutenauer
     [not found] <mailman.2215.1185128434.2368.ntg-context@ntg.nl>
2007-07-23 22:49 ` Wolfgang Werners-Lucchini
2007-07-24  7:51   ` Hans Hagen
2007-07-20 23:19 Wolfgang Werners-Lucchini
2007-07-22 13:03 ` Mojca Miklavec
2007-07-29 12:45   ` George N. White III

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=22af238a0707300854k6af19acv71d0c8028b49c798@mail.gmail.com \
    --to=gnwiii@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).