ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mathieu DUPONT <mathieudupont@hotmail.com>
To: ConTeXt <ntg-context@ntg.nl>
Subject: Re: Modifying the header of a Register : \setuphead or \setupregister not working
Date: Fri, 27 May 2011 15:41:52 -0400	[thread overview]
Message-ID: <COL107-W4690A067948AF6D6133DBB2760@phx.gbl> (raw)
In-Reply-To: <73C1E170-C4E4-4C02-AC81-E6BE2C1BE86C@googlemail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1789 bytes --]



This is fixing a lot of problems I had, thank you !



Mathieu



From: schuster.wolfgang@googlemail.com
Date: Fri, 27 May 2011 20:46:01 +0200
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] Modifying the header of a Register : \setuphead	or \setupregister not working




Am 27.05.2011 um 20:32 schrieb Mathieu DUPONT:Hi,
How can one modify the header of a Register, after it apparently inherited from Chapter ?In the following example, I try to have the title "INDEX" at the same height as the title "CHAPTER",but neither the \setuphead nor \setupregister commands seem to do anything.Is there another command for that ?I couldn't find it.
Thanks for help !

\setupinteraction[state=start]
\setuplabeltext[chapter=CHAPITRE~]\setuphead[chapter][	align=middle,	before={\crlf\blank[1cm-4.2ex]},	style={\blank[2cm]},	after={\blank[3cm]},	header=empty,	]
\setuphead  [chapter]  [alternative=middle,   before={\blank[force,1cm]},   numbercommand=\groupedcommand{}{\blank[2cm]},   after={\blank[3cm]},   header=empty]
\defineregister[MyIndex][MyIndexs]\setupheadtext[MyIndex=INDEX]
\setupregister[MyIndex][{\blank[0cm]}]  %% not working\setuphead[register][{\blank[0cm]}]  %% not working
Invalid setup, the second argument expects assignments.
Wolfgang


___________________________________________________________________________________
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
___________________________________________________________________________________ 		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 3884 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2011-05-27 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 18:32 Mathieu DUPONT
2011-05-27 18:46 ` Wolfgang Schuster
2011-05-27 19:41   ` Mathieu DUPONT [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=COL107-W4690A067948AF6D6133DBB2760@phx.gbl \
    --to=mathieudupont@hotmail.com \
    --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).