From: "Idris Samawi Hamid" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: quotation/blockquote bug
Date: Thu, 27 Dec 2007 16:45:43 -0700 [thread overview]
Message-ID: <op.t30pmhdbnx1yh1@your-b27fb1c401> (raw)
In-Reply-To: <20071228001522.0f9f49c4.schuster.wolfgang@googlemail.com>
On Thu, 27 Dec 2007 16:15:22 -0700, Wolfgang Schuster
<schuster.wolfgang@googlemail.com> wrote:
> Your example is too long, I could reproduce this also with the folowing
> short example.
>
> \startquotation text \quote{text} text\stopquotation
Indeed, much more to the point :-)
> The wrong right values did only appear if you use singlecommand
> quotations within a quotation environment.
>
> The push and popdelimitedtext macros did not work correct in this case
> and ConTeXt thinks there current environment is "quotation" and not
> "blockquote" when it reaches the \stopblockquote command.
>
> A group around the single quote command helps, you core macros would
> look like:
>
> \unprotect
>
> \def\delimitedtext[#1]%
> {\bgroup
> \pushdelimitedtext{#1}%
> \doifelse{\delimitedtextparameter\c!method}\s!font
> {\dofontdrivendelimited}
> {\doifinsetelse{\delimitedtextparameter\c!location}{\v!paragraph,
> \v!margin}% \dodelimitedtextpar\dodelimitedtexttxt}}
>
> \unexpanded\def\dodelimitedtextpar
> {\dohandleleftdelimitedtext\c!left\relax
> \groupedcommand
> \donothing
> {\dohandlerightdelimitedtext\c!right\removelastskip
> \popdelimitedtext
> \egroup}}
>
> \def\doquoteddelimited
> {\dohandleleftdelimitedtext\c!left\relax
> \groupedcommand
> \donothing
> {\dohandlerightdelimitedtext\c!right
> \removelastskip
> \popdelimitedtext
> \egroup}}
>
> \def\doattributeddelimited
> {\groupedcommand
> {\dostartattributes{\??ci\currentdelimitedtext}\c!style\c!color}
> {\dostopattributes
> \popdelimitedtext
> \egroup}}
>
> \protect
>
> I added in the macros above only a \bgroup in \delimitedtext and a
> \egroup in every of the other three commands.
There is a bug in here I think: ConTeXt validation gives
error in file qabas-test.tex at line 6 in column 3: missing } for {
error in file qabas-test.tex at line 10 in column 6: missing } for {
line 6 is {\bgroup
luatex eternally pauses with an apparent runaway argument....
But enclosing the whole thing {\quote{}} is a workaround.
Thank you very much for your continuous outppouring of wisdom, Wolfgang!
Best
Idris
--
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-12-27 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 21:32 Idris Samawi Hamid
2007-12-27 23:15 ` Wolfgang Schuster
2007-12-27 23:45 ` Idris Samawi Hamid [this message]
2007-12-28 0:05 ` Wolfgang Schuster
2007-12-28 1:36 ` Idris Samawi Hamid
2007-12-28 8:16 ` Taco Hoekwater
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=op.t30pmhdbnx1yh1@your-b27fb1c401 \
--to=ishamid@colostate.edu \
--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).