It's just possible that \global \mark would do the trick. Otherwise,
immediate writes and reads look like a good solution to me.
John
----- Original Message -----
From: "Paul Isambert" <zappathus...@free.fr>
To: "Unicode-based TeX for Mac OS X and other platforms" <xetex@tug.org>
Sent: 01 August 2010 08:16
Subject: Re: [XeTeX] \botmark and \firstmark not working for me ...
Selon Ron Aaron <r...@ronware.org>:
On Sunday 01 August 2010 06:23:19 Ron Aaron wrote:
> On Sunday 01 August 2010 00:47:59 John Was wrote:
> I wonder if my problem stems from the "mark" being
> inside a vbox? If that's the problem, I don't know how I would get
> around
> it ...
Argggh! That is exactly what my problem is. The "\mark{}" is inside a
"vbox". I need somehow to get it to show up in the main vertical list,
but
so
far "\vadjust" hasn't worked for me...
Indeed, the \mark won't end up on the main vertical list. In the latest
TUGboat
issue, Hans Hagen writes about this and proposes a nice solution... but
with
LuaTeX!
So to keep with XeTeX, I wonder if a two-run process wouldn't be simpler:
use
\write with an external file, which you \input on the next compilation.
But then a question: what is your \mark doing in \vbox if it is in the
"body
text", as said in your first message?
Best,
Paul
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
