From: "Rodrigo G. López" <rgl@antares-labs.eu>
To: 9front@9front.org
Subject: Re: [9front] ktrans
Date: Fri, 08 Jul 2022 07:39:36 +0000 [thread overview]
Message-ID: <D05E7D8B-C700-477D-837E-9D7D37DE7E8B@antares-labs.eu> (raw)
In-Reply-To: <891985DA6AEAD81D6F3252F393AB2696@hera.eonet.ne.jp>
hi kenji.
i can't find any reference to the mechanism to edit the jisho on the fly you mention. is it the ctl-x shortcut to refresh the in-memory jisho?
people can choose their own jisho through the $jisho environment variable. i didn't document that, but i will update the manpage and also add romi's tool to merge different jishos—which the user can use to build their own jishos for the given task/environment—this weekend.
i'm learning japanese and i'm far from experienced, so i could use all the help i can get. :)
i'd like to talk to you about the transformations you did to the original skk dict (SKK-JISYO.M afaict), in order to automate it and document it as much as possible, so people can add their own entries from scratch.
i can contact you off-list if you prefer.
cheers!
-rodri
On July 8, 2022 12:38:57 AM UTC, kokamoto@hera.eonet.ne.jp wrote:
>Quoth romi <r@grtsk.net>:
>> I didn’t realised that Kenji’s READMEs had a trailing indent (just bellow the 9th bullet of the features list) haha
>>
>> Anyway, awesome to have ktrans shipped with 9front out of the box!
>
>I asked to put ktrans to 9front's contrib several years ago, and I agreed
>it with no maintainance by myself.
>The ktrans was written more than 20 years ago, then, I don't remember it...
>
>When I was asked to collaborate with GSOC last year, I wrote to the author
>the principle under ktrans, then, I'll put it here again (the last time I'll write about this).
>
>1) the most essential thing about ktrans is not in ktrans, but in pipefile.
>2) pipefile was invented by Rob Pike which made us enbale to write Japanese
>seamlessly, which means we can trewat Japanese, Greek and Russian as
>English.
>3) more precisely, WE DON'T NEED TO WRITE PROGRAMS FOR INDIVIDUAL
>LANGUAGE!
>4) for ktrans proper, I chose the ktrans-jisho for individual user not system wide, because
>each person has each habits to write Japanese, then it is better to have
>individual dictionary (Japanese has many different Kanji with the same sound, homophone)
>This is intentional, don't make it change.
>5) I also intentionary exclude proper and technical nouns, because those depend
>on inviduals.
>6) instead, I put tyhe mechanism to edit the ktrans-jisho on the fly.
>7) 9front version includes pipekbd.c written by cinap, which is the same thing
>of pipefile because 9front has kbdfs.
>
>Kenji
>
>PS. if chinese has not so homophone, it may be easier to include it in ktrans...
>
next prev parent reply other threads:[~2022-07-08 7:41 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
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 [this message]
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:
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=D05E7D8B-C700-477D-837E-9D7D37DE7E8B@antares-labs.eu \
--to=rgl@antares-labs.eu \
--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).