From: Guy Worthington <guyw@multiline.com.au>
Subject: Re: Indenting in description
Date: 27 Feb 2003 10:39:09 +0800 [thread overview]
Message-ID: <uwujm8n1u.fsf@multiline.com.au> (raw)
In-Reply-To: <20030226195520.20b09278.md9per@mdstud.chalmers.se>
Mikael Persson wrote:
> When I have descriptions that are longer than one paragraph I want
> the next paragraphs indented in the same way as the other parts of
> the document.
If you're looking for an elegant way to do this then stop reading now.
You can, with a bit of brute force and ignorance, reset the \parindent
dimension from within your description environment by reissuing the
imperative \setupindenting[medium]:
-----
\setupindenting[medium]
\indenting[yes]
\definedescription[testdesc][%
width=broad,
location=serried,
headstyle=bold,
way=bychapter,
text={Testdescription: }]
\starttext
\section{Some indenting tests}
...
\starttestdesc{A nonlucky one}
This is just a test paragraph. I want to se if the next paragraph is
indented or not. So, sooner or later we will know.
\setupindenting[medium] % <-- add this
Is this indented? No, but I want it to be.
\stoptestdesc
...
\stoptext
-----
> I also have another question. How can one install Math fonts (lucida)?
> When I run texfont as with other fonts texfont reports that it is math
> fonts and the installation fail. Should I add another switch? (I tried
> with the same switches as I successfully use for other fonts, that is
> --in and --ma (besides the --ve and --co))
Hans Hagen has done all the hard stuff already, so you can install the
lucida Math fonts by doing nothing. (Well that's not quite true, I
had to lowercase the .pfb binaries and .tfm metrics in the lucida math
collection). So for instance, I simply copied the file lbma.pfb over
into my type1 directory, and similarly I copied lbma.tfm into my tfm
directory.
next prev parent reply other threads:[~2003-02-27 2:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 18:55 Mikael Persson
2003-02-27 2:39 ` Guy Worthington [this message]
2003-02-27 8:46 ` Mikael Persson
2003-02-27 9:10 ` Re[2]: " Giuseppe Bilotta
2003-02-27 18:00 ` Hans Hagen
2003-02-27 18:26 ` Mikael Persson
2003-02-28 7:44 ` Hans Hagen
2003-02-28 9:29 ` Mikael Persson
2003-03-05 8:23 ` Coydell Rivers
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=uwujm8n1u.fsf@multiline.com.au \
--to=guyw@multiline.com.au \
--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).