From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Strange problem with Blockquote
Date: Wed, 17 Aug 2016 18:04:16 +0200 [thread overview]
Message-ID: <e5aff9e2-0e0a-8b22-7400-b464704dd41c@gmx.es> (raw)
In-Reply-To: <57387870-EFF0-471E-8667-69325904CFAB@gmail.com>
On 08/17/2016 10:55 AM, Robert Blackstone wrote:
> Hi Pablo,
>
> Thanks for your suggestion. I did try to insert this code where I
> thought I might help, though must admit that I'm not sure what to do
> with the argument [frontpart].
Hi Robert,
the command only changed the interline space in the front matter, not in
the blockquotes placed in the front part.
Sorry, because it was my fault. Today, I realized my mistake.
> In my projectfiles, admittedly rather a mess, there is nothing with the
> *name *frontpart. Anyway, with or without this or some other possibly
> more appropriate argument, nothing changed the behaviour of this, or
> rather a blockquote in this first chapter, not even surrounding the
> blockquote itself with \setupinterlinespace[small]
> ... \setupinterlinespace[reset], as I wrote in my original post.
frontpart is the sectionblock name for frontmatter. BTW, I didn’t know
it myself. Wolfgang explained to me in one of the many replies I
received from him.
A correct sample should read:
\setupinterlinespace[line=4ex]
\startsetups[interlinear:front]
\setupinterlinespace[line=2.5ex]
\stopsetups
\startsetups[interlinear:general]
\setupinterlinespace[line=5ex]
\stopsetups
\setupdelimitedtext
[blockquote]
[before={\directsetup{interlinear:general}}]
\startsectionblockenvironment[frontpart]
\setupdelimitedtext
[blockquote]
[before={\directsetup{interlinear:front}}]
\stopsectionblockenvironment
\starttext
\startfrontmatter
\dorecurse{2}{\input knuth\par
\startblockquote\input zapf\stopblockquote}
\stopfrontmatter
\startbodymatter
\dorecurse{2}{\input knuth\par
\startblockquote\input zapf\stopblockquote}
\stopbodymatter
\stoptext
But I don’t know whether the way of setting the interline space for
delimited texts is the best one.
Wolfgang, could you correct (or confirm) my previous statement?
I hope it helps now,
Pablo
--
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-17 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1081.1471393150.6154.ntg-context@ntg.nl>
2016-08-17 8:55 ` Robert Blackstone
2016-08-17 16:04 ` Pablo Rodriguez [this message]
2016-08-16 18:00 Robert Blackstone
2016-08-16 20:05 ` 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=e5aff9e2-0e0a-8b22-7400-b464704dd41c@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).