From: Michael Bynum <mdbynum@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Section format using /def
Date: Thu, 5 Feb 2009 13:45:59 -0500 [thread overview]
Message-ID: <bc3554890902051045i7da9b06ax7347aa14829d7759@mail.gmail.com> (raw)
In-Reply-To: <0E733E69-AD62-4DFC-BD9E-B415B4EF9C65@gmail.com>
Ah, I think I see. So "\define[1]\mysectionhead{\bfa
\WORD{\underbar{#1}}}" would also be valid. Is \define a context
equivalent to the \def command for tex? I couldn't find much
documentation on it.
Mike
On Thu, Feb 5, 2009 at 12:55 PM, Wolfgang Schuster
<schuster.wolfgang@googlemail.com> wrote:
>
> Am 05.02.2009 um 18:37 schrieb Michael Bynum:
>
>> I, apparently, do not understand the syntax and/or uses of /def. I am
>> trying to make section heads appear in all caps and underlined. I
>> originally tried to just use \setuphead, but found that I using the
>> "textcommand" option I could only either capitalize or underline and
>> not both. I then figured that using a macro was my next best option.
>> Below is what I tried and it does not work. Can someone tell me what
>> I am doing wrong?
>
> Both commands take parameter and in your example you pass \underbar
> as argument to \WORD.
>
> Two solution are possible for your problem.
>
> 1. You define a command with one argument and use both commands
> nested, it is important to use deeptextcommand for the \WORD style.
>
> \define[1]\mysectionhead{\underbar{\WORD{#1}}}
>
> \setuphead
> [section]
> [number=no,
> deeptextcommand=\mysectionhead,
> style={\tfa\bf}]
>
> 2. You ca use both text commands and pass one with textcommand and
> another one with deeptextcommand.
>
> \setuphead
> [section]
> [number=no,
> textcommand=\underbar,
> deeptextcommand=\WORD,
> style={\tfa\bf}]
>
> 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 : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-05 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 17:37 Michael Bynum
2009-02-05 17:55 ` Wolfgang Schuster
2009-02-05 18:45 ` Michael Bynum [this message]
2009-02-05 19:06 ` \define was: " Wolfgang Schuster
2009-02-05 17:59 ` Aditya Mahajan
2009-02-05 18:48 ` Michael Bynum
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=bc3554890902051045i7da9b06ax7347aa14829d7759@mail.gmail.com \
--to=mdbynum@gmail.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).