From: Oliver Buerschaper <oliver.buerschaper@mpq.mpg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug
Date: Mon, 14 Feb 2011 12:25:44 +0100 [thread overview]
Message-ID: <86376623-10D7-4DBD-8C84-8A1882D79478@mpq.mpg.de> (raw)
In-Reply-To: <0F22F56E-6E6A-4BE7-901D-E9774DD0A61A@gmail.com>
>> here's a bug with quotations in 2011.02.11 18:18 MKIV:
>>
>> ---
>> \starttext
>> \startquotation
>> \input tufte
>> \stopquotation
>> \stoptext
>> ---
>>
>> The closing delimiter should be placed on the same line.
>
> This isn’t a bug, the included file ends the paragraph before
> \stopquotation adds the right quote and it ends up on a new line.
I was wondering because not too long ago (e.g. 2010.11.12 18:22 MKIV) this didn't happen… are included files now automatically terminated by an implicit "\par"? Personally I would find that confusing.
Oliver
___________________________________________________________________________________
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:[~2011-02-14 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 23:06 Bug Oliver Buerschaper
2011-02-13 23:25 ` Bug Wolfgang Schuster
2011-02-14 11:25 ` Oliver Buerschaper [this message]
2011-02-14 17:34 ` Bug Peter Münster
2011-02-14 22:43 ` Bug Hans Hagen
2011-02-15 9:09 ` Bug Oliver Buerschaper
2011-02-14 18:08 ` Bug Wolfgang Schuster
2011-02-14 18:13 ` Bug Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
1998-09-13 11:03 Bug Hans Hagen
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=86376623-10D7-4DBD-8C84-8A1882D79478@mpq.mpg.de \
--to=oliver.buerschaper@mpq.mpg.de \
--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).