From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: More headache with \setuphead
Date: Sun, 01 Feb 2015 10:42:02 +0100 [thread overview]
Message-ID: <54CDF4EA.8090609@gmx.es> (raw)
In-Reply-To: <1c94794bd0abd1d50e3e64ecd2c332e6.squirrel@webmail.xs4all.nl>
On 02/01/2015 12:26 AM, Rob Heusdens wrote:
> Related post:
> section with \sethupead[section][alternative=text]; other type of section
> misbehaves..
> [...]
> Can anyone advise?
Hi Rob,
how about providing a sample that can be copied, pasted and compiled and
a brief description of what you get and what you intend?
It might be that I’m not good at reading, that my background is not
computer science, that my English is broken, or that I’m a lazy person
(or simply a jerk :-)).
Seriously, the sample avoids guesswork. Not only reconstructing the
code, but meeting the requirements you have for your document.
I think this should be your improved sample:
\define[1]\MyContentCommand%
{\framed[frame=on,offset=none,frameoffset=0pt]
{\vbox{\blank[1cm]\Word{#1}}}}
\define[2]\MyChapterCommand%
{\framed[frame=on,offset=none,frameoffset=0pt]
{\vbox{\blank[4cm]{\small \headtext{chapter}
#1}\blank\unhyphenated{#2}}}}
\setuphead[chapter]
[header=nomarking,
command=\MyChapterCommand,
aligntitle=yes,
align={flushleft,nothyphenated,verytolerant}]
\setuphead[title]
[command=,
textcommand=\MyContentCommand]
\starttext
\completecontent
\chapter{Chapter}
\stoptext
In \completecontent, the heading command is not \content but \title.
At least, it seems to work in the previous sample.
I hope it helps,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2015-02-01 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 23:26 Rob Heusdens
2015-02-01 9:42 ` Pablo Rodriguez [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=54CDF4EA.8090609@gmx.es \
--to=oinos@gmx.es \
--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).