Received: from mail-we0-f189.google.com ([74.125.82.189]:45873) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1YCsTB-0006Uz-4c; Sun, 18 Jan 2015 08:12:58 -0800 Received: by mail-we0-f189.google.com with SMTP id k11sf2394028wes.6; Sun, 18 Jan 2015 08:12:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:sender:list-subscribe:list-unsubscribe; bh=xHRlCKOfwbAy2rxHVL7eQjZ4w0SczpywW6VkskRG0yo=; b=nhWhKX8196wjbewk4nOFpDxGGHLOtwsDQqEYSGp84/As4+msH1z01kAwgVndFy8FS2 mJOh9zP5ksp3zp8e1dzSwTk8xyXaDpcqrxkP9GAOtTucqtqreex7BhGchtWkocSZevgN XJXyRVQYT2WeF7MLM7wnqGX8S5lSH/9kduAFwHvdt7RsN2FgIqK1uEbnw+6XxxlxtK4Z YijttBSDgTt1EwBbd4WGRchOSYKc8Qq3kydROCUW74Ywk6Ob3z9afVJxofirMEFu/UXS xKgA//NpKbKSzmAd9Dk41JTwOv4L6XRPJaqrcjvNg0Z6zNSUlUBfPXERbnDxPbKL5AdV 0ZAg== X-Received: by 10.152.246.3 with SMTP id xs3mr88838lac.5.1421597570312; Sun, 18 Jan 2015 08:12:50 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.28.200 with SMTP id d8ls412896lah.18.gmail; Sun, 18 Jan 2015 08:12:49 -0800 (PST) X-Received: by 10.152.170.201 with SMTP id ao9mr178990lac.5.1421597569823; Sun, 18 Jan 2015 08:12:49 -0800 (PST) Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com. [2a00:1450:400c:c03::22e]) by gmr-mx.google.com with ESMTPS id d18si484471wiv.0.2015.01.18.08.12.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 18 Jan 2015 08:12:49 -0800 (PST) Received-SPF: pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c03::22e as permitted sender) client-ip=2a00:1450:400c:c03::22e; Received: by mail-we0-f174.google.com with SMTP id k48so27584719wev.5 for ; Sun, 18 Jan 2015 08:12:49 -0800 (PST) X-Received: by 10.194.8.232 with SMTP id u8mr3269988wja.47.1421597569606; Sun, 18 Jan 2015 08:12:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.86.200 with HTTP; Sun, 18 Jan 2015 08:12:29 -0800 (PST) In-Reply-To: References: From: Gleki Arxokuna Date: Sun, 18 Jan 2015 19:12:29 +0300 Message-ID: Subject: Re: [bpfk] Question on {z} vs. {dz} and {ts} To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=047d7b5d348c266ba7050cef7a48 X-Original-Sender: gleki.is.my.name@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c03::22e as permitted sender) smtp.mail=gleki.is.my.name@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: 0.8 (/) X-Spam_score: 0.8 X-Spam_score_int: 8 X-Spam_bar: / X-Spam-Report: Spam detection software, running on the system "stodi.digitalkingdom.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: 2015-01-18 18:46 GMT+03:00 Mike S. : > On Sat, Jan 17, 2015 at 10:03 AM, Gleki Arxokuna < > gleki.is.my.name@gmail.com> wrote: > >> Today I was reminded of one "flaw" in phonology namely, the presense of >> [z] in Lojban. >> >> Mandarin doesn't have it/has it as an allophone of t͡s. >> >> >> https://docs.google.com/document/d/1_w-c7yM6beFUc_G-XCSLlRfrCewhQosFdQuPD1DwhuU/edit?usp=drive_web >> >> So my question is: what would be the minimally destroying changes to >> remove [z] from the language or to remove {dz} instead so that Mandarin >> speakers can use t͡s to mean [z]. I know that replacing "voiced/voiceless" >> distinction with "non-aspirated-semi-voiced/aspirated-voiceless" might not >> be embraced easily but since Chinese is one of the source languages may be >> something could be done to make their life happier? >> >> I suppose to do that one needs to always insert buffer between {dz}, >> never pronounce {dz} as an affricate and may be even always insert {y} in >> {radzu'e}. >> > > I never knew that [z] was an allophone of Mandarin /t͡s/. > [...] Content analysis details: (0.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: docs.google.com] 2.7 DNS_FROM_AHBL_RHSBL RBL: Envelope sender listed in dnsbl.ahbl.org [listed in googlegroups.com.rhsbl.ahbl.org. IN] [A] -0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3) [74.125.82.189 listed in wl.mailspike.net] 0.0 T_HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -0.0 SPF_PASS SPF: sender matches SPF record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gleki.is.my.name[at]gmail.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED 0.0 HTML_MESSAGE BODY: HTML included in message -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 0.0 T_FREEMAIL_FORGED_FROMDOMAIN 2nd level domains in From and EnvelopeFrom freemail headers are different -0.0 RCVD_IN_MSPIKE_WL Mailspike good senders --047d7b5d348c266ba7050cef7a48 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2015-01-18 18:46 GMT+03:00 Mike S. : > On Sat, Jan 17, 2015 at 10:03 AM, Gleki Arxokuna < > gleki.is.my.name@gmail.com> wrote: > >> Today I was reminded of one "flaw" in phonology namely, the presense of >> [z] in Lojban. >> >> Mandarin doesn't have it/has it as an allophone of t=CD=A1s. >> >> >> https://docs.google.com/document/d/1_w-c7yM6beFUc_G-XCSLlRfrCewhQosFdQuP= D1DwhuU/edit?usp=3Ddrive_web >> >> So my question is: what would be the minimally destroying changes to >> remove [z] from the language or to remove {dz} instead so that Mandarin >> speakers can use t=CD=A1s to mean [z]. I know that replacing "voiced/voi= celess" >> distinction with "non-aspirated-semi-voiced/aspirated-voiceless" might n= ot >> be embraced easily but since Chinese is one of the source languages may = be >> something could be done to make their life happier? >> >> I suppose to do that one needs to always insert buffer between {dz}, >> never pronounce {dz} as an affricate and may be even always insert {y} i= n >> {radzu'e}. >> > > I never knew that [z] was an allophone of Mandarin /t=CD=A1s/. > I only heard it from some speakers. I'm not an expert. May be it's some dialectal variation close but not equal to Beijing dialect. > I am curious, do you know how well Mandarin speakers manage with > Lojban's voiced plosives /b d g/? Are [b d g] allophones of Mandarin /p = t > k/? > IMO, most of them can be rather semi-voiced than fully voiced except [g] probably. But how would they otherwise perceive [b] if not as [p]? As for when we do need to express [p] we would probably have to always aspirate it to make Chinese Lojbanists understand more easily what we are saying. And this is how I mapped the phonologies of the two languages. The result is that only [v] and [z] can pose problems. --=20 You received this message because you are subscribed to the Google Groups "= BPFK" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bpfk-list+unsubscribe@googlegroups.com. To post to this group, send email to bpfk-list@googlegroups.com. Visit this group at http://groups.google.com/group/bpfk-list. For more options, visit https://groups.google.com/d/optout. --047d7b5d348c266ba7050cef7a48 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2015-01-18 18:46 GMT+03:00 Mike S. <maikxlx@gmail.com>:<= br>
On Sat, Jan 17, 2015 a= t 10:03 AM, Gleki Arxokuna <gleki.is.my.name@gmail.com> wrote:
Today I was reminded of one "flaw" in phonology namely, = the presense of [z] in Lojban.

Mandarin doesn't have= it/has it as an allophone of=C2=A0t=CD=A1s.


So my question is: what would be the min= imally destroying changes to remove [z] from the language or to remove {dz}= instead so that Mandarin speakers can use=C2=A0t=CD=A1s to mean [z]. I kno= w that replacing "voiced/voiceless" distinction with "non-as= pirated-semi-voiced/aspirated-voiceless" might not be embraced easily = but since Chinese is one of the source languages may be something could be = done to make their life happier?

I suppose to do t= hat one needs to always insert buffer between {dz}, never pronounce {dz} as= an affricate and may be even always insert {y} in {radzu'e}.=C2=A0

I never knew that [z] = was an allophone of Mandarin /t=CD=A1s/.

I only heard it from some speakers. I'm not an ex= pert. May be it's some dialectal variation close but not equal to Beiji= ng dialect.
=C2=A0
=C2=A0 = I am curious, do you know how well Mandarin speakers manage with Lojban'= ;s voiced plosives /b d g/?=C2=A0 Are [b d g] allophones of Mandarin /p t k= /?

IMO, most of= them can be rather semi-voiced than fully voiced except [g] probably. But = how would they otherwise perceive [b] if not as [p]?

As for when we do need to express [p] we would probably have to always a= spirate it to make Chinese Lojbanists understand more easily what we are sa= ying.

And this is how I mapped the phonologies of = the two languages. The result is that only [v] and [z] can pose problems.

--
You received this message because you are subscribed to the Google Groups &= quot;BPFK" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bpfk-list= +unsubscribe@googlegroups.com.
To post to this group, send email to bpfk-list@googlegroups.com.
Visit this group at ht= tp://groups.google.com/group/bpfk-list.
For more options, visit http= s://groups.google.com/d/optout.
--047d7b5d348c266ba7050cef7a48--