9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio.dere@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] ctrans - Chinese language input for Plan9
Date: Wed, 20 Jul 2022 05:54:34 +0200	[thread overview]
Message-ID: <CAJQ9t7h9TnKzHxy2PfvQd6Td7eMiTCHRHJmUZPqWG828VWF2Ag@mail.gmail.com> (raw)
In-Reply-To: <A5A01F84804C8CC3CE36C32EB2F5D4E5@9p.sdf.org>

I have only one word for all the above: amazing!

As a dumb occidental, I have no idea where one starts with ideograms,
but I realise how different the concept is and how its complexity can
stimulate technical creativity.

Well done, all!

Lucio.

On 7/20/22, smj@9p.sdf.org <smj@9p.sdf.org> wrote:
> With the recent commit of 'ktrans' to 9front, SDF boot camper 'ldb' as taken
> the
> idea and created 'ctrans' https://9p.sdf.org/who/ldb
> 
> As Kenji Okamoto has pointed out, 'ktrans' would be difficult to extend to
> Chinese due to the massive number of characters necessary.  While Japanese
> can
> get away with ~2500 daily use characters, Chinese requires quite a bit more.
> 
> The advantage in Japanese is that there are two other writing alphabets
> which are
> purely phonetic and useful for importing foreign words.
> 
> ldb's 'ctrans' had to take the 'ktrans' idea and optimize it a bit more to
> support
> 20,000 characters.  The result is a mechanism that more or less behaves like
> ktrans
> but is quick (even over drawterm) to cycle through character lists.
> 
> moody has seen this work and it has been an inspiration to adapt to 'ktrans'
> for
> even faster Kanji look up which could allow for more esoteric Kanji to be
> added.
> 
> In addition a new font 'HanaMinA' has been adapted which beautifully
> supports both
> Japanese and Chinese characters and it is what we recommend folks use on
> 9p.sdf.org.
> 
> Thank you ldb for your great work!
> 
> ldb, お疲れ様です!
> 
> smj

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tba6835d445e07919-M69038fd1b148474da50c0796
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-07-20  3:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20  3:20 smj
2022-07-20  3:54 ` Lucio De Re [this message]
2022-07-20  6:50   ` sirjofri
2022-07-21  2:44     ` [9fans] " cigar562hfsp952fans
2022-07-21  6:57       ` sirjofri
2022-07-21  9:46         ` adr
2022-07-21  9:45       ` Lucio De Re
2022-07-21 10:20         ` adr
2022-07-22 12:30           ` Silvan Jegen
2022-07-22 14:43             ` adr
2022-07-22 18:06             ` Sebastian Higgins
2022-07-22 19:09               ` Silvan Jegen
2022-07-22 19:13               ` Jacob Moody
2022-07-22 19:14       ` andpuke
2022-07-22 19:24         ` andpuke
2022-07-22 20:37           ` Silvan Jegen
2022-07-22 22:29             ` LdBeth
2022-07-26 12:29               ` adr
2022-07-29  8:04                 ` Silvan Jegen

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=CAJQ9t7h9TnKzHxy2PfvQd6Td7eMiTCHRHJmUZPqWG828VWF2Ag@mail.gmail.com \
    --to=lucio.dere@gmail.com \
    --cc=9fans@9fans.net \
    /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).