Received: from mail-ob0-f191.google.com ([209.85.214.191]:33093) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1YrS1t-0006Qd-Ay for lojban-list-archive@lojban.org; Sun, 10 May 2015 07:16:40 -0700 Received: by obbnt9 with SMTP id nt9sf29642598obb.0 for ; Sun, 10 May 2015 07:16:23 -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 :content-type:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=+xrbkGkfY/CGxkvLVuOob2mQi3AiBYSK0IFuu5L2lek=; b=w48XU0KnRF5pZGTEZsrzMgvJUSq0OdHeGuwR5JluH0vChIF+eBuDP1wSHa3HByCZtD ToEdmvUsiqwbqWCtUwqlf/9A3t4YziQHtlpAnkA/GvJ8MMnUAmIbsRDaLTocSn6xbgqO cCQGiA/BGfFN2QtpQST1Ovxg3L1Vb8Z5crgKeAgUwF4fghQUo/FlbMEBgtGcHZWhp2wP bIdB/Ks/IfW5xu67R8DGtFpsZUOZsmxqSYBzDaVlhqFDGtk3yA1lojZYqmArfMt/oLZu qPfJuP4f4bByvS69aNhqcM/4mECx6FcwizyUhtXMK9u1wfcWQWAR+VhZE1IvLsFYmRqr FUfQ== 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 :content-type:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=+xrbkGkfY/CGxkvLVuOob2mQi3AiBYSK0IFuu5L2lek=; b=b7iySdI23coecY6ytIbn7CaXOK3BRpWCtQWaXtfw/VpykC2bf0maD3uvinFP8akcR5 SFmd5VF3q+cGVIuNsj3yQgSr+7ERBA9juPSdopL/pL5GSpcXKdukblwofqZoDPLsgnjW DfGYnK1h50C2ja4BRIW8PrqTY3mExXTBVP1UYpWx2b1eAQYribz/VzkEEpt//FlhtwVt kkQKD577X10bHtDSY9HpYdR+XPlcMcYx97uvjndsB4ITU7kygw+zL+hzUGHkqLC/Z1FM 57YFPVXjPQYGbJsoRomRgn2ypjQbIwxXusX/HfTarSTuViL11zYpbpYdr1GpHWm3u+h0 GSiA== X-Received: by 10.50.66.142 with SMTP id f14mr132103igt.17.1431267383342; Sun, 10 May 2015 07:16:23 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.50.62.37 with SMTP id v5ls829473igr.32.canary; Sun, 10 May 2015 07:16:23 -0700 (PDT) X-Received: by 10.51.17.40 with SMTP id gb8mr112971igd.6.1431267383102; Sun, 10 May 2015 07:16:23 -0700 (PDT) Date: Sun, 10 May 2015 07:16:21 -0700 (PDT) From: Spheniscine To: lojban@googlegroups.com Message-Id: <8e9c9536-f830-42f3-8414-48fd3ae740d2@googlegroups.com> In-Reply-To: References: <3a378de3-6fd3-44c1-ae6e-960ef6ee27ea@googlegroups.com> <4183774c-dee7-412d-80fc-a22fd8c9cc7b@googlegroups.com> Subject: Re: [lojban] Re: Proposal for new cmavo: {vau'u} MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_4074_1147957048.1431267381983" X-Original-Sender: spheniscine@gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - ------=_Part_4074_1147957048.1431267381983 Content-Type: multipart/alternative; boundary="----=_Part_4075_721021088.1431267381983" ------=_Part_4075_721021088.1431267381983 Content-Type: text/plain; charset=UTF-8 ({ju'o ru'e} I am a programmer but am not familiar with the gritty details of Lojban grammar parsing) Perhaps we could make {vau'u} the famyma'o of the unit of a sentence (though in attempting to make sense of the parser output, my second bridi-less sentence doesn't seem to produce a structure called "sentence"; is there no structure that describes the construct between two {.i}, or between the start of the text / NIhO and the first {.i}?). Or if it's too difficult to come up with a solution now, we could treat VAUhU like I as a temporary "hack" solution. On Sunday, May 10, 2015 at 9:12:14 PM UTC+8, Latro wrote: > > That's actually pretty hard to my understanding. When you have an {.i}, > basically everything left outstanding has to be over because now a > "sentence" construct is over. There is no corresponding construct for this > situation. So while it would be easy in principle to just backtrack and > count, this isn't actually how the grammar works. Indeed, if this were how > the grammar works it would be a lot harder to be sure that it is correct. > > mi'e la latro'a mu'o > > On Sun, May 10, 2015 at 9:00 AM, Spheniscine > wrote: > >> Actually, instead of pretending to be a string of {vau}, perhaps it'd be >> better just for it to auto-close with all famyma'o that a simple {.i} would >> (but without actually starting a new sentence). This way it can even close >> off sentences that do not actually have bridi (and thus no possible {vau}); >> for example {coi lo tavla pe la .lojban. vau'u ui}. Will probably be easier >> to code too. >> >> On Sunday, May 10, 2015 at 4:04:48 PM UTC+8, Spheniscine wrote: >>> >>> I think it might be useful to have a new cmavo, {vau'u}, which is in its >>> own selma'o. It would act as a "super famyma'o / super vau"; acting as any >>> number of {vau}s needed to close off a sentence. >>> >>> Why? Attitudinals, mostly; it'd allow adding attitudinals as an >>> afterthought, attaching it to the entire sentence rather than the last >>> thing in it. {vau} is sufficient for simple sentences (e.g. {do sidju mi >>> vau ui}), but more complex sentences with subclauses at the end may require >>> several {vau}, which just feels wrong. For example >>> >>> Instead of: {do sidju mi lo nu mi zenba lo ni ricfu vau vau vau ui} >>> You can have: {do sidju mi lo nu mi zenba lo ni ricfu vau'u ui} >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "lojban" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to lojban+un...@googlegroups.com . >> To post to this group, send email to loj...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/lojban. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout. ------=_Part_4075_721021088.1431267381983 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
({ju'o ru'e} I am a programmer but am not familiar with th= e gritty details of Lojban grammar parsing)

Perhaps we c= ould make {vau'u} the famyma'o of the unit of a sentence (though in attempt= ing to make sense of the parser output, my second bridi-less sentence doesn= 't seem to produce a structure called "sentence"; is there no structure tha= t describes the construct between two {.i}, or between the start of the tex= t / NIhO and the first {.i}?). Or if it's too difficult to come up with a s= olution now, we could treat VAUhU like I as a temporary "hack" solution.

On Sunday, May 10, 2015 at 9:12:14 PM UTC+8, Latro wrote:
That's actually = pretty hard to my understanding. When you have an {.i}, basically everythin= g left outstanding has to be over because now a "sentence" construct is ove= r. There is no corresponding construct for this situation. So while it woul= d be easy in principle to just backtrack and count, this isn't actually how= the grammar works. Indeed, if this were how the grammar works it would be = a lot harder to be sure that it is correct.

mi'e la latro'a mu= 'o

On Sun, May 10, 2015 at 9:0= 0 AM, Spheniscine <sphen...@gmail.com> wrote:
Actually, instead of pretending to be = a string of {vau}, perhaps it'd be better just for it to auto-close with al= l famyma'o that a simple {.i} would (but without actually starting a new se= ntence). This way it can even close off sentences that do not actually have= bridi (and thus no possible {vau}); for example {coi lo tavla pe la .lojba= n. vau'u ui}. Will probably be easier to code too.

On Sun= day, May 10, 2015 at 4:04:48 PM UTC+8, Spheniscine wrote:
I think it might be useful to have = a new cmavo, {vau'u}, which is in its own selma'o. It would act as a "super= famyma'o / super vau"; acting as any number of {vau}s needed to close off = a sentence.

Why? Attitudinals, mostly; it'd allow adding= attitudinals as an afterthought, attaching it to the entire sentence rathe= r than the last thing in it. {vau} is sufficient for simple sentences (e.g.= {do sidju mi vau ui}), but more complex sentences with subclauses at the e= nd may require several {vau}, which just feels wrong. For example

Instead of: {do sidju mi lo nu mi zenba lo ni ricfu vau vau= vau ui} 
You can have: {do sidju mi lo nu mi zenba lo ni ri= cfu vau'u ui}

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+un...@= googlegroups.com.
To post to this group, send email to loj...@googlegroups.com.
Visit this group at http://groups.google.com/group/l= ojban.
For more options, visit https://groups.google.com/d/optout.

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