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,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, 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 3408723FEB for ; Sun, 12 Jan 2025 12:54:46 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id C310E4853A5 for ; Sun, 12 Jan 2025 12:54:28 +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:user-agent:references:in-reply-to:message-id:date :date:from:from:mime-version:received:received:received:received :received; s=cgl; t=1736682868; x=1739274869; bh=FROddxqVqCF8Ph3 5/T820gL8xdXocrkLIS9Ugre/lXA=; b=ZGW40stIcn90aKHz2SXbQTmrrbNbUdO a2h4/TecVtrolDSAyq0vRV6KeUMGsU0ZAutUPPrwJ6RJS7LJLACuA+ZgU4d4Goh2 PkhKsHs6OpVCPr05zjNu2cU9oWqDeJpctapMF8xzlEaEcySQuWP7u5W8bzlKtYHz c8FrRfezpFl0= 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 TzQGY-6BXOXm for ; Sun, 12 Jan 2025 12:54:28 +0100 (CET) Received: from cgl.ntg.nl (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id 1AFDD485190 for ; Sun, 12 Jan 2025 12:54:11 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id CE6D14850AD for ; Sun, 12 Jan 2025 12:53:56 +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 V_tUUxpHY7Im for ; Sun, 12 Jan 2025 12:53:56 +0100 (CET) Received: from cgl.ntg.nl (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id 8B3EF4850AB for ; Sun, 12 Jan 2025 12:53:56 +0100 (CET) MIME-Version: 1.0 From: "autumnus " To: ntg-context@ntg.nl Date: Sun, 12 Jan 2025 11:53:56 -0000 Message-ID: <173668283655.1761.4882098632104514752@cgl.ntg.nl> In-Reply-To: References: User-Agent: HyperKitty on http://mailman.ntg.nl/ Message-ID-Hash: GMAZNJVWHVMQLK5C3OORPYXZEGDURUBX X-Message-ID-Hash: GMAZNJVWHVMQLK5C3OORPYXZEGDURUBX X-MailFrom: ai2472206007@yeah.net 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" Content-Transfer-Encoding: 7bit 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) 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) For the sorting of Japanese, the sorting I see on latex so far is also directly marked out of the pronunciation, and then sorted by the pronunciation of the kana. (Because kanji in Japanese may have more than one pronunciation, and maybe even as many as 5). Unless there is a tool that can simultaneously phonetize the Chinese characters in the index at compile time. ___________________________________________________________________________________ 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 ___________________________________________________________________________________