9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] input methods for non-ascii languages
Date: Wed, 30 Jul 2003 11:33:42 +0900	[thread overview]
Message-ID: <ca8391a080afb5fb5d4dffd51348aa1b@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <01fa01c35640$b572c840$b9844051@insultant.net>

> yes, calligraphy is hard.  i can't even write ascii based stuff now after

I was raised in such Kanji calture where it's very natural we can't read
ancient Kanji writings, because it's too much artificial.

When I was at Old Bible's museum in Jerusalem, I was much surprised
that a young mother is reading that Bible, written 2000 years ago!, to
her daughter.   And I couldn't stop to ask her why you can read such
an old document, and her answer was, well it's not easy to read it,
because a bit art like.   I felt that every nation has a similar tendency
to write their words in art like if possible.   However, in case of
Kanji, it's hard to read if it's written, and importantly we feel it
beautifuller, in art like...

Kenji



  reply	other threads:[~2003-07-30  2:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29  7:42 sasa
2003-07-29  7:56 ` okamoto
2003-07-29 10:44 ` Skip Tavakkolian
2003-07-29 11:29   ` boyd, rounin
2003-07-29 12:20     ` David Presotto
2003-07-30  0:51       ` okamoto
2003-07-30  1:14         ` okamoto
2003-07-30  1:19         ` boyd, rounin
2003-07-30  2:06           ` okamoto
2003-07-30  2:17             ` boyd, rounin
2003-07-30  2:33               ` okamoto [this message]
2003-07-30  2:40                 ` boyd, rounin
2003-07-30  4:45                 ` Skip Tavakkolian
2003-07-30  8:26                 ` Anthony Mandic
2003-07-29 15:07     ` Anthony Mandic
2003-07-29 20:47       ` boyd, rounin
2003-07-30  8:26         ` Anthony Mandic
2003-07-30 11:35           ` boyd, rounin
2003-07-29 12:23   ` David Presotto
2003-07-29 12:06 sasa

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=ca8391a080afb5fb5d4dffd51348aa1b@granite.cias.osakafu-u.ac.jp \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --cc=9fans@cse.psu.edu \
    /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).