9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Simplified Chinese plan 9
Date: Fri, 11 Sep 2009 18:16:49 -0400	[thread overview]
Message-ID: <09b98d8a6bac3a134bc495bb1ed1878c@quanstro.net> (raw)
In-Reply-To: <C890B1F2A8C2EC12D5383D7C@[192.168.1.2]>

> That's true but isn't exactly the same thing. "Irregularly" pronounced
> combinations are still valid combinations. I'd say the universal example
> for languages that are written in Latin alphabet or a variation thereof
> would be the (notorious) 'fgsfds.' It's an invalid combination because
> there is _no_ pronunciation at all--except 'figgis-fiddis' which is a
> really recent, and ground-breaking, invention ;-)

by this definition, one could devise a valid input method
with which it would be impossible to type "xyzzy".

> no written language stands independent of its pronunciation rules.
> alphabets need a somewhat larger set of rules than syllabaries, but
> that's true independent of language.

i'm not sure they are fully dependent.  consider acronyms.  or even
variable names.  (sometimes these need to be referred to
in speech.)  there are special hacks for making these
pronouncable.  in mathematics the same symbol can
have many pronunciations that depend entirely on the
context.

i'm not a linguist, but the linguists i know subscribe to the
viewpoint that the written and spoken language are separate.
and evolve separately.  i would derive from this that writability
is independent of pronouncability.

trying to think as a linguist, i would consider spoken acronyms
to be cognates from the written language.

as an homage to j. arthur seebach i'd say, "english is *neat*".

- erik



  reply	other threads:[~2009-09-11 22:16 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 [this message]
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
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=09b98d8a6bac3a134bc495bb1ed1878c@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).