Received: from mail-wi0-f190.google.com ([209.85.212.190]:64219) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1YDoah-000141-Mu; Tue, 20 Jan 2015 22:16:36 -0800 Received: by mail-wi0-f190.google.com with SMTP id ho1sf1318204wib.7; Tue, 20 Jan 2015 22:16:28 -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=62nnVQVt/WICQtCPo33p5MR2GvcNn1vGNAj4oMLygHk=; b=LU8TiwpXMqAOKIxNJUSKUKyO7H4M2NVHbmzooslYT0dv7tmoZ2LkA2U2L78c6TZbpY t/Rr8BTIhazoXKUGO+uljwoukG5r5+q0X1xFlSYHNkhG4p4NWQHXeVoqC1tdj5sUjRrp fz+3LbyGnyK751+iUg8Bw6BxD2PdF4xIvN+ia781sgjs6M8c6gou2/tzbSyVHgpIF7EF +7lcPA2JLEGJjUCoiG0xwYp1dERVImEGNyVMrO2hQnsWP8rhM70vvRYh10vmlEkB/p/l QXR2gHYC0OV5s8fXwqz6pR8Ji1jrHdTNpV1p3l/pO8vh2f418+bvRJdJ4YsyRP3owKEr wMyQ== X-Received: by 10.180.73.13 with SMTP id h13mr190202wiv.3.1421820988451; Tue, 20 Jan 2015 22:16:28 -0800 (PST) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.180.14.8 with SMTP id l8ls1136572wic.9.canary; Tue, 20 Jan 2015 22:16:28 -0800 (PST) X-Received: by 10.180.98.199 with SMTP id ek7mr3346319wib.1.1421820988028; Tue, 20 Jan 2015 22:16:28 -0800 (PST) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com. [2a00:1450:400c:c05::234]) by gmr-mx.google.com with ESMTPS id v6si5937wiz.2.2015.01.20.22.16.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 20 Jan 2015 22:16:28 -0800 (PST) Received-SPF: pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c05::234 as permitted sender) client-ip=2a00:1450:400c:c05::234; Received: by mail-wi0-x234.google.com with SMTP id bs8so29437319wib.1 for ; Tue, 20 Jan 2015 22:16:28 -0800 (PST) X-Received: by 10.194.234.2 with SMTP id ua2mr19437947wjc.40.1421820987896; Tue, 20 Jan 2015 22:16:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.86.200 with HTTP; Tue, 20 Jan 2015 22:16:07 -0800 (PST) In-Reply-To: <54BEFD5E.7030805@gmx.de> References: <54BEFD5E.7030805@gmx.de> From: Gleki Arxokuna Date: Wed, 21 Jan 2015 09:16:07 +0300 Message-ID: Subject: Re: [bpfk] ju'o / ju'o nai To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=089e0141a160eafc49050d237e84 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::234 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-21 4:14 GMT+03:00 selpa'i : > The ma'oste defines {ju'o} as follows: > > "attitudinal modifier: certainty - uncertainty - impossibility." > > If {ju'o} is to express the certainty scale, then this definition is > non-compositional. This is similar to the old {.ai nai} definition, which > BPFK changed to a much more sensible one (replacing the useless {.ai nai} > with a useful one that agrees with the scale the word is on). > > In my opinion, the {ju'o} scale should be: > > "certainty - [mild certainty] - lack of certainty / uncertainty" > > I checked the corpus and {ju'o nai} was rarely used at all, and > occasionally used in the sense of current {ju'o cu'i}. > > Just like old {.ainai} was completely redundant to {.ai na}, current {ju'o > nai} is not much different (if at all) from {ju'o na}. > > {ju'o nai} is currently a very rare word, whereas {ju'o cu'i} is extremely > common, so its length is painful (this is an actual complaint by language > users). With the proposed definition, we'd also get a slightly shorter > replacement, so it would be killing two birds with one stone. > [...] 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: googlegroups.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) [209.85.212.190 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: 6178 --089e0141a160eafc49050d237e84 Content-Type: text/plain; charset=UTF-8 2015-01-21 4:14 GMT+03:00 selpa'i : > The ma'oste defines {ju'o} as follows: > > "attitudinal modifier: certainty - uncertainty - impossibility." > > If {ju'o} is to express the certainty scale, then this definition is > non-compositional. This is similar to the old {.ai nai} definition, which > BPFK changed to a much more sensible one (replacing the useless {.ai nai} > with a useful one that agrees with the scale the word is on). > > In my opinion, the {ju'o} scale should be: > > "certainty - [mild certainty] - lack of certainty / uncertainty" > > I checked the corpus and {ju'o nai} was rarely used at all, and > occasionally used in the sense of current {ju'o cu'i}. > > Just like old {.ainai} was completely redundant to {.ai na}, current {ju'o > nai} is not much different (if at all) from {ju'o na}. > > {ju'o nai} is currently a very rare word, whereas {ju'o cu'i} is extremely > common, so its length is painful (this is an actual complaint by language > users). With the proposed definition, we'd also get a slightly shorter > replacement, so it would be killing two birds with one stone. > pe'i lo'u ju'onai li'u ka'e plixau i mu'a di'e ju'onai xu lo tai valsi cu se pilno Are such words used? I'm sure they are not! i pe'i lo'u ju'o xu li'o na co'e le'u na mapti va'o > > Any thoughts? > > mi'e la selpa'i mu'o > > -- > 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 > email 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. > -- 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 email 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. --089e0141a160eafc49050d237e84 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2015-01-21 4:14 GMT+03:00 selpa'i <seladwa@gmx.de>:
=
The ma'oste defines {ju'o} as follows:

=C2=A0 =C2=A0 "attitudinal modifier: certainty - uncertainty - impossi= bility."

If {ju'o} is to express the certainty scale, then this definition is no= n-compositional. This is similar to the old {.ai nai} definition, which BPF= K changed to a much more sensible one (replacing the useless {.ai nai} with= a useful one that agrees with the scale the word is on).

In my opinion, the {ju'o} scale should be:

=C2=A0 =C2=A0 "certainty - [mild certainty] - lack of certainty / unce= rtainty"

I checked the corpus and {ju'o nai} was rarely used at all, and occasio= nally used in the sense of current {ju'o cu'i}.

Just like old {.ainai} was completely redundant to {.ai na}, current {ju= 9;o nai} is not much different (if at all) from {ju'o na}.

{ju'o nai} is currently a very rare word, whereas {ju'o cu'i} i= s extremely common, so its length is painful (this is an actual complaint b= y language users). With the proposed definition, we'd also get a slight= ly shorter replacement, so it would be killing two birds with one stone.

pe'i lo'u ju'onai li'u ka= 'e plixau i mu'a di'e

ju'onai xu l= o tai valsi cu se pilno
Are such words used? I'm sure they ar= e not!

i pe'i lo'u ju'o xu li'o na= co'e le'u na mapti va'o

=C2=A0

Any thoughts?

mi'e la selpa'i mu'o
--
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 http://groups.google.com/group/bpfk-list.
For more options, visit https://groups.google.com/d/optout.

--
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.
--089e0141a160eafc49050d237e84--