9front - general discussion about 9front
 help / color / mirror / Atom feed
From: rgl@antares-labs.eu
To: 9front@9front.org
Subject: Re: [9front] ktrans
Date: Sun, 03 Jul 2022 12:35:39 +0200	[thread overview]
Message-ID: <B2F9917BB8E0E263162170F25DEBFF4E@antares-labs.eu> (raw)
In-Reply-To: <C33520257318E94971B2B881686E7141@eigenstate.org>

hi ori,

> Is this japanese-only? Does it work for other languages?

it supports input for english (passthrough/no processing), japanese
(hiragana, katakana and kanji), russian, greek and korean.

> 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?

it needs to run before a rio session.  you can either set it up on a
sub-rio running `@{ktrans; rio}` on a window, or put it on a line
right before starting rio in your $home/lib/profile.  i'm thinking
these could be handy to have as examples in the man page, since it
isn't really obvious how you are supposed to get it running from the
current docs.

> I see some large hard-coded tables, as well as some dicts
> and scripts to generate dicts. Can we replace the dicts
> with scripts?

i think so, yeah.  the kanji.jisho is an adaptation of the libskk
dicts, the medium sized one to be more precise.  i will try to figure
out the transformation Okamoto did and set up an automated fetch
script to pull them directly from the github.com/skk-dev/dict repo and
apply the filtering.  users could then go to /lib/ktrans, and do
`grabdict [small|medium|large]` based on their preferences.  it could
also be worth shipping with the small jisho, which is 54KB vs.  the
141KB medium one.

i'll update the thread once i get all of the above done.



  reply	other threads:[~2022-07-03 10:37 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
2022-07-03 10:35   ` rgl [this message]
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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B2F9917BB8E0E263162170F25DEBFF4E@antares-labs.eu \
    --to=rgl@antares-labs.eu \
    --cc=9front@9front.org \


* 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).