From: "autumnus " <ai2472206007@yeah.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Quickly invoke a self-defined index sorting file?
Date: Sun, 12 Jan 2025 11:53:56 -0000 [thread overview]
Message-ID: <173668283655.1761.4882098632104514752@cgl.ntg.nl> (raw)
In-Reply-To: <e8b46fdc-f024-4a11-b267-b2fee76be45d@xs4all.nl>
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
___________________________________________________________________________________
next prev parent reply other threads:[~2025-01-12 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 8:58 [NTG-context] " autumnus
2025-01-12 11:01 ` [NTG-context] " Hans Hagen
2025-01-12 11:53 ` autumnus [this message]
2025-01-12 12:18 ` Hans Hagen
2025-01-12 13:54 ` autumnus
2025-01-12 15:59 ` Hans Hagen via ntg-context
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=173668283655.1761.4882098632104514752@cgl.ntg.nl \
--to=ai2472206007@yeah.net \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).