ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: bug in mptopdf
Date: Fri, 08 Jul 2005 11:44:59 +0200	[thread overview]
Message-ID: <42CE4B1B.20800@wxs.nl> (raw)
In-Reply-To: <42CE3558.8050604@elvenkind.com>

Taco Hoekwater wrote:
> Hi Hans,
> 
> I am afraid there is a bug in the latest mptopdf. It presents
> itself by spurious spaces in the output for long postscript
> strings. Here is an example:
> 
> % uncomment next two lines for viewing in gv(1)
> %defaultfont := "Times-Roman";
> %prologues := 1;
> beginfig(1);
>   label ("This string wraps to a second line"&
>          " in the metapost output",(origin));
> endfig;
> end.
> 
> The created pdf document has a space after the p in metapost.
> The output contains:
> 
> (This\040string\040wraps\040to\040a\040second\040line\040in\040the\040metap\ 
> 
> ost\040output) cmr10 9.96265 fshow

This works ok here:

\starttext

\startMPpage
   label ("This string wraps to a second line"&
          " in the metapost output",(origin));
\stopMPpage

\stoptext

i wonder where your metap\<newline>ost comes from, is that something in your 
local mp? what happens if you set the line length in mp larger?

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
-----------------------------------------------------------------

      reply	other threads:[~2005-07-08  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08  8:12 Taco Hoekwater
2005-07-08  9:44 ` Hans Hagen [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=42CE4B1B.20800@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).