From: Oliver Buerschaper <oliver.buerschaper@mpq.mpg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Letter backaddress
Date: Thu, 3 Jul 2008 15:04:27 +0200 [thread overview]
Message-ID: <172BF122-DD85-41FE-AD3E-2920538A34B1@mpq.mpg.de> (raw)
In-Reply-To: <115224fb0807030332i38c1aaa7s682169e753881d46@mail.gmail.com>
>> \unprotect
>>
>> \startsetups[letter:backaddress]
>> \def\\{\lettervalue{\c!backaddress\c!separator}}
>> \doifelselettervalue\v!backaddress
>> {\lettervalue\v!backaddress}
>> {\lettervalue\c!fromname
>> \doiflettervalue\c!fromaddress\\
>> \lettervalue\c!fromaddress}
>> \stopsetups
>>
>> \protect
>
> And add \setupletterstyle[backaddress=yes] to your file
> because the backaddress is disabled by default.
Thanks very much, this works!
Still a minor suggestion regarding the interface: I guess at the
moment it's slightly inconsistent because on the one hand one has
\setupletterstyle
[backaddress=yes]
and on the other hand
\setupletter
[list={name,phone,fax,date}]
Note that both commands actually implement boolean switches, namely,
whether backaddress, name etc. should be displayed or not. For
consistency reasons these switches should perhaps be interfaced in the
same way, e.g. by "name=yes" etc.
Another possibility would be removing the "backaddress=yes" switch
completely. Then if backaddress data is supplied it's printed along
with the line below and if not, well, then leave out the separator line.
What do you think?
Oliver
___________________________________________________________________________________
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:[~2008-07-03 13:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 10:23 Oliver Buerschaper
2008-07-03 10:30 ` Wolfgang Schuster
2008-07-03 10:32 ` Wolfgang Schuster
2008-07-03 13:04 ` Oliver Buerschaper [this message]
2008-07-03 13:20 ` Wolfgang Schuster
2008-07-03 15:12 ` Oliver Buerschaper
2008-07-03 15:19 ` Oliver Buerschaper
2008-07-04 6:58 ` Wolfgang Schuster
2008-07-04 7:02 ` Wolfgang Schuster
2008-07-09 6:46 ` Wolfgang Schuster
2008-07-09 7:51 ` Olivier Guéry
2008-07-09 8:06 ` Wolfgang Schuster
2008-07-09 8:18 ` Olivier Guéry
2008-07-09 8:27 ` Wolfgang Schuster
2008-07-09 8:53 ` Olivier Guéry
2010-03-26 23:45 letter: backaddress Wolfgang Werners-Lucchini
2010-03-27 1:55 ` Matija Šuklje
2010-03-27 5:48 ` Wolfgang Schuster
2010-03-27 13:51 ` Andreas Schneider
2010-03-27 14:10 ` Wolfgang Schuster
2010-03-27 15:32 ` Andreas Schneider
[not found] <mailman.94.1269703304.4277.ntg-context@ntg.nl>
2010-03-27 16:56 ` Wolfgang Werners-Lucchini
2010-03-27 18:49 ` Wolfgang Schuster
[not found] <mailman.96.1269720246.4277.ntg-context@ntg.nl>
2010-03-28 13:39 ` Wolfgang Werners-Lucchini
2010-03-28 14: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=172BF122-DD85-41FE-AD3E-2920538A34B1@mpq.mpg.de \
--to=oliver.buerschaper@mpq.mpg.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).