From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/114323
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: Re: registers, how to ignore quote marks
Date: Mon, 31 Jan 2022 07:55:38 +1100
Message-ID: <fd66a3f3-a699-0322-fca2-534e754992e6@gmail.com>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1164429868670234947=="
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="14183"; 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 Sun Jan 30 21:56:17 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 1nEHFB-0003Vc-3k
	for gctc-ntg-context-518@m.gmane-mx.org; Sun, 30 Jan 2022 21:56:17 +0100
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 7A01F2A2786;
	Sun, 30 Jan 2022 21:55:50 +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 pIKKLhZplLA9; Sun, 30 Jan 2022 21:55:47 +0100 (CET)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 88DC82A257D;
	Sun, 30 Jan 2022 21:55:47 +0100 (CET)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 90FEB2A2780
 for <ntg-context@ntg.nl>; Sun, 30 Jan 2022 21:55:46 +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 lzYp8QaMUldf for <ntg-context@ntg.nl>;
 Sun, 30 Jan 2022 21:55:45 +0100 (CET)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.216.43;
 helo=mail-pj1-f43.google.com; envelope-from=roma83537@gmail.com;
 receiver=<UNKNOWN> 
Original-Received: from mail-pj1-f43.google.com (mail-pj1-f43.google.com
 [209.85.216.43])
 (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 6DA5BE77
 for <ntg-context@ntg.nl>; Sun, 30 Jan 2022 21:55:45 +0100 (CET)
Original-Received: by mail-pj1-f43.google.com with SMTP id
 s2-20020a17090ad48200b001b501977b23so16267974pju.2
 for <ntg-context@ntg.nl>; Sun, 30 Jan 2022 12:55:45 -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=CnBaHJN5urg1lKJF9ck8mO00OK5ECssVvgnqD8m7siA=;
 b=UfbImWBlSuoBY42ne2Ib6aKrvgl465ZtsrkOY3z92na6xSNWH2+EzTuYkUdw0Pkfma
 9fKzZ+6TL8HJhi9rYGqdka4ZLgxVWqUTxnbscGILob59Hd73t64ESRyvU5mM7KQ9fxLv
 iHtiT01cRLo72J/RilwahBgWYrgpDGw0lFevI95HI5EkoNvMLgyuau7Fm2qFNXBNV5f/
 VubVn9AeRzDIi+S474QgADmVnCOXw2fYkcZgBhRIfzsuWRYf3RsIX/3mgip+k5r7pH5o
 3YbHivFSXd7Df2TNUSIXaEg5DXC/PpoUWi/M1XYsNQ96Wi5Feqp6pf06s/GvWR0LwJnH
 z+yw==
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=CnBaHJN5urg1lKJF9ck8mO00OK5ECssVvgnqD8m7siA=;
 b=QiDML04AelVnauP2NemyajeigLnhtu8EVWYcvA3TZMahzvheoy7lGVCPJH0dZ7p/2A
 kIaVK5Tzp6nWJmllA+aONMsONfUY/Vi3NpH9NmBIk7Zd2LMYZOA/ns763g/bHcTx8R+8
 bMzz+eDXcK1RIxryk6v+8TJhUJbnmXiBSk23VkUkl+M0NsvL+fGAxWDhQ0aPWHtOUWLo
 9cP3Mgo9jUpejK2n0eG2cLyA80h0jqAUt7CYYku5KMysMq/Y84oTV00Z835VboLzED5F
 4ZiMQIWms5UnV2BU4TIFGRM5b66aK0PJC0gfSPx/GhuXWlgpsa9l0QYibLAnSVgQZtCN
 9Zow==
X-Gm-Message-State: AOAM532yuFdzCDcwfPG05DkMgdE/pxd6gKzn2bS44M0uygOADiX7fVqc
 gbT7G7GaWnY4Z27XLSJ/gYEOu2DarSk=
X-Google-Smtp-Source: ABdhPJzf/A9n9VTQwbC10MRDrl221U5xWWMdcZgMQKlaQC37kgHojPMU0sou2AzHPyBcVrBRHG+alw==
X-Received: by 2002:a17:90b:2245:: with SMTP id
 hk5mr21114741pjb.73.1643576142230; 
 Sun, 30 Jan 2022 12:55:42 -0800 (PST)
Original-Received: from [192.168.0.100] ([120.21.109.121])
 by smtp.gmail.com with ESMTPSA id lk8sm9362167pjb.40.2022.01.30.12.55.41
 for <ntg-context@ntg.nl>
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Sun, 30 Jan 2022 12:55:42 -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:114323
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/114323>

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

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

No, I had already tried that. It places the subentry at the top of the 
list of subentries, not in its correct alphabetical order. Using the 
example below, I assume you meant (I am including text before and after):

The \index[Plenary+periti]{Plenary Council+{\it periti} (experts)} group 
comprises 10 members.

There are nine subentries altogether, and quite a number under 'p', like 
\index{Plenary Council+preparations for}. The italicised /periti /should 
come just before the latter (preparations for) but, using the double key 
above it comes first in the list. The same happens with the subentry 
surrounded by single quotes. It too comes first in the list if I use a 
double key. So clearly it is the fact that there is formatting ({\it 
something}) or quotes ({‘word’}) in a subentry that causes the problem, 
and I am wondering how to overcome this.

Julian

On 30/1/22 20:59, Hans Hagen wrote:
>> 2. \index{Plenary Council+{\it periti} (experts)}: in this case it is 
>> the italicised /periti/ that appears out of place, after the letter 
>> 'i' rather than after 'p'. Again I tried putting various keys but 
>> this did not help.
>>
>> I guess my confusion is this: I assumed that the [key] establishes 
>> the literal string which determines sort order. That seems to be the 
>> case for a main entry. How do I get it to work for a subentry?
> just provide an extra key: 
--------------UUHfgrOSnNQBxMFZuFj5HJ8P
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>
    <div class="moz-text-html" lang="x-unicode">
      <p>No, I had already tried that. It places the subentry at the top
        of the list of subentries, not in its correct alphabetical
        order. Using the example below, I assume you meant (I am
        including text before and after):</p>
      <p>The \index[Plenary+periti]{Plenary Council+{\it periti}
        (experts)} group comprises 10 members.</p>
      <p>There are nine subentries altogether, and quite a number under
        'p', like \index{Plenary Council+preparations for}. The
        italicised <i>periti </i>should come just before the latter
        (preparations for) but, using the double key above it comes
        first in the list. The same happens with the subentry surrounded
        by single quotes. It too comes first in the list if I use a
        double key. So clearly it is the fact that there is formatting
        ({\it something}) or quotes ({‘word’}) in a subentry that causes
        the problem, and I am wondering how to overcome this.</p>
      <p>Julian<br>
      </p>
      <div class="moz-cite-prefix">On 30/1/22 20:59, Hans Hagen wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:7eced3d3-604f-35f9-a85b-bef9e5345b47@xs4all.nl">
        <blockquote type="cite" style="color: #007cff;">2.
          \index{Plenary Council+{\it periti} (experts)}: in this case
          it is the italicised <i class="moz-txt-slash"><span
              class="moz-txt-tag">/</span>periti<span
              class="moz-txt-tag">/</span></i> that appears out of
          place, after the letter 'i' rather than after 'p'. Again I
          tried putting various keys but this did not help. <br>
          <br>
          I guess my confusion is this: I assumed that the [key]
          establishes the literal string which determines sort order.
          That seems to be the case for a main entry. How do I get it to
          work for a subentry? <br>
        </blockquote>
        just provide an extra key: </blockquote>
    </div>
  </body>
</html>

--------------UUHfgrOSnNQBxMFZuFj5HJ8P--

--===============1164429868670234947==
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==

--===============1164429868670234947==--