Subject: Re: [9front] ktrans
Date: Sat, 02 Jul 2022 16:56:23 -0400 [thread overview]
Message-ID: <C33520257318E94971B2B881686E7141@eigenstate.org> (raw)
> this is a new version of ktrans(1), originally written by Kenji
> Okamoto, that includes modifications by:
> - cinap: to work with kbdfs(8) instead of pipefile(1) (could've done more work i can't track)
> - BurnZeZ: naming corrections and proper argument handling
> - romi: support for korean and shortcuts that play nice with sam and rc
> i cleaned up the code a bit, corrected some comments (mostly typos)
> and adapted the man page to reflect the aforementioned changes.
> romi also made a nice little tool to extend the kanji.jisho Kenji
> prepared—in case 7.5K kanjis aren't enough for you. you can find it
> is it OK to commit?
I like the idea of shipping with kanji support, but I'm not in a position
to know whether this is any good, or if it needs any work.
A few questions:
- Is this japanese-only? Does it work for other languages?
- How hard is it to set up? The last tutorial I saw for it
made it look like a pain, and I'm wondering if this patch
makes it any better. If not, what work would we want to
do on it?
- I see some large hard-coded tables, as well as some dicts
and scripts to generate dicts. Can we replace the dicts
next prev parent reply other threads:[~2022-07-02 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 16:00 rgl
2022-07-02 20:56 ` ori [this message]
2022-07-03 10:35 ` rgl
2022-07-03 18:25 ` ori
2022-07-06 23:18 ` smj
2022-07-07 5:35 ` romi
2022-07-08 0:38 ` kokamoto
2022-07-08 7:39 ` Rodrigo G. López
2022-07-08 15:15 ` Xiao-Yong Jin
2022-07-16 22:57 ` Jacob Moody
2022-07-07 15:21 ` Xiao-Yong Jin
2022-07-03 17:56 ` cinap_lenrek
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).