From: Eris Discordia <eris.discordia@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Simplified Chinese plan 9
Date: Mon, 14 Sep 2009 13:47:06 +0100 [thread overview]
Message-ID: <E0FCD7F5CF14795027264E29@[192.168.1.2]> (raw)
In-Reply-To: <87hbv8wyyn.fsf@plap.localdomain>
I've been, for the time being, officially p9-gagged due to "core-dumping"
on the list. But thanks anyway for the information. And yes, the Latin
alphabet does function.
--On Monday, September 14, 2009 09:33 +0000 Paul Donnelly
<paul-donnelly@sbcglobal.net> wrote:
> eris.discordia@gmail.com (Eris Discordia) writes:
>
>>> http://thinkzone.wlonk.com/Language/Korean.htm
>>
>> Interesting. I used to think Korean, too, uses a syllabary. Turns out
>> it's expressed alphabetically. Expressing Japanese that way would
>> create some space for confusion as there are certain sounds that never
>> combine with certain other sounds, e.g. there are 'sa,' 'se,' 'so,'
>> and 'su' syllables in which 's' is heard just like 's' in 'say' but
>> there's no 'si'--there's only 'shi.'
>
> Actually, I belive that in Korean, "si" (시, if that displays for you at
> all) is pronounced "shi". :P
>
>> If there existed an 's' character and also characters for vowels the
>> invalid combination 'si' could be created in writing. I wonder if
>> Korean alphabet can be used to make invalid combinations or all
>> possible combinations correspond to existing phonetic constructs.
>
> Some combinations don't occur. Especially there are dipthongs that don't
> occur. But that's not really strange or a problem. Consider the word:
> qimk. It doesn't work in English, but the Latin alphabet still
> functions.
>
next prev parent reply other threads:[~2009-09-14 12:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 8:40 xiangyu
2009-09-11 10:23 ` erik quanstrom
2009-09-11 11:29 ` Alexander Sychev
2009-09-11 16:13 ` Eris Discordia
2009-09-11 17:49 ` erik quanstrom
2009-09-11 19:14 ` Eris Discordia
[not found] ` <68F5914168759B188DF09A60@192.168.1.2>
2009-09-11 19:53 ` Anthony Sorace
2009-09-11 21:28 ` Eris Discordia
2009-09-11 22:16 ` erik quanstrom
2009-09-12 1:19 ` Eris Discordia
2009-09-12 1:46 ` erik quanstrom
2009-09-12 7:05 ` Eris Discordia
2009-09-12 8:39 ` Daniel Lyons
2009-09-12 14:22 ` Eris Discordia
2009-09-12 14:27 ` erik quanstrom
2009-09-12 14:39 ` Eris Discordia
[not found] ` <160F5E4B5D4057F12BB54C75@192.168.1.2>
2009-09-12 20:22 ` Nick LaForge
[not found] ` <C890B1F2A8C2EC12D5383D7C@192.168.1.2>
2009-09-11 21:59 ` Anthony Sorace
2009-09-14 9:33 ` Paul Donnelly
2009-09-14 12:47 ` Eris Discordia [this message]
2009-09-11 16:54 ` Anthony Sorace
2009-09-11 18:36 ` Eris Discordia
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='E0FCD7F5CF14795027264E29@[192.168.1.2]' \
--to=eris.discordia@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).