>
>
> Thanks a lot!!! The magic apparently works. I don't understand what
> exactly the "obeylines" macro does (it seems that it just makes sure
> that none of line endings get lost, not even inside definition
> itself).
>
>
sometimes when you typeset a piece of text like poems, you actually want
On Sun, Jul 12, 2009 at 23:02, Wolfgang Schuster wrote:
> Am 12.07.2009 um 22:49 schrieb Mojca Miklavec:
>
>> This is a complete minimal example (no need for any external package).
>> It seems that \obeyMPlines or something related introduces a space
>> somewhere, and that generates an empty page.
Am 12.07.2009 um 22:49 schrieb Mojca Miklavec:
This is a complete minimal example (no need for any external package).
It seems that \obeyMPlines or something related introduces a space
somewhere, and that generates an empty page.
Why don't you use grouping then?
\def\startGNUPLOTpage
{\beg
On Sun, Jul 12, 2009 at 22:45, Hans Hagen wrote:
> Mojca Miklavec wrote:
>>
>> Hello,
>>
>> The following code works OK in mkiv, but in mkii it generates a
>> spurious empty page at the end. How can I get rid of it? (I think that
>> it used to work OK a while ago.)
>>
>> \def\startGNUPLOTpage%
>>
Mojca Miklavec wrote:
Hello,
The following code works OK in mkiv, but in mkii it generates a
spurious empty page at the end. How can I get rid of it? (I think that
it used to work OK a while ago.)
\def\startGNUPLOTpage%
{\obeyMPlines\dostartGNUPLOTpage}
\long\def\dostartGNUPLOTpage#1\st
Hello,
The following code works OK in mkiv, but in mkii it generates a
spurious empty page at the end. How can I get rid of it? (I think that
it used to work OK a while ago.)
\def\startGNUPLOTpage%
{\obeyMPlines\dostartGNUPLOTpage}
\long\def\dostartGNUPLOTpage#1\stopGNUPLOTpage%
{
Thomas A. Schmitz wrote:
Hi all,
I'm not sure if this is a bug or a feature, but I'm still having trouble
understanding the new structure code. Here is a small example:
i messed up the xml part when i added support for list/mark/bookmark
specification ... i'll fix it (and also make expansion