Return-Path: Received: (qmail 22448 invoked from network); 28 May 2000 09:16:23 -0000 Received: from unknown (10.1.10.26) by m1.onelist.org with QMQP; 28 May 2000 09:16:23 -0000 Received: from unknown (HELO qg.egroups.com) (10.1.2.27) by mta1 with SMTP; 28 May 2000 09:16:23 -0000 Received: (qmail 20118 invoked from network); 28 May 2000 09:16:23 -0000 Received: from mw.egroups.com (10.1.2.2) by iqg.egroups.com with SMTP; 28 May 2000 09:16:23 -0000 X-eGroups-Return: Ti@fa-kuan.muc.de Received: from [10.1.10.94] by mw.egroups.com with NNFMP; 28 May 2000 09:16:22 -0000 Date: Sun, 28 May 2000 09:16:16 -0000 To: lojban@egroups.com Subject: Re: coi rodo - mi'e .aulun. Message-ID: <8gqo50+56qc@eGroups.com> In-Reply-To: <4.2.2.20000528030210.00b44100@127.0.0.1> User-Agent: eGroups-EW/0.82 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: eGroups Message Poster From: "=?iso-8859-1?q?Alfred_W._T=FCting?=" X-Yahoo-Message-Num: 2869 Content-Length: 2791 Lines: 69 --- In lojban@egroups.com, "Bob LeChevalier (lojbab)" wrote: > I could post this (and/or put it on the website). Unfortunately, this > official mapping led to severe collision because so many pinyin letters > mapped to schwa; we also did not at the time understand how C+i sounded > (e.g. pinyin "zi"), though I have since had this clarified. Would be interested in! > If we had it to do over again, we would map "ong" to "on(g?)" and not to > "yn". IMHO this mapping to lb: "yn" most probably is based on a misunderstanding, maybe going back to pronunciation standards in southern Chinese dialects like Cantonese: Mandarin (pinyin) -eng (lb: -yn(g)) very often is pron. -ong (=3Dung) or -un in southern dialects (e.g. BIG5 =C2=D7 pinyin: feng1, "fruitful/abundant" in dialect is *written* and pronounced "fung" - pron. in 'virtual' pinyin about: fong -, or BIG5 =AD=B7 pinyin: feng1, "wind" etc. in dialect written and pron. "fun" as in Cantonese taifun, BIG5 =A4j=AD=B7, pinyin: dafeng!) Pinyin "-ong" should be transcribed to lb: "un(g)" *not* -yn (e.g. mau.dzydun.) > The g is questionable because Lojban maps the /ng/ consonant to > /n/. As someone noted, if the g is present it is pronounced separately > from the n. But the real problem is that in gismu making we could have > ended up with the g and not the n in the Lojban word, and the g by itself > without the n is probably useless to a Chinese speaker for recognition. In Mandarin there can be no g-ending except in -ng, so this would not necessarily lead to much misunderstanding to a Chinese speaker familiar with lojbanization. BTW, in southern dialects, there are lots of consonant endings, e.g. in Hakka language BIG5 =AB=C8 =AEa (=3DHakka or "guest families"), pinyin: ke4 jia1, it is "hag-ga". One principle question: For what reason cmene have to follow the strict rules of Lojban phonology?? If it just were for computers to understand the language, isn't it sufficient to enclose cmene (first of all personal names etc.) in the structure beginning with the cmene indicators "la" and the "."? Shouldn't it be the main goal to giving the reader an idea of what the name word is pointing to and what's its common/real pronunciation? So, e.g. writing la maozedong. (instead of la mau.dzydun.) would function a lot better in this sense. Or, writing the the cluster "ng" in (e.g. Chinese or German) names could imply that it's not pronounced like in British/American English as two separated consonants (Engl.: fin-ger, Germ.: Finger), so the reader is not obliged to pronounce it the lb way. In Glosa language, all 'foreign' words (like 'french', 'english' etc.) had been 'incorporated' (i.e. left untouched). I wouldn't go that far, though. co'o mi'e .aulun.