ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Willi Egger <w.egger@boede.nl>
Subject: Re: Re: page setup
Date: Mon, 02 Feb 2004 13:33:06 +0100	[thread overview]
Message-ID: <401E4382.2070707@boede.nl> (raw)
In-Reply-To: <009101c3e933$f306d120$1301a8c0@spekoun>

[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]

Hi Vit

When using arranging one needs either to use the option --arranging 
together with texexec and therefore no \setuparranging in the file or 
put \setuparranging in the file and run it first with the 
\setuparranging command commented. This will result in a jobname.tuo 
file, which is used in a further run with the \setuparranging line 
uncommented. - With this method the problem is, that when running the 
file through texexec with the \setuparranging command uncommented for 
all runs you end up with an inappropriate jobname.tuo file. That is the 
reason why you do not get the table of contents.

When compiling your sample code with first the commented \setuparranging 
command and a final run with this line uncommented I get here:

2 sheets, first page with table of contents, the sections one and three, 
then follows a whole empty page (A4) with the mentioned 0 (zero)at the 
bottom left, the last page contains the the section two.

See also attachment.

Kind regards Willi

Vit Zyka wrote:
>>>>\setuppapersize[A5][A4,landscape]
>>>>\setuparranging[2SIDE]
>>
>>With [2SIDE], I don't get an empty page. I do get an extra page with a
>>0 down at the lower left corner. And this is annoying.
> 
> 
> Yes, I have the same observation. The "0" in left bottom corner of
> additional (and unwanted) sheet.
> 
> Perhaps it is corrected in the new beta (my ConTeXt is a half year old), but
> a) I am travelling foreign country with limited time and Internet access,
> b) I am using rather complex macro for traveller electronic journal and
> switching to new beta means complex testing if everything will work OK.
> 
> Please, can anybody with new ConTeXt check, how many pages are produced by
> next code? And if the table of contents is present?
> 
> Thanks
> Vit Zyka
> 
> (Hint: I got 3 pages (not expected 2) without table of content. Table of
> content is relaxed by using command \setuparranging.)
> 
> Code:
> ---
> \setuppapersize[A5,landscape][A4]
> \setuparranging[2TOPSIDE]
> 
> \starttext
>   Content: \placecontent
>   \switchtobodyfont[20pt]
>   \dorecurse{3}{\section{Section \recurselevel}Page \recurselevel\page}
> \stoptext
> ---
> 
> 
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

[-- Attachment #2: VitZyka.pdf --]
[-- Type: application/pdf, Size: 13466 bytes --]

  reply	other threads:[~2004-02-02 12:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-15 13:45 Hans van der Meer
2003-12-15 14:47 ` Patrick Gundlach
2004-01-06 22:20   ` Patrick Gundlach
2004-01-06 23:13     ` Steve Peter
2004-01-12  9:27       ` Patrick Gundlach
2004-02-01  5:13       ` Vit Zyka
2004-02-02 12:33         ` Willi Egger [this message]
2004-02-03 21:38           ` Vit Zyka

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=401E4382.2070707@boede.nl \
    --to=w.egger@boede.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).