From: Marco Kuhlmann <lists@picoli.com>
Subject: Re: Questions/Comments
Date: Wed, 12 Sep 2001 15:58:44 +0200 [thread overview]
Message-ID: <20010912155844.A3289@wimsey> (raw)
In-Reply-To: <5.1.0.14.1.20010911183140.025dee60@server-1>
Hans Hagen wrote (2001-09-11 (18:36)):
> no, you can use \definealternativestyle [see font-ini and bet
> manual] to define a style that acts differently in normal text
> and section headers
I tried to accomplish that with
\definealternativestyle [versface]
[\versface]
[\versface]
but (a) I do not understand why one needs such definitions (it
would be appropriate for the versface style to default to these
settings) and (b) it does not get me where I want to be: now,
the headers are typeset in boldface at 100% of the requested
size, while the inline abbreviation is typeset in medium face
at 92.5% (versface). What I want is to have it typeset in bold
versface. :-) Do I really have to type
\definealternativestyle [versface]
[\versface]
[\versface\bf]
to accomplish that? But then, how do I handle cases like
blabla {\em \FOO} blabla
in normal text, where I want to be typeset in italic versface,
or even the same line in a header, where I want it to appear in
bold italic versface? It seems that I have not yet understood
how to distinguish between font commands that are "absolute"
(\versface seems to be one of those) and commands that are
"relative" (like \it).
Marco
--
Marco Kuhlmann marco.kuhlmann@gmx.net
next prev parent reply other threads:[~2001-09-12 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-10 16:57 Questions/Comments Marco Kuhlmann
2001-09-11 8:27 ` Questions/Comments Hans Hagen
2001-09-11 11:29 ` Questions/Comments Marco Kuhlmann
2001-09-11 16:36 ` Questions/Comments Hans Hagen
2001-09-12 13:58 ` Marco Kuhlmann [this message]
2001-09-14 11:10 ` Questions/Comments Hans Hagen
2001-09-14 19:39 ` Questions/Comments Marco Kuhlmann
2001-09-14 20:00 ` Questions/Comments Marco Kuhlmann
2001-09-17 16:34 ` Questions/Comments Hans Hagen
2001-09-17 16:30 ` Questions/Comments Hans Hagen
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=20010912155844.A3289@wimsey \
--to=lists@picoli.com \
--cc=marco.kuhlmann@gmx.net \
/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).