From: Ville Voipio <ville.voipio@kpatents.com>
Subject: RE: Capitalized headings
Date: Tue, 3 May 2005 19:56:19 +0300 [thread overview]
Message-ID: <98D0564335EC4848A87BEDEFF4EA056B55C1@posti.kpatents.com> (raw)
> However, this is a workaround, another way of attacking it (it can be
> better, too, stylistically, as you can change the font independently):
> \setuphead [title] [textcommand=\uppercase]
And that works, thanks!
---
The bad news is that now I have a lot more questions concerning the
heading formatting.
There are several parameters which can be used:
style
textstyle
textcommand
numberstyle
numbercommand
This is how I understand those (please, correct me when I am wrong).
Let us assume we have a chapter heading saying "Chapter 1. Title"
in the following examples:
style=\bf -> {\bf Chapter 1.}{\bf Title}
textstyle=\bf -> {Chapter 1.}{\bf Title}
numberstyle=\bf -> {\bf Chapter 1.}{\bf Title}
If I got it right this far, then I think I get these. The relevant
parts of the heading are prepended with the given commands (whatever
they then may be).
But this mechanism does work only with the commands which change the
style from that point onwards (e.g., \it, \tfx). What about the
commands which take the text as a parameter (such as \cap{text})?
And what are textcommand and numbercommand? I tried playing a bit
with them. For example, \it or \bf can be put either as textstyle=\it
or textcommand=\it. On the other hand, the \uppercase can be used
only with textstyle. So, there is a difference as the name suggests
(my initial guess was that the difference is exactly what I ask above,
but doesn't seem to be so).
Where on Earth is \uppercase explained? I tried looking for it in
the manual -- in vain. I found some references to \uppercased which
seems to be another beast.
Thank you for your patience. If the stuff is not explained in
other places, I can Wiki it once I understand it.
- Ville
next reply other threads:[~2005-05-03 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 16:56 Ville Voipio [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-03 21:32 Ville Voipio
2005-05-03 22:58 ` Adam Lindsay
2005-05-02 17:49 Ville Voipio
2005-05-02 22:53 ` Adam Lindsay
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=98D0564335EC4848A87BEDEFF4EA056B55C1@posti.kpatents.com \
--to=ville.voipio@kpatents.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).