Received: from mail-la0-f55.google.com ([209.85.215.55]:61197) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1YCUuu-0005gr-TL; Sat, 17 Jan 2015 07:04:01 -0800 Received: by mail-la0-f55.google.com with SMTP id ms9sf101365lab.0; Sat, 17 Jan 2015 07:03:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version: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=MPgdWs4ag2qZFkvZzpZ6fNc/t9fKcGRivlflksBfpZI=; b=pUBQaJa2wtk4MN6DtvY8Q6JscJoZPWnlY8xrp5E3ZQF8PT0F93bGHtIkQl8r3pLmLu 0czRZ8FW4et0CM79BzjETWbNV2g2lnpiKpcAMqJimw1biyS4LLckWib16s5sY1X8/HDh KamzCWVs1zmVVbJYa7ooSO2DhTxMVyVcJseZrLlJMddU5MU8xLSJQEdNM9ev2ABlV5mI USbzKnExiQZMYVolHzpF3T8E/+2RTOFdYJVQ/F/LnfRO+y7Gp55xCBbXDPi/ehqeriZ5 8MMOR8Hofim5xhOH8mbnwm/vmp0u235Mim1f2lzXPdTH3pFtKN0bjTodh7nv1xlPYPkr SUYw== X-Received: by 10.180.208.67 with SMTP id mc3mr60668wic.20.1421507032777; Sat, 17 Jan 2015 07:03:52 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.180.75.48 with SMTP id z16ls507005wiv.28.canary; Sat, 17 Jan 2015 07:03:52 -0800 (PST) X-Received: by 10.180.89.211 with SMTP id bq19mr1037846wib.4.1421507032522; Sat, 17 Jan 2015 07:03:52 -0800 (PST) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com. [2a00:1450:400c:c05::233]) by gmr-mx.google.com with ESMTPS id s6si495126wif.0.2015.01.17.07.03.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 17 Jan 2015 07:03:52 -0800 (PST) Received-SPF: pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c05::233 as permitted sender) client-ip=2a00:1450:400c:c05::233; Received: by mail-wi0-f179.google.com with SMTP id ho1so8955782wib.0 for ; Sat, 17 Jan 2015 07:03:52 -0800 (PST) X-Received: by 10.180.20.177 with SMTP id o17mr16925819wie.64.1421507032423; Sat, 17 Jan 2015 07:03:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.86.200 with HTTP; Sat, 17 Jan 2015 07:03:32 -0800 (PST) From: Gleki Arxokuna Date: Sat, 17 Jan 2015 18:03:32 +0300 Message-ID: Subject: [bpfk] Question on {z} vs. {dz} and {ts} To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=bcaec53d5b4bb6a47c050cda6533 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:c05::233 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: 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 [...] Content analysis details: (0.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 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 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: googlegroups.com] -0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3) [209.85.215.55 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 Content-Length: 3367 --bcaec53d5b4bb6a47c050cda6533 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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-XCSLlRfrCewhQosFdQuPD1D= whuU/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/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}. --=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. --bcaec53d5b4bb6a47c050cda6533 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Today I was reminded of one "flaw" in phonology = namely, the presense of [z] in Lojban.

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

https://docs.google.com/document/d= /1_w-c7yM6beFUc_G-XCSLlRfrCewhQosFdQuPD1DwhuU/edit?usp=3Ddrive_web
<= /div>

So my question is: what would be the minimally des= troying changes to remove [z] from the language or to remove {dz} instead s= o that Mandarin speakers can use=C2=A0t=CD=A1s to mean [z]. I know that rep= lacing "voiced/voiceless" distinction with "non-aspirated-se= mi-voiced/aspirated-voiceless" might not be embraced easily but since = Chinese is one of the source languages may be something could be done to ma= ke their life happier?

I suppose to do that one ne= eds to always insert buffer between {dz}, never pronounce {dz} as an affric= ate and may be even always insert {y} in {radzu'e}.=C2=A0

--
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.
--bcaec53d5b4bb6a47c050cda6533--