Re: [9fans] ktrans for Release 3 Plan 9

Re: [9fans] ktrans for Release 3 Plan 9

[okamoto]

Thanks Matt.

However, I felt that the README file got much smoother and clearer
meanings as such what I WANTED to say when I read Paul's correction.

When I have to talk to native English speakers, things are worse, and
I always feel myself to be getting fool like a cheap robot.☺  

Kenji

Re: [9fans] ktrans for Release 3 Plan 9

[Lucio De Re]

On Thu, Aug 17, 2000 at 05:57:54PM +0000, okamoto@granite.cias.osakafu-u.ac.jp wrote:
> 
> Russian is made possible by Ritchie-san from the original
> distribution.
> 
> Yes, I don't know Russian and Greek.  --> to Lucio

:-)

I used to pride myself of my ability to pick up languages, but I never
used the talent, through laziness as well as lack of opportunity.

Foreign alphabets I always found daunting, though.  Maybe the two aren't
as tightly coupled as one may assume.  I'll finish Umberto Eco's
_In_Search_Of_The_Perfect_Language_ before I comment further, but I'd
be curious to hear other opinions.  Maybe it's time I expanded my
horizons.

++L

Re: [9fans] ktrans for Release 3 Plan 9

[okamoto]

Russian is made possible by Ritchie-san from the original
distribution.

Yes, I don't know Russian and Greek.  --> to Lucio

Re: [9fans] ktrans for Release 3 Plan 9

[Wladimir Mutel]

okamoto@granite.cias.osakafu-u.ac.jp wrote:

> I put "ktrans for Release 3 Plan 9" on our web site 
> (http://basalt.cias.osakafu-u.ac.jp/plan9/p9index.html).  
> Ktrans was included in the Release 2 Plan 9, which enables us to 
> input Japanese and Greek and Russian using English key board.  

	Oh thanks, this is exactly what I was dreaming about.
	And would it be ported to Inferno r3 ?

--
mwg@alkar.net

Re: [9fans] ktrans for Release 3 Plan 9

[Matt]

> I seem to get what is right English wrting, but it's not easy to make
> it so by myself.
> 
> Kenji

from your posts here I would say your English writing is pretty good


Matt

Re: [9fans] ktrans for Release 3 Plan 9

[okamoto]

[-- Attachment #1: Type: text/plain, Size: 286 bytes --]

Someone kindly sent me a correction of my poor English of
README file.  Yes, he is right, and then, I've editted it and replaced
it of our web site.

Thank you very much Paul.

I seem to get what is right English wrting, but it's not easy to make
it so by myself.☺

Kenji


[-- Attachment #2: Type: message/rfc822, Size: 9327 bytes --]

From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] ktrans for Release 3 Plan 9
Date: Wed, 16 Aug 2000 11:49:09 0900
Message-ID: <200008160247.WAA05212@cse.psu.edu>

I put "ktrans for Release 3 Plan 9" on our web site 
(http://basalt.cias.osakafu-u.ac.jp/plan9/p9index.html).  
Ktrans was included in the Release 2 Plan 9, which enables us to 
input Japanese and Greek and Russian using English key board.  
This is a "derived work" Licensed distribution of Plan 9.  Above page 
is written in UTF-8, and you can search the part read as English, and 
take it, even if you'd find many of strange language there. ☺

Below is my README file for convenience to others.

This version of ktrans works with pipefile by Rob Pike, which replaces /dev/kbd of
the Release 2 Plan 9 by Dennis Ritchie.  By this new idea, we can input Japanese
anytime onto any windows.  I included his post to 9fans mailing-list here (pipefile
file).

This is a distribution as a derived work license of Plan 9, and I included the
Plan 9 License term here.  Please refer to it on the details of this license.


Main features are as follows:

1) have a "local" dictionary file for translation from kana to kanji which can 
      easily editted by user.  The default file name is $home/lib/ktrans-jisho.
      If you want to use other dictionary file, set the KTJISHO environment 
      variable to point to that file.  This dictionary complize many lines of
      text strings.  

2) capital romaji input for a word such as verbs or adjectives with okurigana, 
      which follows the idea of SKK system by Masahiko Sato of Kyoto Univ.
      (masahiko@kuis.kyoto-u.ac.jp).  If you want to get kanji string (runes)
      "動かす", which is a verb, you may input "ugoKasu" from the keyboard.  
      Note here the Kasu's k is a capital (important).  You will see a hiragana
      runes "うごかす", and then, the kanji runes of "動かす", when you hit 
      "Shift+Space". 
        If you are satisfied by that translation, continue to input next word.   
      If you are not pleasure with that candidate, hit 'Shift+Space' once more 
      to see more candiate for that hiragana inputs.  When no more other candidates
      are registered in your dictionary, you will see the initial hiragana input.

3) for Japanese "joshi", a postpositioned short word after noun, you can use another
      method which I developed for this work.  If you want kanji string (runes)
      "私は", then, try to hit "watashiHA" from the keyboard.  Note that the sound
      of "wa(ha)" is express as capitalized "HA".  You will see a hiragana string
      of "わたしは", and then, "私は" after `Shift+Space'.

4) a control sequence of 'ctl-l' is introduced to leave input hiragana runes unchanged.
      This is occasionally neccessary.

5) simple leaning mechanism has been implemented on the on-memory hashing dictinary
      where most recently used kanji runes (candidate) moves to the top of the
      list of candidates.  This is valid only during the session you called ktrans.
      This is done so intentionally, because present learning method is ..well... 
      naive. ^_^  I know this, however, I believe you can solve it by making a good 
      dictionary best fitted to your purpose by yourself.

6)  'ctl-x' re-reads the new kana-kanji translation dictionary when you edited your
      kana-kanji translation to update by acme, and want to reflect it into your
      current on memory translation dictionary.
      The kana-kanji translation dictionary is, usually, read only once at the 
      beginning of the ktrans session. I believe you will be suffered nothing 
      from this simplification, because you can edit the dictionary anytime by
      co-working with acme, and use this ctl-x.

7) mode change to kana-input is triggered by 'ctl-n', ctl-k for katakana mode, 
      ctl-g for Greek mode, and ctl-r for Russian mode.

8) as the starting $home/lib/ktrans-jisho, you may re-format the SKK-JISYO.S 
      (66.9KB) of SKK system, which can be reached from ftp.kuis.kyoto-u.ac.jp.  
      The next three lines shows the short sed filter to transform from SKK type 
      dictionary to Plan 9.  Before this, you should change kanji code of the SKK
      dictionary from ujis(euc) to UTF-8 by tcs utility, of course.
            s/\// /g
            s/  /	/g
            s/ $//g
      The header items are sorted in a strange order in the original SKK 
      dictionary.  This implementation does not care the order, therefore, 
      you can change it by yourself.

9) SKK jisho, such as SKK-JISYO.S, is composed of two parts, okuri-ari and 
      okuri-nashi entries.  This is greatly depend on the Japanese grammer,
      and okuri-ari may represent verb/adjective etc., i.e., not noun.
        These two parts work differently in the original SKK system, however,
      I did not employed that method, rather, a simple approarch as described
      in (2) and (3).  Here, we have no difference between these two parts, 
      and the reason why I leaved the two part structure remained is just 
      to make easier to read for editting.  Of course, you can change it
      without any side-effects.
    
10) This implementation of Japanese input method is to convert every one word 
      by one key triggering essentially.  This may cause some cumbersome feeling 
      to Nihongo users who are accustomed to, say, Windows. I know this.  
      However, I intended to keep the codes compact as possible as a first step 
      to develope Nihongo input system on Plan 9.  Furthermore, I've never seen 
      the latters worked perfectly.  I think the conversion failed essentially 
      when we see more than, say, five/six candidates for one input hiragana
      runes.

11) The trabslation trigger key has been chnaged from ^t to Shift+Space, because
      we experienced butting of the trigger key sequence sometime.  For this reason,
      you have to edit key binding table such as kbtabshift[0x39] in /sys/src/9/pc/kbd.c
      or keymapshift[0x79] in /sys/src/9/ss/screen.c to assign Shift+Space to '^\'.
      In my patch to translate.c, I use '^\' as the trigger key.  Therefore, you can
      trigger translation from kana to kanji by Shit+Space or just '^\'.

12) a usage example: if you want to make the Japanese text as below:

           私は毎日35分以上歩いて、 更に10分電車に乗って学校に通います。
           健康の維持にも役だっていますが、 なかなかたのしいものです。

      your keyboard hitting stream should be:

      watashiHA[^t]mainichi[^t]35[^l]fun[^t]ijou[^t]aruIte, [^t]saraNI[^t]
      10[^l]fun[^t]denshaNI[^t]noTte[^t]gakkouNI[^t]kayoImasu.[^t]
      kenkouNO[^t]ijiNImo[^t]yakuDAtteimasuga, [^t]nakanaka[^l]tanoshiI[^t]
      monodesu.[^l]

    where [^t], [^l] indicates 'Shift+Space' and 'ctl-l' respectively.


		       				Kenji  Okamoto  August 14, 2000--upas-zswcmhqqafaaevjkwveswyslof--

[9fans] ktrans for Release 3 Plan 9

[okamoto]

I put "ktrans for Release 3 Plan 9" on our web site 
(http://basalt.cias.osakafu-u.ac.jp/plan9/p9index.html).  
Ktrans was included in the Release 2 Plan 9, which enables us to 
input Japanese and Greek and Russian using English key board.  
This is a "derived work" Licensed distribution of Plan 9.  Above page 
is written in UTF-8, and you can search the part read as English, and 
take it, even if you'd find many of strange language there. ☺

Below is my README file for convenience to others.

This version of ktrans works with pipefile by Rob Pike, which replaces /dev/kbd of
the Release 2 Plan 9 by Dennis Ritchie.  By this new idea, we can input Japanese
anytime onto any windows.  I included his post to 9fans mailing-list here (pipefile
file).

This is a distribution as a derived work license of Plan 9, and I included the
Plan 9 License term here.  Please refer to it on the details of this license.


Main features are as follows:

1) have a "local" dictionary file for translation from kana to kanji which can 
      easily editted by user.  The default file name is $home/lib/ktrans-jisho.
      If you want to use other dictionary file, set the KTJISHO environment 
      variable to point to that file.  This dictionary complize many lines of
      text strings.  

2) capital romaji input for a word such as verbs or adjectives with okurigana, 
      which follows the idea of SKK system by Masahiko Sato of Kyoto Univ.
      (masahiko@kuis.kyoto-u.ac.jp).  If you want to get kanji string (runes)
      "動かす", which is a verb, you may input "ugoKasu" from the keyboard.  
      Note here the Kasu's k is a capital (important).  You will see a hiragana
      runes "うごかす", and then, the kanji runes of "動かす", when you hit 
      "Shift+Space". 
        If you are satisfied by that translation, continue to input next word.   
      If you are not pleasure with that candidate, hit 'Shift+Space' once more 
      to see more candiate for that hiragana inputs.  When no more other candidates
      are registered in your dictionary, you will see the initial hiragana input.

3) for Japanese "joshi", a postpositioned short word after noun, you can use another
      method which I developed for this work.  If you want kanji string (runes)
      "私は", then, try to hit "watashiHA" from the keyboard.  Note that the sound
      of "wa(ha)" is express as capitalized "HA".  You will see a hiragana string
      of "わたしは", and then, "私は" after `Shift+Space'.

4) a control sequence of 'ctl-l' is introduced to leave input hiragana runes unchanged.
      This is occasionally neccessary.

5) simple leaning mechanism has been implemented on the on-memory hashing dictinary
      where most recently used kanji runes (candidate) moves to the top of the
      list of candidates.  This is valid only during the session you called ktrans.
      This is done so intentionally, because present learning method is ..well... 
      naive. ^_^  I know this, however, I believe you can solve it by making a good 
      dictionary best fitted to your purpose by yourself.

6)  'ctl-x' re-reads the new kana-kanji translation dictionary when you edited your
      kana-kanji translation to update by acme, and want to reflect it into your
      current on memory translation dictionary.
      The kana-kanji translation dictionary is, usually, read only once at the 
      beginning of the ktrans session. I believe you will be suffered nothing 
      from this simplification, because you can edit the dictionary anytime by
      co-working with acme, and use this ctl-x.

7) mode change to kana-input is triggered by 'ctl-n', ctl-k for katakana mode, 
      ctl-g for Greek mode, and ctl-r for Russian mode.

8) as the starting $home/lib/ktrans-jisho, you may re-format the SKK-JISYO.S 
      (66.9KB) of SKK system, which can be reached from ftp.kuis.kyoto-u.ac.jp.  
      The next three lines shows the short sed filter to transform from SKK type 
      dictionary to Plan 9.  Before this, you should change kanji code of the SKK
      dictionary from ujis(euc) to UTF-8 by tcs utility, of course.
            s/\// /g
            s/  /	/g
            s/ $//g
      The header items are sorted in a strange order in the original SKK 
      dictionary.  This implementation does not care the order, therefore, 
      you can change it by yourself.

9) SKK jisho, such as SKK-JISYO.S, is composed of two parts, okuri-ari and 
      okuri-nashi entries.  This is greatly depend on the Japanese grammer,
      and okuri-ari may represent verb/adjective etc., i.e., not noun.
        These two parts work differently in the original SKK system, however,
      I did not employed that method, rather, a simple approarch as described
      in (2) and (3).  Here, we have no difference between these two parts, 
      and the reason why I leaved the two part structure remained is just 
      to make easier to read for editting.  Of course, you can change it
      without any side-effects.
    
10) This implementation of Japanese input method is to convert every one word 
      by one key triggering essentially.  This may cause some cumbersome feeling 
      to Nihongo users who are accustomed to, say, Windows. I know this.  
      However, I intended to keep the codes compact as possible as a first step 
      to develope Nihongo input system on Plan 9.  Furthermore, I've never seen 
      the latters worked perfectly.  I think the conversion failed essentially 
      when we see more than, say, five/six candidates for one input hiragana
      runes.

11) The trabslation trigger key has been chnaged from ^t to Shift+Space, because
      we experienced butting of the trigger key sequence sometime.  For this reason,
      you have to edit key binding table such as kbtabshift[0x39] in /sys/src/9/pc/kbd.c
      or keymapshift[0x79] in /sys/src/9/ss/screen.c to assign Shift+Space to '^\'.
      In my patch to translate.c, I use '^\' as the trigger key.  Therefore, you can
      trigger translation from kana to kanji by Shit+Space or just '^\'.

12) a usage example: if you want to make the Japanese text as below:

           私は毎日35分以上歩いて、 更に10分電車に乗って学校に通います。
           健康の維持にも役だっていますが、 なかなかたのしいものです。

      your keyboard hitting stream should be:

      watashiHA[^t]mainichi[^t]35[^l]fun[^t]ijou[^t]aruIte, [^t]saraNI[^t]
      10[^l]fun[^t]denshaNI[^t]noTte[^t]gakkouNI[^t]kayoImasu.[^t]
      kenkouNO[^t]ijiNImo[^t]yakuDAtteimasuga, [^t]nakanaka[^l]tanoshiI[^t]
      monodesu.[^l]

    where [^t], [^l] indicates 'Shift+Space' and 'ctl-l' respectively.


		       				Kenji  Okamoto  August 14, 2000