Received: from mail-wg0-f64.google.com ([74.125.82.64]:33810) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1Z2nvp-0007nv-8l; Wed, 10 Jun 2015 14:53:17 -0700 Received: by wggx12 with SMTP id x12sf19800318wgg.1; Wed, 10 Jun 2015 14:53:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:sender:list-subscribe:list-unsubscribe; bh=wXfaJ74DgoJiWjAZTKJqSEIsFF6G5fmXCM5YfOrrifs=; b=OZMpzXloFPJWW2fJ6wRqIf0FNpFVzVyE9+VRXVB5elvoN2Re3ELiC72CPm7T4tuzb1 n9XCvXicXdRyWkYQHviSxy7qmAzrKJqFPi7wIfoKEMF6RSbrcrPixF1bb8kRNcweqyUz JPsIEiSZQlYaaM8/8OosO4bKnQxBtZ6Ps7ujAnrq5L8ROYMhvKoK6jksj8WA2+MrUp8T pv6fwD2DsbiOdrGKkzAubdbPSrSt/yOZj2WwE5CoDU4ulHhDEZqZhgSHyygTDa0Zw9tj 6WwjtVydA4xd86PwR1UmdaL5vuC473mgoL+u6aQUfhzVCZR6M97or7+0kLg85byNe1Ts irLw== X-Received: by 10.152.29.5 with SMTP id f5mr91107lah.19.1433973182288; Wed, 10 Jun 2015 14:53:02 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.178.195 with SMTP id da3ls315063lac.43.gmail; Wed, 10 Jun 2015 14:53:01 -0700 (PDT) X-Received: by 10.112.97.210 with SMTP id ec18mr4834877lbb.15.1433973181836; Wed, 10 Jun 2015 14:53:01 -0700 (PDT) Received: from mail-wi0-x242.google.com (mail-wi0-x242.google.com. [2a00:1450:400c:c05::242]) by gmr-mx.google.com with ESMTPS id bc3si316493wib.2.2015.06.10.14.53.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Jun 2015 14:53:01 -0700 (PDT) Received-SPF: pass (google.com: domain of and.rosta@gmail.com designates 2a00:1450:400c:c05::242 as permitted sender) client-ip=2a00:1450:400c:c05::242; Received: by mail-wi0-x242.google.com with SMTP id r20so11033241wiv.1 for ; Wed, 10 Jun 2015 14:53:01 -0700 (PDT) X-Received: by 10.180.13.175 with SMTP id i15mr12641299wic.30.1433973181732; Wed, 10 Jun 2015 14:53:01 -0700 (PDT) Received: from [192.168.1.208] ([95.147.224.24]) by mx.google.com with ESMTPSA id u6sm16435494wja.40.2015.06.10.14.53.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jun 2015 14:53:00 -0700 (PDT) Message-ID: <5578B1C1.4090300@gmail.com> Date: Wed, 10 Jun 2015 22:53:05 +0100 From: And Rosta User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120711 Thunderbird/14.0 MIME-Version: 1.0 To: bpfk-list@googlegroups.com Subject: Re: [bpfk] Re: Grammar of letterals and numerals in {li} References: <69108030-6005-444c-830a-26aac6447cbc@googlegroups.com> <983f5a31-9fc4-426b-9565-a315d23b6d84@googlegroups.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Original-Sender: and.rosta@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of and.rosta@gmail.com designates 2a00:1450:400c:c05::242 as permitted sender) smtp.mail=and.rosta@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-Spam-Checked-In-Group: bpfk-list@googlegroups.com X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -3.0 (---) X-Spam_score: -3.0 X-Spam_score_int: -29 X-Spam_bar: --- spheniscine@gmail.com, On 10/06/2015 09:10: > The problems with pabu / pa'y are: > > * They almost double the length of all character strings that are > heavy in digits, e.g. my date system and Pierre's coordinate system. IMO a fundamental principle of BPFK work should be not to obsess about syll= ables, for two related reasons. The first reason is that we need large usag= e corpora before we can assess which constructions are most responsible for= a potentially avoidable excess of syllables. The second reason is that onc= e equipped with that assessment, we could potentially allocate monosyllabic= cmavo in the light of it, tho this wouldn't apply to the PA'y/PAbu cases, = where one would want the longer cmavo to be morphologically related to the = basic PA. Syllable counting should be verboten in these discussions. Morpheme countin= g is okay, tho. > * As for numeral/number distinction... the problem is that that very > distinction is often hazy. Take for example the name of the game > TIS-100 ; do those numbers > actually mean "one hundred", or are they just an arbitrary string of > numerals? Etymologizing and translating names isn't a big issue. Is _Christopher_ _la= kristofer_ or _la xriso bevri_? The choice is kind of arbitrary. Ditto wit= h the alternative analyses of _TIS-100_. --And. --=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.