9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Chris A. Fröschl <chris@chrisfroeschl.de>
To: 9front@9front.org
Subject: [9front] [PATCH] ktrans: updates ktrans to use pinyin by default, documents $zidian env
Date: Sat, 05 Oct 2024 12:36:25 +0000	[thread overview]
Message-ID: <A7EAB8F107FE6A7ABC8D3937617C4303@chrisfroeschl.de> (raw)


Pinyin is by far more commonly used than wubi. Therefore, the default
should be adjusted. Documentation for the $zidian env variable for setting
a custom character mapping file is now also documented.
---
diff 6ebfbaa82641fcb727858aeb7dd790a3ac10864f 3ad6886ad077a9f42647129243b41378264433b8
--- a/sys/man/1/ktrans	Sat Oct  5 02:43:38 2024
+++ b/sys/man/1/ktrans	Sat Oct  5 14:36:25 2024
@@ -189,11 +189,12 @@
 we have successfully communicated to ktrans when to reset the explicit
 match buffer without needing to explicitly give a ctl-l character.
 .SS CHINESE
-Implicit conversion converts punctuation. Explicit matches
-use a dictionary to convert a series of Latin characters
-into Hanzi. By default a Wubizixing input dictionary
-is used. Additionally a Pinyin input dictionary 
-is provided.
+The Pinyin input mapping method to simplified characters is used by
+default.  Other input method mapping files are provided at /lib/ktrans
+and can be used by setting the $zidian environment variable to the
+wanted file.  Implicit conversion is done for punctuation only.
+Explicit conversion interprets latin characters as their $zidian
+counterparts to do lookup of chinese characters.
 .SS VIETNAMESE
 Implicit conversion is modeled after Telex, supporting
 standard diacritic suffixes.
--- a/sys/src/cmd/ktrans/main.c	Sat Oct  5 02:43:38 2024
+++ b/sys/src/cmd/ktrans/main.c	Sat Oct  5 14:36:25 2024
@@ -945,7 +945,7 @@
 	Hmap **m;
 } initdicttab[] = {
 	"jisho", "kanji.dict", &jisho,
-	"zidian", "wubi.dict", &zidian,
+	"zidian", "pinyin.dict", &zidian,
 };
 
 mainstacksize = 8192*2;

                 reply	other threads:[~2024-10-05 12:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=A7EAB8F107FE6A7ABC8D3937617C4303@chrisfroeschl.de \
    --to=chris@chrisfroeschl.de \
    --cc=9front@9front.org \
    /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).