Received: from mail-yh0-f64.google.com ([209.85.213.64]:40089) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XWsnm-0006In-9x for lojban-beginners-archive@lojban.org; Wed, 24 Sep 2014 13:04:53 -0700 Received: by mail-yh0-f64.google.com with SMTP id z6sf915198yhz.19 for ; Wed, 24 Sep 2014 13:04:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=9cE2rJ2ehExrkPqtqja+Z3T1IyVBv0XArCo5juk9KOk=; b=EkW0SGakPqH0CsWc+/wIMuU41nrprZxqijoXInA+uxTUp5eijDQ60K6DbuWCikX1Qu UJ3ur2hueYGmv6OwkqX0OKUY3Rdkzm5zZCvX6Nszb+8ThVf2iv759zlsxMTzmHKoeN6F GbWrKyYGNC+xht7m4gWCckSrVFuq7cpI/d6WS06VM8iyv+umhpJyxZmliZ/aMyIzoq1e ieTDt08Fp7BXce3MMoZ/Ziib2fygkvgNaU4jbn8SulibTWI1tvi6KzEMN0zH2hyQvloL wAT4TYSh40HlAsGnBgVInv8QzyBlOjE4zh6wrjb0Dx6//fQFE2LA711M20Zns+u23xDD 32Dw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=9cE2rJ2ehExrkPqtqja+Z3T1IyVBv0XArCo5juk9KOk=; b=R1R9/x+16ZhewF4OSQNWsn/xM8YsSQMJkQUFQnhw/pTsEFeptRlr9WLC6R0Uy1xLp1 daq+uHG4804+pb3U5dNF4NDyWxKMyiC4h/NP0/vGLME+XaaGrrejxArZfzjiWda3LKzF ICP9ImsxiWrfUSFcBQYJTr6LGjYewF7kTQ255vcaDPOohoOYSoTuvFV5HxM2+ddWTBZP M2gGQjLUFI8/rXdUxyDBFeucgEn38YOf0XJfb+bwLk461pQDhroX3khyVsbNRMC0ix67 +aVnB/NZOSaUT6JC7out/Ehn7G0ChTiC8Te6CSD42msfr/5R79WGfOWd6IbdjnpicN1i CZbQ== X-Received: by 10.140.30.246 with SMTP id d109mr66086qgd.7.1411589071756; Wed, 24 Sep 2014 13:04:31 -0700 (PDT) X-BeenThere: lojban-beginners@googlegroups.com Received: by 10.140.23.134 with SMTP id 6ls644284qgp.45.gmail; Wed, 24 Sep 2014 13:04:30 -0700 (PDT) X-Received: by 10.140.18.161 with SMTP id 30mr18292qgf.31.1411589070730; Wed, 24 Sep 2014 13:04:30 -0700 (PDT) Date: Wed, 24 Sep 2014 13:04:30 -0700 (PDT) From: TR NS To: lojban-beginners@googlegroups.com Message-Id: In-Reply-To: References: Subject: Re: [lojban-beginners] oi bei MIME-Version: 1.0 X-Original-Sender: transfire@gmail.com Reply-To: lojban-beginners@googlegroups.com Precedence: list Mailing-list: list lojban-beginners@googlegroups.com; contact lojban-beginners+owners@googlegroups.com List-ID: X-Google-Group-Id: 300742228892 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="----=_Part_6765_1685102152.1411589070103" X-Spam-Score: -2.0 (--) X-Spam_score: -2.0 X-Spam_score_int: -19 X-Spam_bar: -- Content-Length: 6527 ------=_Part_6765_1685102152.1411589070103 Content-Type: text/plain; charset=UTF-8 On Wednesday, September 24, 2014 2:59:21 PM UTC-4, Ian Johnson wrote: > > On Wed, Sep 24, 2014 at 11:26 AM, TR NS > > wrote: > >> >> Considering the reasoning, it seems to me that the most concise solution >> would be to have two different cmavo for {be}. One that only takes a single >> sumti, and another that can take any number but has to be terminated. >> >> This would be harder to learn, and it would require an amount of > forethought that isn't really worth the amount of word savings it would > provide. > > Also, {bei} can be very useful for terminator elision. Another artificial > example: > > {.i broda be lo nu brode lo nu brodi lo nu brodo lo nu brodo bei ko'a} > > Writing that with {be*}, you would need: > > {.i broda be* lo nu brode lo nu brodi lo nu brodo lo nu brodo kei kei kei > kei ko'a} > > which is both much more verbose and much more difficult to read. > > Not so much difficult to read as it is to say b/c you have keep count of all those {nu}. It's easy as long as there is a wa to close them all at once as you point out. But as it stands, conversely one has: {.i broda be lo nu brode bei lo nu brodi bei lo nu brodo bei lo nu brodo bei ko'a} Which is quite verbose. And then what happens if anther {be} shows up? {.i broda be lo nu brode bei lo nu brodi be lo nu brodo bei lo nu brodo bei ko'a} While it is convenient that closing a previous clause (of a different selma'o) can close all those in between, I don't think it should be a defacto substitute for actually having an explicit means of doing that, e.g. with the example: {.i broda be* lo nu brode lo nu brodi lo nu brodo lo nu brodo kei kei kei kei ko'a} shouldn't there be something like {vau} but allows one to specify the cmavo. For the sake of discussion, let's call it {vau*}. {.i broda be* lo nu brode lo nu brodi lo nu brodo lo nu brodo vau* kei ko'a} Actually I would prefer {vau* nu}, but in either case, it is much more explicit this way. -- You received this message because you are subscribed to the Google Groups "Lojban Beginners" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban-beginners+unsubscribe@googlegroups.com. To post to this group, send email to lojban-beginners@googlegroups.com. Visit this group at http://groups.google.com/group/lojban-beginners. For more options, visit https://groups.google.com/d/optout. ------=_Part_6765_1685102152.1411589070103 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wednesday, September 24, 2014 2:59:21 PM UTC-4,= Ian Johnson wrote:
On Wed, Sep 24, 2014 at 11:26 AM, TR = NS <tran...@gmail= .com> wrote:

Considering the reasoning, it see= ms to me that the most concise solution would be to have two different cmav= o for {be}. One that only takes a single sumti, and another that can take a= ny number but has to be terminated. 

This would be harder to learn, and it w= ould require an amount of forethought that isn't really worth the amount of= word savings it would provide.

Also, {bei} can be very useful for = terminator elision. Another artificial example:

{.i broda= be lo nu brode lo nu brodi lo nu brodo lo nu brodo bei ko'a}

=
Writing that with {be*}, you would need:

{.i broda be* lo nu br= ode lo nu brodi lo nu brodo lo nu brodo kei kei kei kei ko'a}

=
which is both much more verbose and much more difficult to read.

Not so much diff= icult to read as it is to say b/c you have keep count of all those {nu}. It= 's easy as long as there is a wa to close them all at once as you point out= . But as it stands, conversely one has:

  &nb= sp; {.i broda be lo nu brode bei lo nu brodi bei lo nu brodo bei lo nu brod= o bei ko'a}

Which is quite verbose. And then what = happens if anther {be} shows up?

    {.i= broda be lo nu brode bei lo nu brodi be lo nu brodo bei lo nu brodo bei ko= 'a}
 
While it is convenient that closing = a previous clause (of a different selma'o) can close all those in between, = I don't think it should be a defacto substitute for actually having an expl= icit means of doing that, e.g. with the example:

&= nbsp;   {.i broda be* lo nu brode lo nu brodi lo nu brodo lo nu brodo = kei kei kei kei ko'a}

shouldn't there be somet= hing like {vau} but allows one to specify the cmavo. For the sake of discus= sion, let's call it {vau*}.

    {.i brod= a be* lo nu brode lo nu brodi lo nu brodo lo nu brodo vau* kei ko'a}

Actually I would prefer {vau* nu}, but in either cas= e, it is much more explicit this way.

--
You received this message because you are subscribed to the Google Groups &= quot;Lojban Beginners" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lo= jban-beginners+unsubscribe@googlegroups.com.
To post to this group, send email to lojban-beginners@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban-beginners.
For more options, visit http= s://groups.google.com/d/optout.
------=_Part_6765_1685102152.1411589070103--