From: Ed L Cashin <ecashin@coe.uga.edu>
Cc: "ConTeXt" <ntg-context@ntg.nl>
Subject: Re: "Negative" font switches
Date: 26 Jan 2001 17:01:18 -0500 [thread overview]
Message-ID: <m3d7daug5t.fsf@coe.uga.edu> (raw)
In-Reply-To: "Giuseppe Bilotta"'s message of "Fri, 26 Jan 2001 20:31:17 +0100"
Giuseppe Bilotta <oblomov@freemail.it> writes:
> Hello, one more request: I would like to see some font switches that act by
> "nullifying" other switches. An example would explain better:
>
> {\bf Some bold {\nobf and some not bold} text}
>
> should be equivalent to
>
> {\bf Some bold} and some not bold {\bf text}
Could you give a concrete example of a situation where the "\nobf"
method is easier or clearer than the second method?
--
--Ed Cashin integrit file verification system
ecashin@coe.uga.edu http://integrit.sourceforge.net/
next prev parent reply other threads:[~2001-01-26 22:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 19:31 Giuseppe Bilotta
2001-01-26 22:01 ` Ed L Cashin [this message]
2001-01-26 22:17 ` Giuseppe Bilotta
2001-01-27 16:40 ` H. Ramm
2001-01-27 17:18 ` Marc van Dongen
2001-01-28 18:35 ` Hans Hagen
2001-01-28 18:34 ` Hans Hagen
2001-01-28 18:37 ` 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=m3d7daug5t.fsf@coe.uga.edu \
--to=ecashin@coe.uga.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).