Re: [9front] ktrans

[ori@eigenstate.org]

Quoth rgl@antares-labs.eu:
> 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.

Yes, adding an example of how to use it would be fantastic.
 
> > 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'd document where it comes from, but I'd just treat it like
/lib/keyboard in kbdfs. Could add some script to pull them,
but I'd be ok with just checking them in.

I'm also ok with just keeping the tables, it just seemed odd
to have a mix.

Thanks!