From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/114333 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: jbf via ntg-context Newsgroups: gmane.comp.tex.context Subject: Re: sorting for particular sub entries to register Date: Tue, 1 Feb 2022 11:41:22 +1100 Message-ID: References: Reply-To: mailing list for ConTeXt users Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2894823316624046516==" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40726"; 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 , mailing list for ConTeXt users To: Adam Reviczky Original-X-From: ntg-context-bounces@ntg.nl Tue Feb 01 01:42:12 2022 Return-path: 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 ) id 1nEhFM-000AL6-DH for gctc-ntg-context-518@m.gmane-mx.org; Tue, 01 Feb 2022 01:42:12 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 92A74289710; Tue, 1 Feb 2022 01:41:38 +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 J2C4YL2MX5wD; Tue, 1 Feb 2022 01:41:36 +0100 (CET) Original-Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 88EE9289756; Tue, 1 Feb 2022 01:41:36 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 3C33428971D for ; Tue, 1 Feb 2022 01:41:35 +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 O-mduN5O8EG4 for ; Tue, 1 Feb 2022 01:41:31 +0100 (CET) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.210.170; helo=mail-pf1-f170.google.com; envelope-from=roma83537@gmail.com; receiver= Original-Received: from mail-pf1-f170.google.com (mail-pf1-f170.google.com [209.85.210.170]) (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 1D80B289710 for ; Tue, 1 Feb 2022 01:41:30 +0100 (CET) Original-Received: by mail-pf1-f170.google.com with SMTP id u130so14358508pfc.2 for ; Mon, 31 Jan 2022 16:41:30 -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:subject:content-language:to :references:cc:from:in-reply-to; bh=4S92bN9yWV7SQNkK2kfVDBVLiJPSkAnUNvIefnLrONg=; b=grgpglbSD91l8lVTqvr1S/82McLydUmNhygPC5hczPVY9/LYIxzQYKWa/VvGHoythW 2Kz3XwMWH3EkcBD3BfGQ5P5hwTR+mXoW2+1n78zchahDNd20ZUR/DtVLwb9xgMrmvKDp Q/wg7XcAAN5bWJ6433wRqqkTkwbtR86OppENtK9IMBcobh5I1oTx8zjXTepGfPm5ew2G 6vBfyV1XpmkiZQ6EGBoqkjun6JMGxzGAFT6hb6UquUIcAAck/gXdoZGoSfG0bHCHO1Xe uSzn05DUvqWPSN38H3ZZCq9bIp3t27n+nX0AUz1lYIBGH4bAfmUkVk2CpLqx8tiOb/+m W1Rg== 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:subject :content-language:to:references:cc:from:in-reply-to; bh=4S92bN9yWV7SQNkK2kfVDBVLiJPSkAnUNvIefnLrONg=; b=gFl50NMZE5wWOARDnhy54+eI5us9++5Tys3ihp5z7zj8aixAD9rrkIB0CfhRpHopS9 rSVj3EpDHhaWI6ewIsuc4Hsf+J6lEy/0hm3aYxcbHzkR9hHll5/UOlaXEp+eFLZU/qFF N8Xo7CP8UYs8Oo3iru6TuqY5x7iOZzpkOGGhb0zG07UcuGc2Fulwv5Of2TQzrKDpdEZt ZRlHYpPHPHGoQV+ylIIb+ZLOD9pyGveKOUjjfThNAZLhcPQKkRiKXSsPeWIdz52z1qfA TDNQLZ7HyvpK9+l9f8E376QQ2B/af2Fg4u9KIp/5E5m2XSVXrNz18q0etn0C/zARhd15 y4qQ== X-Gm-Message-State: AOAM532R8edHYNl5xAKyh9jvY8JQpopTenSufm2Vm8T2FFw7rf48QS5X 15f+dO27tf9wKC1WG5Ck2qm/HKNZJnQ= X-Google-Smtp-Source: ABdhPJzCjFtoIESLWaalLjsec9D7VClwGnWJTEmPEX9M01v81HbNKYErvsax3ZfpVZjSi64S8kH4VQ== X-Received: by 2002:a05:6a00:2490:: with SMTP id c16mr23054604pfv.36.1643676086358; Mon, 31 Jan 2022 16:41:26 -0800 (PST) Original-Received: from [192.168.0.100] ([120.21.109.121]) by smtp.gmail.com with ESMTPSA id e14sm19995129pfv.219.2022.01.31.16.41.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 31 Jan 2022 16:41:26 -0800 (PST) Content-Language: en-US In-Reply-To: X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.26 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.io gmane.comp.tex.context:114333 Archived-At: This is a multi-part message in MIME format. --===============2894823316624046516== Content-Type: multipart/alternative; boundary="------------g2DWpNbuDb0KA34EY4w0QSjs" Content-Language: en-US This is a multi-part message in MIME format. --------------g2DWpNbuDb0KA34EY4w0QSjs Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Yes, Adam, that works. Though it can be a laborious solution, since it means creating keys for everything in a sub entry list (and I have many instances, 40 or more in some cases). However, I did not ask for a 'simple' solution, just a solution! Thank you. Julian On 1/2/22 11:09, Adam Reviczky wrote: > Hi Julian, > > How about using the keys in every instance? > > \setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD] > \defineprocessor[special][style=italic] > > \starttext > P\index[Plenary+periti]{Plenary Council+{\it periti} (experts)} > B\index[Plenary+beriti]{Plenary Council+{\it beriti} (experts)} > A\index[Plenary+aeriti]{Plenary Council+aeriti (experts)} > > S\index[animals+special]{animals+‘special kinds’} > B\index[animals+bpecial]{animals+bpecial} > A\index[animals+apecial]{animals+‘apecial’} > U\index[animals+upecial]{animals+‘upecial’} > T\index[animals+tpecial]{animals+tpecial} > > \placeindex > \stoptext > > See result in: https://live.contextgarden.net/cgi-bin/result.cgi?id=j46XhZ > > Adam > > On Mon, Jan 31, 2022 at 10:38 PM jbf via ntg-context > wrote: > > 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 > > ___________________________________________________________________________________ > 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 > ___________________________________________________________________________________ > --------------g2DWpNbuDb0KA34EY4w0QSjs Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Yes, Adam, that works. Though it can be a laborious solution, since it means creating keys for everything in a sub entry list (and I have many instances, 40 or more in some cases). However, I did not ask for a 'simple' solution, just a solution! Thank you.

Julian

On 1/2/22 11:09, Adam Reviczky wrote:
Hi Julian,

How about using the keys in every instance?

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

\starttext
P\index[Plenary+periti]{Plenary Council+{\it periti} (experts)}
B\index[Plenary+beriti]{Plenary Council+{\it beriti} (experts)}
A\index[Plenary+aeriti]{Plenary Council+aeriti (experts)}

S\index[animals+special]{animals+‘special kinds’}
B\index[animals+bpecial]{animals+bpecial}
A\index[animals+apecial]{animals+‘apecial’}
U\index[animals+upecial]{animals+‘upecial’}
T\index[animals+tpecial]{animals+tpecial}

\placeindex
\stoptext


Adam

On Mon, Jan 31, 2022 at 10:38 PM jbf via ntg-context <ntg-context@ntg.nl> wrote:

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

___________________________________________________________________________________
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
___________________________________________________________________________________
--------------g2DWpNbuDb0KA34EY4w0QSjs-- --===============2894823316624046516== 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== --===============2894823316624046516==--