From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Macro for acronyms
Date: Sat, 19 Mar 2011 00:37:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1103190036040.29679@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <AANLkTinRq=Zw28FguVdior0Ggssz2gEuHWV70HZmfK4-@mail.gmail.com>
On Sat, 19 Mar 2011, Cecil Westerhof wrote:
> 2011/3/19 Aditya Mahajan <adityam@umich.edu>
>
>> On Sat, 19 Mar 2011, Cecil Westerhof wrote:
>>
>> At the moment I have I my document:
>>> {\switchtobodyfont[1.25em]\bf M}ust
>>>
>>> {\switchtobodyfont[1.25em]\bf S}hould
>>>
>>> {\switchtobodyfont[1.25em]\bf C}ould
>>>
>>> {\switchtobodyfont[1.25em]\bf N}ot now
>>>
>>> But I like to have a macro for this, so I could just do:
>>> \Acronym{Must Should Could Not~now}
>>>
>>> Is more readable and when I want a change (for example another color for
>>> the
>>> first letter), this is much easier to implement. How should I implement
>>> such
>>> a macro?
>>>
>>
>>
>> Use recursion!
>>
>> \definestartstop
>> [FancyFirstLetter]
>> [style={\switchtobodyfont[big]\bf},
>> color=red]
>>
>> \def\FancyUppercase#1%
>> {\dostartFancyUppercase#1\dostopFancyUppercase}
>>
>> \def\dostartFancyUppercase#1#2\dostopFancyUppercase
>> {\FancyFirstLetter{#1}#2}
>>
>>
>> \def\Acronym#1%
>> {\dostartAcronym#1 \dostopAcronym}
>>
>> \def\dostartAcronym#1 #2\dostopAcronym
>> {\doifsomething{#1}
>> {\FancyUppercase{#1} %space
>> \dostartAcronym#2 \dostopAcronym}}
>
>
> Almost. dostartAcronym needs a blanco line to put the words under
> each-other:
Better to use an explicit \blank (A blank space is equal to \par, and can
give funny results when you change indenting)
> \def\dostartAcronym#1 #2\dostopAcronym
> {\doifsomething{#1}
> {\FancyUppercase{#1} %space
. \blank% addied this
> \dostartAcronym#2 \dostopAcronym}}
>
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-03-19 4:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 2:29 Cecil Westerhof
2011-03-19 3:08 ` Aditya Mahajan
2011-03-19 4:00 ` Cecil Westerhof
2011-03-19 4:37 ` Aditya Mahajan [this message]
2011-03-19 4:54 ` Cecil Westerhof
2011-03-19 9:30 ` Wolfgang Schuster
2011-03-19 9:22 ` Wolfgang Schuster
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=alpine.LNX.2.01.1103190036040.29679@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).