9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] ktrans
Date: Sat, 16 Jul 2022 16:57:06 -0600	[thread overview]
Message-ID: <9ff6217c-fe43-03aa-aac9-2aa417dcbbb0@posixcafe.org> (raw)
In-Reply-To: <0FC9AEA7-4263-42A2-8A68-DD06E0A5AC3C@gmail.com>

On 7/8/22 09:15, Xiao-Yong Jin wrote:
>> On Jul 7, 2022, at 7:38 PM, kokamoto@hera.eonet.ne.jp wrote:
> Current code in 9front has built-in kata, hira, cyril, greek, hangul, mappings in the header file.
> I hope it can become individual files that lives outside of the binary.

I want to make ktrans serve a fs where a user can upload mappings/dictionaries.
That way they can live outside the program and the user can just load whichever
specific one they prefer.

>> Kenji
>> PS. if chinese has not so homophone, it may be easier to include it in ktrans...
> Pronunciation is only one constricted way of mapping ascii to 漢字.
> I'm interested in this, https://raw.githubusercontent.com/fcitx/fcitx-table-data/master/wbx.txt

I got this dictionary working with a tiny bit of modifications, but I would like to ask
your opinion of how the completion should work.

Currently how I have it working is 漢字 is only looked up explicitly using [^\], but
ascii are otherwise passed along. Is this how it should be? Or should it map more similarly
to how the kana is done (implicit lookup)?

Thank you,

  reply	other threads:[~2022-07-16 22:58 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
2022-07-08 15:15           ` Xiao-Yong Jin
2022-07-16 22:57             ` Jacob Moody [this message]
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=9ff6217c-fe43-03aa-aac9-2aa417dcbbb0@posixcafe.org \
    --to=moody@mail.posixcafe.org \
    --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).