From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Cranky booklet layout.
Date: Thu, 27 Apr 2006 00:59:27 +0200 [thread overview]
Message-ID: <444FFB4F.2030306@wxs.nl> (raw)
In-Reply-To: <200604261653.14769.john@wexfordpress.com>
John R. Culleton wrote:
> On Wednesday 26 April 2006 07:21, John R. Culleton wrote:
>
>> On Wednesday 26 April 2006 04:42, Willi Egger wrote:
>>
>>> Hi John,
>>>
>>> Coud it be that you simply forgot the "=" after width?
>>>
>>> Willi
>>>
>> Of course. It was staring at me and I didn't see it. I missed two
>> of them in fact.
>>
>> Thanks Willi.
>>
>
> Ah I spoke too soon. The layout is OK but the TOC disapears when
> I use the \setuparranging. It works otherwise. I get a message on
> sysout:
> -------------------------------------
> output file : apr06.tuo
> remark : no output file generated
> -------------------------------------
> The apr06.tui file has the TOC entries, e.g.,
> -------------------------------------
> c \listentry{section}{1}{}{2006 Events Calendar}{2::0:0:1:0:0:0:0::25}{25}
> c \listentry{section}{2}{}{2007 Events Calendar}{2::0:0:2:0:0:0:0::25}{25}
> c \listentry{section}{3}{}{2006 Officers, Directors and Board Members}
> {2::0:0:3:0:0:0:0::25}{25}
> c \listentry{section}{4}{}{Contact Information}{2::0:0:4:0:0:0:0::25}{25}
> c \listentry{section}{5}{}{Board Meeting Minutes February 20, 2006}
> {2::0:0:5:0:0:0:0::25}{25}
> c \listentry{section}{6}{}{Brags}{2::0:0:6:0:0:0:0::25}{25}
> --------------------------------------
>
> The log file says in part:
> ---------------------------------------
> ./content.tex
> system : part,chapter,section not found/processed
> -----------------------------------------
>
> content.tex is a called subfile containing just:
> -------------------------------------------
> \startcolumns[n=2]
> \placecontent[level=section, alternative=c]
> \stopcolumns
> -------------------------------------------
>
> I use a mode to create the booklet. When I don't use the mode the
> toc is fine. Here is the mode:
> ------------------------------
> \startmode[hal]
> \definepapersize[halff][width=5.5in,height=8.5in]
> \definepapersize[ful][width=8.5in,height=11in]
> \setuppapersize[halff][ful]
> \setuparranging[2UP,rotated,doublesided]
> \setuplayout[margin=0pt,width=fit]
> \stopmode
> -------------------------------------
>
> The TOC is not absolutely critical to this particular job, but I
> would like to know what is happpening (or not happening in this
> case.)
>
>
use
texexec --arrange
which will do a normal run followed by an arrange one
(alternatively, use --once when you arrange)
Hans
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2006-04-26 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 1:02 John R. Culleton
2006-04-26 8:42 ` Willi Egger
2006-04-26 11:21 ` John R. Culleton
2006-04-26 20:53 ` John R. Culleton
2006-04-26 22:59 ` Hans Hagen [this message]
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=444FFB4F.2030306@wxs.nl \
--to=pragma@wxs.nl \
--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).