ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Malte Stien <malte@stien.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Strange errors on using setupheader
Date: Fri, 30 Mar 2012 20:35:36 +1100	[thread overview]
Message-ID: <EE02DEE3-2D7C-404D-885F-F917E1FD07D2@stien.de> (raw)

Hi again,

After I had some issues with \externalfigure, Hans suggested to me that I use a newer version of ConTeXt. So, rather than using the latest current (which seems to be from May 2011)

  ConTeXt  ver: 2011.05.18 18:04 MKIV  fmt: 2011.12.6  int: english/english

I am not using the latest beta

  ConTeXt  ver: 2012.03.29 11:28 MKIV  fmt: 2012.3.29  int: english/english

However, as it turns out, the document I am working on is no longer processed without errors. I butchered my document to isolate the error and come up with a (close to) minimal example:


% Use UTF encoding
\enableregime[utf]

% Set English as the language
\language[en]

% Select A4 as the paper size
\setuppapersize[A4]

% Setup the header...
\setupheadertexts[chapter][section]
\setupheader[leftwidth=.5\hsize, rightwidth=.4\hsize]

\starttext
\startfrontmatter
\completecontent

\chapter{Purpose and Scope}
\section[]{Purpose}
This document should be read in conjunction with bla bla bla...

\stopfrontmatter
\stoptext


I get the following error when processing with the aforementioned version:


<argument> doifelsemarking("\ascii 
                                   ")
\ctxcommand #1->\directlua \zerocount {commands.#1
                                                  }
\page_layouts_process_element_single_limited ...i 
                                                  {\limitatetext {\getmarkin...
\page_layouts_process_element_single_indeed ...#4}
                                                  \fi \endgroup 
\page_layouts_process_element_single ...#1#2#3{#4}
                                                  \fi 
<argument> ...\layoutelementparameter \c!lefttext 
                                                  \hss }\hskip -\makeupwidth...
...
l.18 \chapter{Purpose and Scope}


Strangely enough, all works well when I remove (or comment) the \setupheader line. Is there anything strange I am doing here? Should work, right?

Any pointers would be appreciated.
Thank you,
Malte.

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2012-03-30  9:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30  9:35 Malte Stien [this message]
2012-03-30  9:44 ` Hans Hagen
2012-03-30  9:47   ` Malte Stien
2012-03-30 14:17     ` Hans Hagen
2012-03-31 12:20       ` Malte Stien
2012-03-31 12:45         ` Wolfgang Schuster
     [not found] <mailman.1.1333274401.9682.ntg-context@ntg.nl>
2012-04-01 10:35 ` Malte Stien
2012-04-01 13:10   ` Hans Hagen

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=EE02DEE3-2D7C-404D-885F-F917E1FD07D2@stien.de \
    --to=malte@stien.de \
    --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).