From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: Hans van der Meer <havdmeer@ziggo.nl>
Cc: mailing users <ntg-context@ntg.nl>
Subject: Re: index with more than one column?
Date: Sun, 26 Aug 2018 17:54:42 +0200 [thread overview]
Message-ID: <46156d8c-db81-a0cf-3833-a8224d7c3aae@gmail.com> (raw)
In-Reply-To: <128FC472-DEAE-4656-A494-492710E71C9D@ziggo.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1828 bytes --]
Try it without the columns environment in your document, i.e.
\startchapter[title=\mytitle{Register}]
\placeregister[index]
\stopchapter
Hans van der Meer schrieb am 26.08.18 um 17:48:
> Could the following setup I used be the culprit?
>
> \setupregister[index][pagestyle=slanted,textstyle=small,alternative=A]
>
>
>> On 26 Aug 2018, at 17:43, Wolfgang Schuster
>> <wolfgang.schuster.lists@gmail.com
>> <mailto:wolfgang.schuster.lists@gmail.com>> wrote:
>>
>> The real question is why do you get an index without two columns.
>>
>> \starttext
>>
>> \dorecurse{26}{\convertnumber{a}{#1}\expanded{\index{\convertnumber{a}{#1}}}}
>>
>> \placeregister[index]%[n=3]
>>
>> \stoptext
>>
>>
>>
>> Hans van der Meer schrieb am 26.08.18 um 17:37:
>>> How do I produce an index with more than one column?
>>>
>>> This produces one column only:
>>> \startchapter[title=\mytitle{Register}]
>>> \startcolumns[n=2]
>>> \placeregister[index]
>>> \stopcolumns
>>>
>>> Nor did \placeregister[index][n=2] or \placeindex[n=2], with or
>>> without the columns envirenment, produce the result wanted.
>>> The \startsimplecolumns[n=2] environment did produce two columns,
>>> but then played havoc with the textheight.
>>>
>>> dr. Hans van der Meer
>>>
>>>
>>>
>>>
>>> ___________________________________________________________________________________
>>> 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://context.aanhet.net
>>> archive :https://bitbucket.org/phg/context-mirror/commits/
>>> wiki :http://contextgarden.net
>>> ___________________________________________________________________________________
>>
>
> met vriendelijke groet
> dr. Hans van der Meer
>
>
[-- Attachment #1.2: Type: text/html, Size: 6082 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2018-08-26 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 15:37 Hans van der Meer
2018-08-26 15:43 ` Wolfgang Schuster
[not found] ` <128FC472-DEAE-4656-A494-492710E71C9D@ziggo.nl>
2018-08-26 15:54 ` Wolfgang Schuster [this message]
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=46156d8c-db81-a0cf-3833-a8224d7c3aae@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=havdmeer@ziggo.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).