From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Bug with \quotation ?
Date: Sun, 03 Dec 2006 15:03:07 +0100 [thread overview]
Message-ID: <4572D91B.3040506@elvenkind.com> (raw)
In-Reply-To: <725B1506-A3B1-4880-9CC6-63D7D1DEF630@uni-bonn.de>
Thomas A. Schmitz wrote:
> Hi all,
>
> there seems to be a bug with the \quotation command: ConTeXt doesn't
> break the line after the closing quotes it generates. Here's a small
> test file showing the problem (hope the utf-encoding makes it through
> the mail):
...
>
> I tried reading core-mis.tex, but wasn't able to find where this
> behavior comes from.
This is tricky: at the end of the quoted material, the sequence is
<rightquotationsymbol>
\penalty10000
\hskip\delimitedtextsignal
<a space>
<S>
And that sequence does not actually allow a line break (thanks to the
\penalty10000). A number of low-level hacks is possible, but I am not
sure which one is best.
Something like this redefinition works (the penalty is new):
\definedelimitedtext
[quotation]
[left={\symbol[leftquotation]},
right={\symbol[rightquotation]\penalty0 },
leftmargin=standard]
Best, Taco
prev parent reply other threads:[~2006-12-03 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 22:38 Thomas A. Schmitz
2006-12-03 14:03 ` Taco Hoekwater [this message]
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=4572D91B.3040506@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).