From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Lettrine Problems
Date: Fri, 30 Sep 2005 17:57:02 +0200 [thread overview]
Message-ID: <433D604E.4010906@elvenkind.com> (raw)
In-Reply-To: <20050930144229.58673.qmail@web42108.mail.yahoo.com>
Hello,
This is one of a good many situations I am aware of where
the lettrine module fails to play nice with other parts of
ConTeXt (not unlike the LaTeX original, btw).
I never intended the module to cover any of those problem
areas, since a good number of them fall in the category
"you can't have it all", anyway.
I'll have a look, but don't get your hopes up.
Cheers, Taco
Marcus Vinicius Mesquita de So wrote:
> Problems occur with Lettrine when used with the linenumbering
> environment, the dropped cap stays outside the margin.
> Minimal example below.
next prev parent reply other threads:[~2005-09-30 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 14:42 Marcus Vinicius Mesquita de So
2005-09-30 15:57 ` Taco Hoekwater [this message]
2005-10-03 8:00 ` Taco Hoekwater
2005-10-03 16:20 ` Marcus Vinicius Mesquita de So
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=433D604E.4010906@elvenkind.com \
--to=taco@elvenkind.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).