Re: Outputtemplate influences %& format comment parsing in verbatimtex
luigi scarso <[email protected]> Sun, 24 Dec 2023 16:19:24 +0100
| Newsgroups | gmane.comp.tex.metapost |
|---|---|
| Message-ID | <CAG5iGsDwxYt_QrH3TzTn_BV_tTivRzb_ukC8as8B+Yd_rpDspw@mail.gmail.com> |
--===============6793899259343126648== Content-Type: multipart/alternative; boundary="00000000000024c5c4060d42fab0" --00000000000024c5c4060d42fab0 Content-Type: text/plain; charset="UTF-8" On Sun, 24 Dec 2023 at 16:07, Ben Frank <[email protected]> wrote: > Dear mailing list, > > consider the following code: > > ``` > outputtemplate := "%j-%2c.mps"; > > verbatimtex %&latex > \documentclass{article} > \begin{document} > etex > > beginfig(1) > label.lft(btex \textbf{J} etex,origin); > endfig; > > end; > ``` > > Why does it not compile when fed to mpost as is (because of the space > before %&latex carrying into the output preventing its parsing as a > format comment) but compile fine when the outputtemplate line is > commented (i.e., the space seems to be gobbled as expected)? > as the result of the compilation you should have some *mpx* files in the same folder -- what do they say ? -- luigi --00000000000024c5c4060d42fab0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Sun, 24 Dec 2023 at 16:07, Ben Fra= nk <<a href=3D"mailto:[email protected]">[email protected]</a>> wrote= :<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.= 8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear mailing l= ist,<br> <br> consider the following code:<br> <br> ```<br> outputtemplate :=3D "%j-%2c.mps";<br> <br> verbatimtex %&latex<br> =C2=A0 =C2=A0\documentclass{article}<br> =C2=A0 =C2=A0\begin{document}<br> etex<br> <br> beginfig(1)<br> =C2=A0 =C2=A0label.lft(btex \textbf{J} etex,origin);<br> endfig;<br> <br> end;<br> ```<br> <br> Why does it not compile when fed to mpost as is (because of the space <br> before %&latex carrying into the output preventing its parsing as a <br= > format comment) but compile fine when the outputtemplate line is <br> commented (i.e., the space seems to be gobbled as expected)?<br></blockquot= e><div><br></div><div>as the result of the compilation you should have some= *mpx* files in the same folder -- what do they say ?</div><div><br></div><= div>--</div><div>luigi</div><div>=C2=A0</div></div></div> --00000000000024c5c4060d42fab0-- --===============6793899259343126648== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- http://tug.org/metapost/ --===============6793899259343126648==--