From: Taco Hoekwater <taco@elvenkind.com>
Subject: bug in mptopdf
Date: Fri, 08 Jul 2005 10:12:08 +0200 [thread overview]
Message-ID: <42CE3558.8050604@elvenkind.com> (raw)
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
Greetings, Taco
next reply other threads:[~2005-07-08 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 8:12 Taco Hoekwater [this message]
2005-07-08 9:44 ` Hans Hagen
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=42CE3558.8050604@elvenkind.com \
--to=taco@elvenkind.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).