From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Beta: bug in \setuphead[chapter]
Date: Tue, 3 Jan 2012 08:05:32 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.02.1201030759090.11181@nqv-gnoyrg> (raw)
In-Reply-To: <63847A47-0EA0-418C-BB6A-B190990CDD98@gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 778 bytes --]
On Tue, 3 Jan 2012, Otared Kavian wrote:
> On 3 janv. 2012, at 08:38, Wolfgang Schuster wrote:
>
>> […]
>> You need a command after “align=middle” because you assign “middle ” (with a space) to the align key.
>
> I didn't get exactly what you mean, but saying either of the following:
I have not checked why the extra space is being introduced, but what
Wolfgang meant was that
\setup<whatever>[key=value]
is the same as
\setup<whatever>
[
key=value,
]
but not the same as
\setup<whatever>
[
key=value
]
Whitespace is significant in ConTeXt setups. The last style is equivalent
to
\setup<whatever>[key={value\n}]
and that could be the reason that you are seeing extra space.
Aditya
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2012-01-03 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 5:41 Otared Kavian
2012-01-03 7:38 ` Wolfgang Schuster
2012-01-03 12:58 ` Otared Kavian
2012-01-03 13:05 ` Aditya Mahajan [this message]
2012-01-03 13:06 ` Wolfgang Schuster
2012-01-03 13:17 ` Otared Kavian
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=alpine.LNX.2.02.1201030759090.11181@nqv-gnoyrg \
--to=adityam@umich.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).