ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: [Index] Indenting long primaries after secondaries
Date: Sun, 16 Mar 2014 19:06:28 +0100	[thread overview]
Message-ID: <5325E824.8030305@wxs.nl> (raw)
In-Reply-To: <003b01cf413d$98624020$c926c060$@tosovsky@email.cz>

On 3/16/2014 6:31 PM, Jan Tosovsky wrote:
> On 2014-03-16 Hans Hagen wrote:
>>>>> On 2014-02-26 Jan Tosovsky wrote:
>>>>>>
>>>>>> when a long primary is preceded with the secondary or tertiary
>>>>>> index entry, the second line is not indented as usual, see
>>>>>> the following example:
>>>>>>
>>>>>> \setupregister[balance=no]
>>>>>> \starttext
>>>>>> \index{primary+secondary+tertiary}
>>>>>> \index[primary long]{\dorecurse{5}{primary long }}
>>>>>> \index[primary longer]{\dorecurse{5}{primary longer }} % Ok
>>>>>> \input{tufte}
>>>>>> \completeindex
>>>>>> \stoptext
>>>>>>
>>>
>>> My main wish is fixing that indentation (or offering any workaround).
>>
>> we get this:
>>
>> p
>> primary
>>     secondary
>>       tertiary 1
>> primary long primary long primary
>>     long primary long primary long 1
>> primary longer primary longer primary
>>     longer primary longer primary longer
>>     1
>>
>
> hmm, I was getting different output in ConTeXt-2014.03.07:
>
> p
> primary
>    secondary
>       tertiary 1
> primary long primary long primary
> long primary long primary long 1 (!!! this was not indented)
> primary longer primary longer primary
>    longer primary longer primary longer 1
>
> (or see the screenshot)
>
> I've just updated ConTeXt to 2014.03.16 and now it works as expected!
>
> Thanks a lot!

The register mechanism has been adapted a bit and this was probably a 
positive side effect. Some changes:

- using mixed columns
- support for: referencemethod=forward (smaller tuc files)
- more efficient interactive support (esp when no page numbers)
- better keeping entries and subentries together

Apart from that the beta has some (small) speed improvements and there 
will be a slightly different index anchoring once the new version of 
luatex is available on all platforms.

Also, the beta has slightly different low level implementation of some 
of the interactive features (which can result in more efficient pdf 
files in some cases). In fact, due to some other changes, pdf files 
could be smaller anyway.

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2014-03-16 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <019201cf331d$8bf5be80$a3e13b80$@tosovsky@email.cz>
2014-03-07 17:54 ` Jan Tosovsky
     [not found] ` <00f801cf3a2e$4f722120$ee566360$@tosovsky@email.cz>
2014-03-16 13:35   ` Hans Hagen
2014-03-16 15:34     ` Jan Tosovsky
     [not found]     ` <003001cf412d$3f2692a0$bd73b7e0$@tosovsky@email.cz>
2014-03-16 16:09       ` Hans Hagen
2014-03-16 17:31         ` Jan Tosovsky
     [not found]         ` <003b01cf413d$98624020$c926c060$@tosovsky@email.cz>
2014-03-16 18:06           ` Hans Hagen [this message]
2014-03-16 16:14       ` Hans Hagen
2014-02-26 18:07 Jan Tosovsky

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=5325E824.8030305@wxs.nl \
    --to=pragma@wxs.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).