From: Hans Hagen <pragma@wxs.nl>
Cc: "Morten Høgholm" <moho01ab@student.cbs.dk>
Subject: Re: Possible bug in texexec
Date: Fri, 16 Apr 2004 09:31:04 +0200 [thread overview]
Message-ID: <6.0.1.1.2.20040416093005.027d75b0@server-1> (raw)
In-Reply-To: <opr6igk5m2lz63g6@news.gmane.org>
At 20:35 15/04/2004, you wrote:
>Dan Luecking has reported the following problem on c.t.t.:
>
>When mptopdf is used on a .mp file it preprocesses the file and
>the result (on my system it seems always to be named mptrace.tmp)
>is run through mpost. This mptrace.tmp has new-lines after every
>semicolon (;). This causes an error when the semicolon is part of
>a literal string, because mpost syntax requires such strings to be
>entirely on one line.
the reason for adding newlines after ;'s is that there have been problems
with the metapost buffer length
i didn't test itm, but maybe
s/(btex.*?)\;(.*?etex)/$1\@\@\@$2/gmois;
s/(\".*?)\;(.*?\")/$1\@\@\@$2/gmois; # add this line
s/\;/\;\n/gmois;
s/\n\n/\n/gmois;
s/(btex.*?)\@\@\@(.*?etex)/$1\;$2/gmois;
s/(\".*?)\@\@\@(.*?\")/$1\;$2/gmois; # and this one
somewhere around line 2260 in texexec.pl will help
Hans
next prev parent reply other threads:[~2004-04-16 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 18:35 Morten Høgholm
2004-04-16 7:31 ` Hans Hagen [this message]
2004-04-19 7:53 ` Morten Høgholm
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=6.0.1.1.2.20040416093005.027d75b0@server-1 \
--to=pragma@wxs.nl \
--cc=moho01ab@student.cbs.dk \
--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).