From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Strange problem with Blockquote
Date: Tue, 16 Aug 2016 22:05:02 +0200 [thread overview]
Message-ID: <008693ad-e1f3-7fb0-0231-bca27c1eb3e1@gmx.es> (raw)
In-Reply-To: <9A4BE7B6-27DD-41C7-8E20-0AA161209846@gmail.com>
Hi Robert,
from what I get from your message, there is only one blockquote in the
introduction.
How about adding the following code before \starttext?
\startsectionblockenvironment[frontpart]
\setupinterlinespace[small] % or whichever value you want
\stopsectionblockenvironment
I think it might work. I hope it helps,
Pablo
On 08/16/2016 08:00 PM, Robert Blackstone wrote:
> Dear all,
>
> I have a small but nasty problem with the book I’m (still) working
> on.
>
> Its 10 chapters contain many Blockquotes, and they all come out as
> intended except one, in the first, unnumbered, chapter “Introduction".
> That particular blockquote v]comes out like the others only as far as
> its width and its fontsize are concerned, but unlike the others it
> insists on keeping the same interline distance as the main text. Even
> that would not have been too much of a problem if it had not spoiled the
> layout by pushing a rather large float off the page, leaving a large gap.
>
> This particular chapter is input by means of the Frontmatter file,
> as is Ch1, which also contains several Blockquotes, that come out OK.
>
> When I process this chapter “Introduction" separately with the same
> setups the blockquote also comes out allright.
> When, as a test, I input that chapter again, the second time through
> the Bodymatter, then again it comes out allright (while the blockquote
> in the real Ch0 keeps its large interline distance).
>
> I have tried the following:
> - add the setup for the blockquote to the Frontmatter file
> - add the setup for the blockquote also to the Ch0 file itself
> - add \setupinterlinespace[small] in the text just before the blockquote
> and \setupinterlinespace[reset] after it.
> None of this has changed the interline distance of the blockquote one bit.
>
> Is there anybody on this list for whom this problem is or sounds
> familiar and who knows a remedy?
> If not, which information would I have to give to make a diagnosis
> possible?
> (It may be evident that it is impossible to show the problem in an
> MWE.)
>
> Thanks in advance for any help.
>
> Best regards,
> Robert Blackstone
--
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-08-16 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 18:00 Robert Blackstone
2016-08-16 20:05 ` Pablo Rodriguez [this message]
[not found] <mailman.1081.1471393150.6154.ntg-context@ntg.nl>
2016-08-17 8:55 ` Robert Blackstone
2016-08-17 16:04 ` Pablo Rodriguez
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=008693ad-e1f3-7fb0-0231-bca27c1eb3e1@gmx.es \
--to=oinos@gmx.es \
--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).