<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.tex.metapost">
    <title>gmane.comp.tex.metapost</title>
    <link>http://blog.gmane.org/gmane.comp.tex.metapost</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2377"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2373"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2371"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2369"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2368"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2356"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2353"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2338"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2336"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2333"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2320"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2316"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2310"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2299"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2298"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2297"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2269"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2265"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2263"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.tex.metapost/2260"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2377">
    <title>intersectiontimes peculiarity</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2377</link>
    <description>&lt;pre&gt;I've read Knuth's explanation of how "intersectiontimes" works when two
paths intersect in multiple points (in Chapter 14 of the METAFONTbook), but
I cannot seem to figure out how to FORCE lexicographic ordering of the
intersection times.

For example, if paths p and q intersect in multiple points, I would like
to, somehow, have

(s,whatever) = q intersectiontimes p;

return the "first" (i.e., smallest "time") for q in which q and p
intersect.  This is illustrated in the code below (which generates the
attached figure).

Notice that q intersects p at times (and these times are for q) 0.07144,
0.35716, 0.64287, and 0.92859 which correspond to the points (1,-5),
(1,-3), (1,-1) and (1,1), respectively.  However, the command

(s,whatever) = q intersectiontimes p;

returns the last (namely 0.92859) time for q instead of the first (namely
0.07144) time for the intersection.  Is there a way to FORCE "q
intersectiontimes p" to always return the smallest time for q?

Thanks in advance,

Troy

--

path p,q,r;
p:=(0,0)&lt;/pre&gt;</description>
    <dc:creator>Troy Henderson</dc:creator>
    <dc:date>2013-04-24T09:27:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2373">
    <title>point "inside" cycle</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2373</link>
    <description>&lt;pre&gt;Does MetaPost have a clever way of determining whether a point z is
"inside" a closed path (cycle) p?

Troy Henderson
--
http://tug.org/metapost/&lt;/pre&gt;</description>
    <dc:creator>Troy Henderson</dc:creator>
    <dc:date>2013-04-23T01:10:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2371">
    <title>metapost packages</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2371</link>
    <description>&lt;pre&gt;Is there a web repository dedicated to Metapost macros/packages?
For example, I need to draw dimensions (a CAD feature): I have to write some macro myself or I am reinventing the wheel? And if I write something worth, how can I share it so to give it good web visibility and let others improve it?
Thanks.

Mario

--
http://tug.org/metapost/

&lt;/pre&gt;</description>
    <dc:creator>mv968</dc:creator>
    <dc:date>2013-04-07T23:14:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2369">
    <title>feature request</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2369</link>
    <description>&lt;pre&gt;Sorry newbie here. What about a "scaledaround" command? That is scaling 
with the possibility of choosing the origin of scaling. I think it would 
be useful.

Thanks.

Mario
--
http://tug.org/metapost/

&lt;/pre&gt;</description>
    <dc:creator>mv968</dc:creator>
    <dc:date>2013-04-07T10:08:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2368">
    <title>MetaPost 1.801 announcement</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2368</link>
    <description>&lt;pre&gt;
I am happy to announce a new release of MetaPost:

----------------------------------------------------------------------
MetaPost 1.801
----------------------------------------------------------------------

This is a bugfix release for 1.800.

The win32 binary as well as a source archive can be downloaded
immediately from the files section at

   https://foundry.supelec.fr/projects/metapost/

If you want to build MetaPost yourself, you can also do an anonymous
subversion checkout:

   $ svn checkout --username anonsvn 
https://foundry.supelec.fr/svn/metapost/tags/1.801

The password is anonsvn

----------------------------------------------------------------------
What is new in MetaPost version 1.801:
----------------------------------------------------------------------

* fixed an off-by-one error in the SVG output that prevented the last
   font's glyphs from actually being output to the svg file under
   prologues:=3;

* fixed a bug in bbox calculations in that caused the max y to be set
   based on &lt;/pre&gt;</description>
    <dc:creator>Taco Hoekwater</dc:creator>
    <dc:date>2013-04-05T09:57:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2356">
    <title>lua news</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2356</link>
    <description>&lt;pre&gt;The addition of lua to TeX and Metafont has been an interesting
development.  This snippet from the ACM TechNews Bulletin today
shows that others have recognized the value of lua as well, even
if not directly for font design and typesetting:


-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- University of Utah                    FAX: +1 801 581 4148                  -
- Department of Mathematics, 110 LCB    Internet e-mail: beebe&amp;lt; at &amp;gt;math.utah.edu  -
- 155 S 1400 E RM 233                       beebe&amp;lt; at &amp;gt;acm.org  beebe&amp;lt; at &amp;gt;computer.org -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe/ -
-------------------------------------------------------------------------------
--
http://tug.org/metapost/

&lt;/pre&gt;</description>
    <dc:creator>Nelson H. F. Beebe</dc:creator>
    <dc:date>2013-03-20T17:57:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2353">
    <title>solving equatiosn with metapost</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2353</link>
    <description>&lt;pre&gt;Hello,
           I am interested in Metapost's ability to solve equations. 
Consider this code "second.mp":

a/b=(a+3)/(b+8);
a=-3;
show a,b;

When I run the code, however I get mistake(s):

mpost second.mp
This is MetaPost, version 1.504 (kpathsea version 6.0.1)
(mpost.mp (c:/texlive/2011/texmf-dist/metapost/base/plain.mp
Preloading the plain mem file, version 1.004)) (./second.mp
 &amp;gt;&amp;gt; a
 &amp;gt;&amp;gt; b
! Not implemented: (unknown numeric)/(unknown numeric).
&amp;lt;to be read again&amp;gt;
                    =
l.1 a/b=
         (a+3)/(b+8);
?


I would be grateful if someone would let me know:

(a) what I am doing wrong with this code?
(b) Say if the code is fixed and run well, what Metapost command to put 
after show a,b; so that Metapost exits normally because it seems that I 
get a * if the code runs well and then Metapost is still awaiting for 
some other command(s)?



Thanks a lot...

Best Regards,
Y.Calleecharan

--
http://tug.org/metapost/

&lt;/pre&gt;</description>
    <dc:creator>Yogeshwarsing Calleecharan</dc:creator>
    <dc:date>2013-03-20T07:55:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2338">
    <title>btex..etex debugging</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2338</link>
    <description>&lt;pre&gt;Hi,

I am experiencing strange effects when using btex..etex with a certain
document style: the bounding box is not determined correctly. For
debugging purposes I would therefore like to obtain an mpxerr.tex file
even though not tex-error occurs. Is that possible? Thanks for any
help!

Best,
Stefan
--
http://tug.org/metapost/

&lt;/pre&gt;</description>
    <dc:creator>Stefan Witzel</dc:creator>
    <dc:date>2013-03-12T16:40:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2336">
    <title>what about allsuffixes operator?</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2336</link>
    <description>&lt;pre&gt;
Hello, again,

MS:

To derail the discussion further, we would like to come up
with a proposal (it sprouts in our heads quite a long time)
of extending the functionality of Metapost by an
`allsuffixes' operator.

Let's explain the idea on a trivial example. Assume that we have
declared or used variables a.a, a.a.b, a.a.b.c; then the statement
    forsuffixes $:=allsuffixes a:
would succesively assign to $ the suffixes a, a.b, a.b.c,
and the statement
    forsuffixes $:=allsuffixes a.a:
would succesively assign to $ the suffixes b, b.c.

Perhaps the operation of the undefining of a variable
(i.e., deleting it, not to be confused with the assigning
of an undefined value to a variable) should consequently
accompany such and extension.

The generated sequence of suffixes could be perhaps
lexicographically ordered.

Note that such an operation actually is ("implicitly")
implemented in Metafont, and, thus, in Metapost.
The primitive `showvariable' does the job, with lexicographic
sorting. (There is not, however, &lt;/pre&gt;</description>
    <dc:creator>Boguslaw Jackowski</dc:creator>
    <dc:date>2013-03-02T21:09:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2333">
    <title>testing mpost 1.790 under Windows and Linux</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2333</link>
    <description>&lt;pre&gt;
Dear Taco,

very many thanks for releasing the version 1.790 of MetaPost.

We have tested it with one of our fonts. The resaults
are nearly good. :)

In a `standard' math mode (low precision) we were able to compile
the whole fonts without problems, the results being identical
to the results produced by mpost 1.5*.

We have four remarks: a serious one and three minor ones.
Let's start with tha latter ones.

1. Minor remarks:

   (a) mpost 1.790 is noticeably slower under Windows than
       the previous, 1.503, version; under Linux i64, there
       is no measurable difference

   (b) even the most trivial program invoked without mem file name
       given explicitly loops generating (infinitely?) many of parethesises:

       This is MetaPost, version 1.790 (kpathsea version 6.1.1dev)  1 MAR 2013 14:47
       **zz.mp
       (plain.mp Preloading the plain mem file, version 0.63))))))))...

       Passing on the command line parameter --mem=mpost
       cures the problem (note that --mem=mpost.mp doesn't)

 &lt;/pre&gt;</description>
    <dc:creator>Boguslaw Jackowski</dc:creator>
    <dc:date>2013-03-01T14:18:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2320">
    <title>Question: [MPLib, MetaFun, ConTeXt, LuaTeX] metapost logging and message primitive?</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2320</link>
    <description>&lt;pre&gt;I have a METAPOST program that works fine with mpost, but fails when I try
to run it inline in ConTeXt. In order to debug it, I would like to see the
usual METAPOST logging and/or to use the METAPOST "message" primitive.

However, whenever I add "loggingall;" or a message statement to my ConTeXt
file, I encounter errors like this

%------
metapost        &amp;gt; initializing instance 'metafun' using format 'metafun'
metapost        &amp;gt; loading 'metafun':
D:/texlive/2012/texmf-dist/metapost/context/base/metafun.mpiv
! terminal:
%-------

What is the appropriate way to debug problems with inline METAPOST code in
ConTeXt?

My example file is:
%-------
\loggingall

\starttext
\framed{Hello world.}
This is a simple_test.

\startMPpage
loggingall;
fill fullcircle scaled 1in withcolor blue;
label.top(btex This is a test. etex, origin);
\stopMPpage

\stoptext
%-------

I am using TeXLive 2012 on Windows.

I apologize for any vagueness in this question. I'm not really sure how the
various pieces fit together.

Thanks for you&lt;/pre&gt;</description>
    <dc:creator>Colin Fraizer</dc:creator>
    <dc:date>2013-02-18T12:57:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2316">
    <title>[bug report] Segmentation fault when unifying strings</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2316</link>
    <description>&lt;pre&gt;Hi,

When I metapost the following program, I get a segmentation fault:

%%%%%%%%%%%%%%%%
string a;

%a = "a";% works fine.
"a" = a;   % segmentation fault.

end
%%%%%%%%%%%%%%%%

typing:
$ mpost --version
gives:
%%%%%%%%%%
MetaPost 1.504
The MetaPost source code in the public domain.
MetaPost also uses code available under the
GNU Lesser General Public License (version 3 or later);
therefore MetaPost executables are covered by the LGPL.
There is NO warranty.
For more information about these matters, see the file
COPYING.LESSER or &amp;lt;http://gnu.org/licenses/lgpl.html&amp;gt;.
Original author of MetaPost: John Hobby.
Author of the CWEB MetaPost: Taco Hoekwater.
%%%%%%%%%%%


I'm using Ubuntu 12.04.1 on a 32-bit machine.

I'm happy to supply further details if needed.

Yours,
Ohad.
--
http://tug.org/metapost/

&lt;/pre&gt;</description>
    <dc:creator>Ohad Kammar</dc:creator>
    <dc:date>2013-01-10T14:51:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2310">
    <title>"input mp-tool" and "input metafun" do not work</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2310</link>
    <description>&lt;pre&gt;Hello,

In the Metafun manual, it is said that its is enough to input the "mp-tool" file, or to enter "input metafun;"  to use most of the metafun macros with the plain format of MetaPost. It does not work with the Metapost or Metafun version included in TeXLive 2012 (I use MacTeX 2012, with Mac OS X 6.8).

Each time I include the line

input mp-tool;

in a MetaPost file, it triggers this error message:

! I can't open file `mp-tool'.
l.4 input mp-tool
                 ;
Please type another input file name:  file name: 

Note that this bug has already been reported here: http://tex.stackexchange.com/questions/68750/metapost-mptopdf-complains-cant-open-file-mp-tool?rq=1

The solution is apparently to enter "input mp-tool.mpii" instead of "input mp-tool", but as far as I know it is not documented anywhere.

There is something weirder: If I try "input metafun" instead of "input mp-tool", as the Metafun manual also suggests, I obtain this strange error message:

! Redundant equation.
&amp;lt;to be read again&amp;gt; 
        &lt;/pre&gt;</description>
    <dc:creator>Franck Pastor</dc:creator>
    <dc:date>2013-01-03T20:32:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2299">
    <title>label and for loop</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2299</link>
    <description>&lt;pre&gt;I would like to write something like

for i = 1 upto 10
  label( btex $A_i$ etex, z[i])
endfor

so that I get A_0 for z0, A_1 for z1,...

Is it possible ?
--
http://tug.org/metapost/

&lt;/pre&gt;</description>
    <dc:creator>Ranousse</dc:creator>
    <dc:date>2012-11-23T23:16:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2298">
    <title>Connectons-nous sur LinkedIn</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2298</link>
    <description>&lt;pre&gt;LinkedIn
------------



J'aimerais vous inviter à rejoindre mon réseau professionnel en ligne, sur le site LinkedIn.

Nizar

Nizar Fakhfakh
--
Région de Paris , France

Veuillez confirmer que vous connaissez Nizar Fakhfakh :
https://www.linkedin.com/e/-dy5li7-h9ii0xoo-2w/isd/9583120715/v61ROR1P/?hs=false&amp;amp;tok=2E5UbaBytR3Rw1

--
Vous recevez des invitations à vous connecter par e-mail. Cliquez ici si vous ne souhaitez plus recevoir ces e-mails :
http://www.linkedin.com/e/-dy5li7-h9ii0xoo-2w/zN3QFw3n3ah2b-UpbeJc4ZGvIUh/goo/metapost%40tug%2Eorg/20061/I3203019151_1/?hs=false&amp;amp;tok=0oELrFrbNR3Rw1

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.


  
--
http://tug.org/metapost/&lt;/pre&gt;</description>
    <dc:creator>Nizar Fakhfakh</dc:creator>
    <dc:date>2012-11-14T13:41:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2297">
    <title>Connectons-nous sur LinkedIn</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2297</link>
    <description>&lt;pre&gt;LinkedIn
------------



J'aimerais vous inviter à rejoindre mon réseau professionnel en ligne, sur le site LinkedIn.

Nizar

Nizar Fakhfakh
--
Région de Paris , France

Veuillez confirmer que vous connaissez Nizar Fakhfakh :
https://www.linkedin.com/e/-dy5li7-h9ii0gqp-6n/isd/9583120715/v61ROR1P/?hs=false&amp;amp;tok=2E5UbaBytR3Rw1

--
Vous recevez des invitations à vous connecter par e-mail. Cliquez ici si vous ne souhaitez plus recevoir ces e-mails :
http://www.linkedin.com/e/-dy5li7-h9ii0gqp-6n/zN3QFw3n3ah2b-UpbeJc4ZGvIUh/goo/metapost%40tug%2Eorg/20061/I3203016685_1/?hs=false&amp;amp;tok=2WEic5FlVR3Rw1

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.


  
--
http://tug.org/metapost/&lt;/pre&gt;</description>
    <dc:creator>Nizar Fakhfakh</dc:creator>
    <dc:date>2012-11-14T13:41:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2269">
    <title>C/C++ code to produce Bezier curves from Metafont source</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2269</link>
    <description>&lt;pre&gt;Stupid question, probably …
 
I need some C code to generate Bezier curves from Metafont source code. Ideally, I'd like to have a C/C++ function with the following specifications:
 
Input: an array of text strings (the lines in the MetaFont program)
Output: an array of Bezier curves representing the centerlines of the "pen" strokes (plus some information about the pen used for each stroke).
 
So, internally, this code would parse the MetaFont source, solve little systems of linear equations, and calculate the control points of the Bezier curves.
 
Code like this must exist in both MetaFont and MetaPost, but I'm having trouble finding it. 
 
I read mplibapi.tex and did some other hunting around, and I learned that I should probably be looking at mplib.c and mplib.h.
But I can’t find these at foundry.supelec.fr/gf/project/metapost
 
So, my questions are:
(1) Are mplib.c and mplib.h in fact the best starting points ?
(2) If they are, where can I find them ?
(3) If not, what are better options ?
 
Tha&lt;/pre&gt;</description>
    <dc:creator>xiolyxioly</dc:creator>
    <dc:date>2012-10-21T13:50:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2265">
    <title>Metafun and TeXLive 2012</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2265</link>
    <description>&lt;pre&gt;Hi everybody,

I am having a problem with Metafun. I am running mac os 10.7.5 and have recently installed TeXLive 2012. If I run mptopdf on the following test.mp :


I get 





If I suppress the \input metafun; line, I get 





With TeXLive 2011, everything works fine. Any idea on this issue?

Thanks a lot for your help.


Fabien

--
http://tug.org/metapost/&lt;/pre&gt;</description>
    <dc:creator>Fabien Vignes-Tourneret</dc:creator>
    <dc:date>2012-10-16T21:10:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2263">
    <title>space in labels</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2263</link>
    <description>&lt;pre&gt;I want to write a label with a space in it
label("my label", position);
Instead of a space a kind of minus caracter is written.
Is there a solution to my problem without using btex my label etex ?

--
http://tug.org/metapost/

&lt;/pre&gt;</description>
    <dc:creator>Ranousse</dc:creator>
    <dc:date>2012-10-01T15:30:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2260">
    <title>[Fwd: [tex-live] Old metapost label issue]</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2260</link>
    <description>&lt;pre&gt;Karl mentioned this might be a better plase to post this than the 
texlive list

-------- Original Message --------
Subject: [tex-live] Old metapost label issue
Date: Mon, 6 Aug 2012 11:52:33 +0200
From: Lars Madsen &amp;lt;daleif&amp;lt; at &amp;gt;imf.au.dk&amp;gt;
To: TeX Live &amp;lt;tex-live&amp;lt; at &amp;gt;tug.org&amp;gt;

Hi TL's

Back in 2010, I described a labelling problem in metapost regarding
relative paths

Here is Tacos answer

http://www.tug.org/pipermail/tex-live/2010-February/024806.html

Does anyone know the status of this? The problem still exists, but I'm
not sure if this should be a bug or a feature due to security?


&lt;/pre&gt;</description>
    <dc:creator>Lars Madsen</dc:creator>
    <dc:date>2012-09-26T14:31:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.tex.metapost/2252">
    <title>METATYPE1 pen-stroking and tight curves</title>
    <link>http://comments.gmane.org/gmane.comp.tex.metapost/2252</link>
    <description>&lt;pre&gt;As discussed here a few weeks ago, METATYPE1's pen-stroking macro, because
of the nature of the problem it's solving, can at best produce an
approximation of the theoretical ideal envelope.  On some kinds of input,
the approximation isn't very good; one particular area of difficulty seems
to be when the path being stroked has a segment with tight but smooth
curvature.  The ideal envelope in such a case would include a sharp corner
even though no sharp corner exists in the input; and pen_stroke() will
sometimes produce a deep indentation in the envelope instead of a sharp
corner.  The visual effect looks a little bit like the "ink traps" that
are sometimes deliberately included in traditional metal type designs
intended for printing on newsprint, but the ones from pen_stroke are
uncontrolled and usually undesirable.

I've made some progress on a solution in the context of my Tsukurimashou
project:  code can, with reasonable success, automatically detect path
segments likely to cause this problem and introduce&lt;/pre&gt;</description>
    <dc:creator>mskala&lt; at &gt;ansuz.sooke.bc.ca</dc:creator>
    <dc:date>2012-09-19T16:29:25</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.tex.metapost">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.tex.metapost</link>
  </textinput>
</rdf:RDF>
