Received: from mail-qa0-f63.google.com ([209.85.216.63]:56207) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1V4BTJ-0005mo-Ai; Tue, 30 Jul 2013 08:04:26 -0700 Received: by mail-qa0-f63.google.com with SMTP id u10sf1505920qaz.18 for ; Tue, 30 Jul 2013 08:04:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=cc+wxcR8LkmfZUrNomt2J1nTc6gkLU9CNCQWSx6iKg0=; b=Uem7yVWs/UkWRNy99qdCEdUeBMnVlal3POTGrPcIP4yV+58AgBC/GA1eKTUYOt6O3w 8qkt1vlCw/89LTivx0XFSRmNTSEqpjgBEWiRLQq6TUK1FOgEOjjPYWJzhQwgZzgZ55k0 Z979b57B0gAhgI/Iw7kCBEpKm39tG4kXcaxgZHMVAYMVEx3r+r8IG7SHY7fUxNc71bCe 8lZWrbALvh0zwg7XPdYS1JOd3Kl8CuSJSGeC2aO63tAEBGkGRuBc4ME2PU/SI9QAXwgB uEiHRj4kW3IyYzSlAbptJxPwTeey29Pug22sMz+ibKbaNbsyTNUJw8idvXwE17JjKaFi qgZQ== X-Received: by 10.49.81.208 with SMTP id c16mr900782qey.34.1375196644711; Tue, 30 Jul 2013 08:04:04 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.49.0.66 with SMTP id 2ls240247qec.47.gmail; Tue, 30 Jul 2013 08:04:04 -0700 (PDT) X-Received: by 10.224.137.137 with SMTP id w9mr54340590qat.6.1375196644499; Tue, 30 Jul 2013 08:04:04 -0700 (PDT) Received: by 10.224.22.74 with SMTP id m10msqab; Tue, 30 Jul 2013 07:58:49 -0700 (PDT) X-Received: by 10.49.116.243 with SMTP id jz19mr434084qeb.6.1375196329542; Tue, 30 Jul 2013 07:58:49 -0700 (PDT) Date: Tue, 30 Jul 2013 07:58:49 -0700 (PDT) From: la selpa'i ku To: bpfk-list@googlegroups.com Message-Id: <8c26769d-d067-4165-8fd6-7cd133301431@googlegroups.com> In-Reply-To: <20130709161957.GA16990@stodi.digitalkingdom.org> References: <20130709161957.GA16990@stodi.digitalkingdom.org> Subject: [bpfk] Re: Fiat Attempt #2 MIME-Version: 1.0 X-Original-Sender: seladwa@gmx.de 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: Sender: bpfk-list@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="----=_Part_50_5985025.1375196329220" X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / ------=_Part_50_5985025.1375196329220 Content-Type: text/plain; charset=ISO-8859-1 Am Dienstag, 9. Juli 2013 18:19:57 UTC+2 schrieb Robin Powell: > > > I would like to define the defaults for {za'u} and {me'i} to be > "contextually specified, usually the current value for the thing > under discussion", rather than {pa}. > I always take {me'i} as {me'i ro}, and {za'u} indeed as {za'u pa}. I find this useful, because "plurality" is something that is often relevant: {lo za'u mei} gives us a plurality with very few syllables. {lo za'u pa mei} is much less elegant in my opinion. > Two reasons: > > 1. {za'u} and {su'o} mean almost exactly the same thing as > currently defined, similarily {me'i} and {su'e}. Freaking annoying. > As noted, they are similar, but e.g. < and <= are not the same, and having differenent words for them is useful. > 2. Everybody uses them that way anyways; see {za'u re'u}, which is > very common, and has almost no meaning without this change: > http://corpus.lojban.org/corpus/search/za'ure'u?showall=y and > http://corpus.lojban.org/corpus/search/za'u%20re'u?showall=y > {za'u [pa] re'u} means "not for the first time" or "for the more-than-1-th time". If {xo'e} is {mu}, say, then {za'u mu re'u} doesn't mean "again" either; it means "for more-than-the-5-th time". You need to either say the exact number (which is often impossible to count), or just say "za'u pa re'u", which means "I'm doing this, and I've done it before", which is pretty close to "again". Yet another approach would be to use {[vei] xo'e su'i pa re'u}, but it needs to be made grammatical first. > > In addition, it would give me a clean way to say "I need more flour > for this cake", or whatever. > I think it comes down to what is perceived as the more common situation; the times where you want an elliptical number or the times where you want a clear default of {pa} (or {ro}). Choosing the former means having to add more syllables in the latter case, and vice versa. I just don't see very clearly how {xo'e} is a much better default than {pa} for {za'u} and {ro} for {me'i}. mu'o mi'e la selpa'i -- 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/groups/opt_out. ------=_Part_50_5985025.1375196329220 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am Dienstag, 9. Juli 2013 18:19:57 UTC+2 schrieb Robin Powell:

I would like to define the defaults for {za'u} and {me'i} to be
"contextually specified, usually the current value for the thing
under discussion", rather than {pa}.

I always = take {me'i} as {me'i ro}, and {za'u} indeed as {za'u pa}. I find this usefu= l, because "plurality" is something that is often relevant:

{lo za'u= mei} gives us a plurality with very few syllables. {lo za'u pa mei} is muc= h less elegant in my opinion. 
 
Two reasons:

1.  {za'u} and {su'o} mean almost exactly the same thing as
currently defined, similarily {me'i} and {su'e}.  Freaking annoyin= g.

As noted, they are similar, but e.g. < and <= ;=3D are not the same, and having differenent words for them is useful.&nbs= p;
 
2= .  Everybody uses them that way anyways; see {za'u re'u}, which is
very common, and has almost no meaning without this change:
http://corpus.lojban.org/corpus/search/za'ure'u?showall=3Dy and
http://corpus.lojban.org/corpus/search/za'u%20= re'u?showall=3Dy

{za'u [pa] re'u} means "not for the first time" o= r "for the more-than-1-th time".

If {xo'e} is {mu}, say, then {za'u= mu re'u} doesn't mean "again" either; it means "for more-than-the-5-th tim= e".

You need to either say the exact number (which is often impossib= le to count), or just say "za'u pa re'u", which means "I'm doing this, and = I've done it before", which is pretty close to "again".

Yet another = approach would be to use {[vei] xo'e su'i pa re'u}, but it needs to be made= grammatical first.
 

In addition, it would give me a clean way to say "I need more flour
for this cake", or whatever.

I think it comes down to what is perceived as the= more common situation; the times where you want an elliptical number or th= e times where you want a clear default of {pa} (or {ro}). Choosing the form= er means having to add more syllables in the latter case, and vice versa.
I just don't see very clearly how {xo'e} is a much better default tha= n {pa} for {za'u} and {ro} for {me'i}.

mu'o mi'e la selpa'i

--
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 https://groups.google.com/groups/opt_out.
 
 
------=_Part_50_5985025.1375196329220--