From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from cgl.ntg.nl (Cgl.ntg.nl [5.39.185.202]) by inbox.vuxu.org (Postfix) with ESMTP id A2D8821D38 for ; Sun, 12 Jan 2025 13:19:38 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id 6288A4851E1 for ; Sun, 12 Jan 2025 13:19:02 +0100 (CET) Authentication-Results: cgl.ntg.nl (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=ntg.nl DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ntg.nl; h= content-transfer-encoding:content-type:content-type :list-unsubscribe:list-subscribe:list-post:list-owner:list-help :list-archive:archived-at:list-id:subject:subject:reply-to :precedence:in-reply-to:from:from:references:content-language :user-agent:mime-version:date:date:message-id:received:received :received:received:received:received:received; s=cgl; t= 1736684341; x=1739276342; bh=HRPLjcQ46Ag89tGpIc+/f2OELvQfCe5f2NE xXDbK558=; b=k3P1jsO+iMZmdXbke/3kapp3yyhENfhiRHvKOCmEUz4KEFgaYea OC0qo+AnHpa9PW34ZRGlW6OsonOdCg6I1K8nrGRdz1Kf8GwsvoShjnCAKNEG0XLu t6Xey/NU85WkgjcrXF5TjRIg6C2U5np/G3ieqDSHr9FEU/jlFcEMdM7E= X-Virus-Scanned: Debian amavisd-new at cgl.ntg.nl Authentication-Results: cgl.ntg.nl (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=xs4all.nl Received: from cgl.ntg.nl ([127.0.0.1]) by localhost (cgl.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UCUWVIpg91qC for ; Sun, 12 Jan 2025 13:19:01 +0100 (CET) Received: from cgl.ntg.nl (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id B9A53484A4E for ; Sun, 12 Jan 2025 13:18:36 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id 37D0948498E for ; Sun, 12 Jan 2025 13:18:22 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at cgl.ntg.nl Received: from cgl.ntg.nl ([127.0.0.1]) by localhost (cgl.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XnWxoYabw0Ny for ; Sun, 12 Jan 2025 13:18:20 +0100 (CET) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=195.121.94.184; helo=ewsoutbound.kpnmail.nl; envelope-from=j.hagen@xs4all.nl; receiver= Received: from ewsoutbound.kpnmail.nl (ewsoutbound.kpnmail.nl [195.121.94.184]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by cgl.ntg.nl (Postfix) with ESMTPS id D76E448497E for ; Sun, 12 Jan 2025 13:18:20 +0100 (CET) X-KPN-MessageId: 9279606f-d0df-11ef-9401-005056994fde Received: from smtp.kpnmail.nl (unknown [10.31.155.6]) by ewsoutbound.so.kpn.org (Halon) with ESMTPS id 9279606f-d0df-11ef-9401-005056994fde; Sun, 12 Jan 2025 13:20:12 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xs4all.nl; s=xs4all01; h=content-type:from:to:subject:mime-version:date:message-id; bh=3Vtf5OlLbO19GaBD3PRUot5sZZj7ZlKLy7jMkn4Y/7k=; b=uC3Zluta51qjtY1w4x7Zfxc0/yqc9NQsTDl7H2OA0f/Zf2pmSfwO1Yvy2PZC9lHpgkQnZ7ht5LtCO g9HbnIiRIjj/fbOycFLcuP8kcRIupaTpBBJpnf9InA6AWg15wEYHjUlwXg+Huv7j7sRVQ0Ya/iSsHy FKRjE4kbIbSZnWn8Zl9rCjRhFdPVTOAIn/Mtjl+3qBoWElzky2sOlP1BxhZ6zX18Ti5gIvui/z4QQ8 rsbAm2NcddfnOhUnnzv2tMsrjfqBHJQjPvbTojDsrdCqMyyGOhd01QkIGNU7fhjILjXBkc9TwZFnK4 QFRvYR0IbifnqdodQYT98dy+SzWahLw== X-KPN-MID: 33|YoYqvVjdBZeNWdgc75EUtVI7b4cYa1SJofOvl/xi+EMaLxv62404ZNYbkMp9pJl fnVBsHJDJPN56zQ2G7csWI7A8uuxo16n6EkNkWiCLsKE= X-KPN-VerifiedSender: Yes X-CMASSUN: 33|yRVz9DgdDnYs5JvpPHsDx8Kf+OD65eBe3WUOfGyUXJjTAXn3IWEFsVF5eHg/jcE J1+0hllzSo4/bEC0LRxLITg== X-Originating-IP: 213.125.29.162 Received: from [10.100.1.105] (d57d1da2.static.ziggozakelijk.nl [213.125.29.162]) by smtp.xs4all.nl (Halon) with ESMTPSA id 4f4b0309-d0df-11ef-88cb-00505699772e; Sun, 12 Jan 2025 13:18:20 +0100 (CET) Message-ID: <617607a6-27f1-4c41-994e-a73a336d4f63@xs4all.nl> Date: Sun, 12 Jan 2025 13:18:19 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: nl To: ntg-context@ntg.nl References: <173668283655.1761.4882098632104514752@cgl.ntg.nl> From: Hans Hagen In-Reply-To: <173668283655.1761.4882098632104514752@cgl.ntg.nl> Message-ID-Hash: PFKK5LRVLEZGEPGVDO3JET4BFN3XR3FB X-Message-ID-Hash: PFKK5LRVLEZGEPGVDO3JET4BFN3XR3FB X-MailFrom: j.hagen@xs4all.nl X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9 Precedence: list Reply-To: mailing list for ConTeXt users Subject: [NTG-context] Re: Quickly invoke a self-defined index sorting file? List-Id: mailing list for ConTeXt users Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii"; format="flowed" Content-Transfer-Encoding: 7bit On 1/12/2025 12:53 PM, autumnus wrote: > Thanks for the explanation. > > After using \registerctxluafile{sort-hanzi}{}, > the bumping message did not appear. > > In terms of daily practical use, I really don't need so many characters. > I just don't have the energy to pick out those thousands of commonly used Chinese characters > from these 40,000 or 50,000 characters > (In China, for example, there are only about 6,000-8,000 characters actually used on a daily basis. > In Japanese, you may only need about 1000-3000 characters) so the entries table can just be omitted then > There are only two commonly used sorts for these characters: > (Sorting has nothing to do with unicode sorting) > 1 according to the actual pronunciation of the characters and > 2 according to the order in which the characters are written (strokes). > (The situation in Japanese should probably be mostly sorted by actual pronunciation based on kana, > but the pronunciation of kanji in Japanese is much more complicated than in Chinese.) > > But sorting by strokes, I don't have the ability to achieve it at the moment. > So the three indexes I designed are sorted according to the actual pronunciation of the Chinese characters. > > The difference between them is only in the entries. > 1 Sort in the order of a, b, c d, and use these letters as entries.(mostly used) > 2 Sort in the order of a ai ao an ...... , and these pronunciations are used as entries. > 3 Sort Chinese characters directly by their pronunciation and use them as entries. > > Because I know almost nothing about lua myself, just referring to sort-lang (just applying templates) you can set up a combination of sorting if needed so the 'order' table is what matters in your case, is that table made from some public list? > For the sorting of Japanese, the sorting I see on latex > Unless there is a tool that can simultaneously > phonetize the Chinese characters in the index at compile time. if we have the basic data (how to pronounce a single char) then runtime is no big deal Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | 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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___________________________________________________________________________________