From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: setuphead bug?
Date: Tue, 7 Oct 2014 16:40:57 +0000 [thread overview]
Message-ID: <71816EB6-DEC5-442E-9786-84C75AFE0378@uva.nl> (raw)
In-Reply-To: <0A72ABBB-3BB0-4257-BAAC-2390079D971A@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2174 bytes --]
\setuphead[chapter][align=middle] works out ok for me. Thanks!
But then, \setuphead[chapter][alternative=middle] seems quite correct, following the manual. The else seems strange then.
Hans van der Meer
On 07 Oct 2014, at 17:59, Otared Kavian <otared@gmail.com<mailto:otared@gmail.com>> wrote:
Don’t you mean rather
\setuphead[chapter][align=middle]
instead of « alternative »?
Best regards: OK
On 07 Oct 2014, at 17:28, Meer, H. van der <H.vanderMeer@uva.nl<mailto:H.vanderMeer@uva.nl>> wrote:
There seems to be a problem in \setuphead, it produces a spurious else from the alternative=middle.
In the reference manual I see the possibilities: alternative = normal inmargin middle TEXT. Of these middle is the only one giving the else.
minimal example:
\setuphead[chapter][alternative=middle]
\starttext
\startchapter[title=TITLE]
\stopchapter
\stoptext
Is there a quick repair?
ConTeXt ver: 2014.10.06 00:29 MKIV beta fmt: 2014.10.6 int: english/english
Hans van der Meer
<else-bug.pdf>___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl<mailto:ntg-context@ntg.nl> / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl<http://www.pragma-ade.nl/> / http://tex.aanhet.net<http://tex.aanhet.net/>
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net<http://contextgarden.net/>
___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl<mailto: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
___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 4038 bytes --]
[-- 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:[~2014-10-07 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 15:28 Meer, H. van der
2014-10-07 15:59 ` Otared Kavian
2014-10-07 16:40 ` Meer, H. van der [this message]
2014-10-07 19:22 ` Otared Kavian
2014-10-07 20:32 ` Wolfgang Schuster
2014-10-07 20:32 ` Wolfgang Schuster
2014-10-07 22:33 ` 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=71816EB6-DEC5-442E-9786-84C75AFE0378@uva.nl \
--to=h.vandermeer@uva.nl \
--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).