From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/114331
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: jbf via ntg-context <ntg-context@ntg.nl>
Newsgroups: gmane.comp.tex.context
Subject: sorting for particular sub entries to register
Date: Tue, 1 Feb 2022 09:35:56 +1100
Message-ID: <f420006f-7779-4ed8-75c7-b68a3e373f07@gmail.com>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1756196955946858761=="
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="20871"; mail-complaints-to="usenet@ciao.gmane.io"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
Cc: jbf <roma83537@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Original-X-From: ntg-context-bounces@ntg.nl Mon Jan 31 23:36:45 2022
Return-path: <ntg-context-bounces@ntg.nl>
Envelope-to: gctc-ntg-context-518@m.gmane-mx.org
Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl)
	by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ntg-context-bounces@ntg.nl>)
	id 1nEfHw-0005E6-DY
	for gctc-ntg-context-518@m.gmane-mx.org; Mon, 31 Jan 2022 23:36:44 +0100
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id AE8D828968E;
	Mon, 31 Jan 2022 23:36:06 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4s7-CzeqnZZE; Mon, 31 Jan 2022 23:36:05 +0100 (CET)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id EDC4E289809;
	Mon, 31 Jan 2022 23:36:04 +0100 (CET)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 05B51289687
 for <ntg-context@ntg.nl>; Mon, 31 Jan 2022 23:36:03 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id x3ZqVtL68cNK for <ntg-context@ntg.nl>;
 Mon, 31 Jan 2022 23:36:02 +0100 (CET)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.215.175;
 helo=mail-pg1-f175.google.com; envelope-from=roma83537@gmail.com;
 receiver=<UNKNOWN> 
Original-Received: from mail-pg1-f175.google.com (mail-pg1-f175.google.com
 [209.85.215.175])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits))
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id B6AE5282AF1
 for <ntg-context@ntg.nl>; Mon, 31 Jan 2022 23:36:01 +0100 (CET)
Original-Received: by mail-pg1-f175.google.com with SMTP id p125so13588943pga.2
 for <ntg-context@ntg.nl>; Mon, 31 Jan 2022 14:36:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=message-id:date:mime-version:user-agent:content-language:to:from
 :subject; bh=iYrXK84vARwiDBx+iRsCnvKumQPLAobs3/22L5T2BIc=;
 b=X7evJiJU40NEtsFYc4sx6leZWBznYk/Oi4DPO3rqkAVbY/KHp2kzv+8FHdogDBPEFd
 JcL+p+UR4NMa5CMKXZQ9IC9u6L5agyIDC8Z4B48gRAOEa/4+rXRCNMTNQJ+rOM1PAn9a
 9BOYBRSY2MhdhKx5yudqp9wYDLXilTbXELFBEITrwmF0ciFaVu+0vY3AWgWhUVo5gOy8
 SzynVWetWdKMrzwZsibWsc81kQOpqc7W0TGQfVKqE/WgDgQhobbzngMVsx4lsEGNGZMk
 jOUxtT8zZ6nhF7GB3ZUxnJZgGhkxRHpTbbtKNl6pDreESsEbPNLNZE+sRw6SDK4LZGRC
 uDjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:message-id:date:mime-version:user-agent
 :content-language:to:from:subject;
 bh=iYrXK84vARwiDBx+iRsCnvKumQPLAobs3/22L5T2BIc=;
 b=39J63BYLfmO+hHCMhL8WhMtUMoFkNVRIxX/mRCxu4Qeku3m4gU2ouOcvaVV+weWuJV
 3OsNjHPNy/htu32wmR8dqRgtxS95JSpM4dC6y2DN7doT/XhPRLLLitidTyGiNO4Fkln8
 HkRjwURnBCSwPfISmxZEGQFF2emFxWlPoNtTDtIEcZekOjXcjH8Q697ZTbRqy3rOUM3r
 oWRjJuwdguke+q52n10I/j8s2IHch5CwdeFJKoiIbUIQY7PR9AQA2Z55DxCRb5Jp1WZ8
 witt6k+ugfOy7G4TW34ZZUKwZ1nA73u6CpOZ9dBPNfxcn6fwLeX2kYQEGtAcEJrV70c3
 ERjA==
X-Gm-Message-State: AOAM531tcgKIX1HtACulrOXhxjIBW5HHRyiLJrLIMYEVI0wTrHsJmWqj
 C4IAKNmPlaEKyOPYcIIjRPXVzFYqsZo=
X-Google-Smtp-Source: ABdhPJzD1qyqDP3/NzrqCxjjtFRg3SumfEpBwZiSq8vUHViUJsrrm2cIoaY1l3foiySAWc44+SCitQ==
X-Received: by 2002:a63:2a95:: with SMTP id
 q143mr18621021pgq.492.1643668559497; 
 Mon, 31 Jan 2022 14:35:59 -0800 (PST)
Original-Received: from [192.168.0.100] ([120.21.109.121])
 by smtp.gmail.com with ESMTPSA id o7sm17976198pfk.184.2022.01.31.14.35.58
 for <ntg-context@ntg.nl>
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Mon, 31 Jan 2022 14:35:59 -0800 (PST)
Content-Language: en-US
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
Errors-To: ntg-context-bounces@ntg.nl
Original-Sender: "ntg-context" <ntg-context-bounces@ntg.nl>
Xref: news.gmane.io gmane.comp.tex.context:114331
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/114331>

This is a multi-part message in MIME format.
--===============1756196955946858761==
Content-Type: multipart/alternative;
 boundary="------------cIYyTsj0ZY5cc0QBKsNQdE53"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------cIYyTsj0ZY5cc0QBKsNQdE53
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Let me come back to the unresolved (for me) question of two situations 
in sub entries to a book index (register). Sub entries that have 
formatting or sub entries that are surrounded by quote marks (straight 
or curly, it makes no difference) do not appear in the correct 
alphabetical order.

Two attempts on my part:

text before \index[Plenary+periti]{Plenary Council+{\it periti} 
(experts)} text after.

text before \index{animals+‘special kinds’} text after. Or 
alternatively, \index[animals+special]{animals+‘special kinds’}

The setup for my register is a pretty standard one. The processor is not 
for the 'periti' case above but I use it for book titles.

\setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD]

\defineprocessor[special][style=italic]

In the periti case it is the \it command that clearly interferes with 
correct alphabetic positioning in the sub entry list. Placing +periti in 
the key does not overcome that problem.

In the ‘special kinds’ case it is the initial single quote mark (‘) that 
causes the problem. The item comes last in the sub entry list. And if i 
include a key [special], then it comes first in the sub entry list. 
Either way, it is out of the desired sorting order.

I believe I have followed the helpful suggestions of various ones, but 
it is always possible that I have not fully understood those 
suggestions. The reality is that at the moment the issue remains 
unresolved for me. Any further wisdom out there to offer me?

Julian

--------------cIYyTsj0ZY5cc0QBKsNQdE53
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Let me come back to the unresolved (for me) question of two situations in sub entries to a book index (register). Sub entries that have formatting or sub entries that are surrounded by quote marks (straight or curly, it makes no difference) do not appear in the correct alphabetical order.</p>
    <p>Two attempts on my part:</p>
    <p>text before \index[Plenary+periti]{Plenary Council+{\it periti}
        (experts)} text after.</p>
    <p>text before \index{animals+‘special kinds’} text after. Or alternatively, \index[animals+special]{animals+‘special kinds’}</p>
    <p>The setup for my register is a pretty standard one. The processor is not for the 'periti' case above but I use it for book titles.<span style=" color:#000000;"></span></p>
    <pre style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" color:#800000;">\setupregister</span><span style=" color:#000000;">[index][n=1,method={</span><span style=" text-decoration: underline; color:#000000;">zc</span><span style=" color:#000000;">,pc,</span><span style=" text-decoration: underline; color:#000000;">zm</span><span style=" color:#000000;">,pm,</span><span style=" text-decoration: underline; color:#000000;">uc</span><span style=" color:#000000;">},style=WORD]</span></pre>
    <pre style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" color:#800000;">\defineprocessor</span><span style=" color:#000000;">[special][style=italic]</span></pre>
    <p><style type="text/css">p, li { white-space: pre-wrap; }</style></p>
    <p>In the periti case it is the \it command that clearly interferes with correct alphabetic positioning in the sub entry list. Placing +periti in the key does not overcome that problem.</p>
    <p>In the ‘special kinds’ case it is the initial single quote mark (‘) that causes the problem. The item comes last in the sub entry list. And if i include a key [special], then it comes first in the sub entry list. Either way, it is out of the desired sorting order.</p>
    <p>I believe I have followed the helpful suggestions of various ones, but it is always possible that I have not fully understood those suggestions. The reality is that at the moment the issue remains unresolved for me. Any further wisdom out there to offer me?</p>
    <p>Julian
</p>
    <p><style type="text/css">I believe I have followed the helpful suggestions from variousp, li { white-space: pre-wrap; }</style></p>
  </body>
</html>

--------------cIYyTsj0ZY5cc0QBKsNQdE53--

--===============1756196955946858761==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz
dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h
aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s
aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv
IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v
cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn
YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg==

--===============1756196955946858761==--