From: Berend de Boer <berend@pobox.com>
Cc: ConTeXt List <ntg-context@ntg.nl>
Subject: Re: [Q] First work cap
Date: Tue, 13 Feb 2001 18:55:00 +0100 [thread overview]
Message-ID: <3A8974F4.60503@pobox.com> (raw)
In-Reply-To: <200102131608.RAA02669@anxur.fi.muni.cz>
Han The Thanh wrote:
>>> is it possible to make the first word of each chapter as smallcap without
>>> saying explicitly \cap{someword}?
>>
>>
>> Use \Caps.
>
>
> if I have some huge document with a lot of
>
> \chapter{abc}
> <text...>
>
> already, how can I do it without inserting \Caps to every word after a
> chapter?
Oops, didn't read your question carefully. Forget my answer. As for your
question: I don't know. Pretty hard I think.
Groetjes,
Berend. (-:
next prev parent reply other threads:[~2001-02-13 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 15:01 Han The Thanh
2001-02-13 15:19 ` Berend de Boer
2001-02-13 16:08 ` Han The Thanh
2001-02-13 17:55 ` Berend de Boer [this message]
2001-02-14 9:00 ` Hans Hagen
2001-02-14 14:51 ` Giuseppe Bilotta
2001-02-15 8:51 ` Hans Hagen
2001-02-16 10:49 ` Giuseppe Bilotta
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=3A8974F4.60503@pobox.com \
--to=berend@pobox.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).