Received: from mail-yw0-f61.google.com ([209.85.213.61]:36347) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1T2o8M-0005ny-8W; Sat, 18 Aug 2012 11:52:38 -0700 Received: by yhoo21 with SMTP id o21sf5162300yho.16 for ; Sat, 18 Aug 2012 11:52:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:x-original-authentication-results :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=LljZBYtM0aIpbtu1MOWiBKmyQufNclFE2RP7kl7mR5w=; b=tR1xOboy2ZJhotR9mTxYu/NWNZkHBjcLAMiIAmAyYLg6xUcF1jjSEMTKcUXaD/i5XN qc+3P9Qvny205LMGwCmuYkOP1Q/UI3KdLa4VM2E/BBAGUF/rH9EQJ5WINL8JYCCL8cUB 0btd9w0c5+V0T2xrqtH/mZT27Lfptfslq3Poc= Received: by 10.236.87.71 with SMTP id x47mr2666177yhe.6.1345315943133; Sat, 18 Aug 2012 11:52:23 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.101.48.8 with SMTP id a8ls1861924ank.0.gmail; Sat, 18 Aug 2012 11:52:22 -0700 (PDT) Received: by 10.236.170.7 with SMTP id o7mr2718845yhl.3.1345315942504; Sat, 18 Aug 2012 11:52:22 -0700 (PDT) Date: Sat, 18 Aug 2012 11:52:21 -0700 (PDT) From: la gleki To: lojban@googlegroups.com Message-Id: In-Reply-To: <536d8399-344f-41e4-9315-27c7d8c95176@googlegroups.com> References: <16cab846-3f84-4bc6-b64f-56aeab08244b@googlegroups.com> <536d8399-344f-41e4-9315-27c7d8c95176@googlegroups.com> Subject: [lojban] Re: Let's move {soi} to JOI. And why can't places be interconnected in lojban predicates? MIME-Version: 1.0 X-Original-Sender: gleki.is.my.name@gmail.com X-Original-Authentication-Results: ls.google.com; spf=pass (google.com: domain of gleki.is.my.name@gmail.com designates internal as permitted sender) smtp.mail=gleki.is.my.name@gmail.com; dkim=pass header.i=@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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="----=_Part_301_29564695.1345315941526" X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / ------=_Part_301_29564695.1345315941526 Content-Type: text/plain; charset=ISO-8859-1 On Saturday, August 18, 2012 10:14:29 PM UTC+4, djandus wrote: > > Whenever I first learned {soi}, I had a similar thought, but slightly > different. It's not to take SOI and make it JOI, because that's basically > completely undesired. Instead, it would say: > > Use SOI like JOI between sumti, but *only* between sumti. (SOI thus > allows {ku} elision) SOI, like JOI, is allowed to make a SOI series. ({ko'a > soi ko'e soi ko'i} is allowed.) SOI asserts that all sumti in the series > can be swapped in any order without changing the validity of the overall > bridi. Otherwise, you can remove all SOI (and insert the possibly elided > {ku} where necessary) and parse the bridi exactly. (So every sumti still > falls into the place structure as if SOI wasn't there, except that the > components of the series can be swapped and replaced in any order.) > > The benefit is that > mi prami do soi vo'a vo'e > is shortened to > mi soi do prami > And even more beneficial are longer statements, such as > mi bevri lo tanxe ku ti soi tu ca'o bi cacra ca lo cabdei > "I carried boxes there and back for eight hours today." > (In the current system, the placement of {soi} is rather annoying as well, > as it kind of... sucks, no matter where you put it.) > > The main reason I had for the idea was that Lojban goes through so much > effort to allow any place structure order that it is *always* the case > that {soi} could be between the necessary sumti, with proper rearranging. > Secondarily, it allows the extension of "vice-versa" to include multiple > items. (The current SOI uses the restriction of requiring exactly two items > to help with VOhA elision.) > > However, this type of change sorely disagrees with current usage > Pardon, current usage? Does anybody use it? How many times in the corpus it is met? Even L4B mentions it as unsettled and the CLL has two different examples without proper explanations. It sounds more like a waste of precious cmavo space. > , so a new word would be more proper than a replacement. > > On a complete side note, I also dislike the current SOI process as it > feels like it was created with lame reasons behind it. I get the feeling > that somebody came up with VOhA for reflexives and somebody didn't like > that a whole series of words was being created for one purpose. That, or > maybe somebody liked that {vo'a vo'e} parallels "vice-versa" phonetically. > Both of which are pretty lame reasons to not think of a better way of doing > things. > > And on a final side note, I would also like to mention that the > reciprocity should be able to be expressed without filling the places, as > in the current: > {mi prami soi vo'a vo'e} for "I love something (and it loves me)" > The way I would do that with my proposal would be: > {mi soi vo'e prami}, where vo'e fills the place it represents. > (Once again, if anyone actually likes this proposal, we would need a word > other than {soi} to use.) > > mu'o mi'e djos > -- You received this message because you are subscribed to the Google Groups "lojban" group. To view this discussion on the web visit https://groups.google.com/d/msg/lojban/-/RcMlhi8Frp0J. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. ------=_Part_301_29564695.1345315941526 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Saturday, August 18, 2012 10:14:29 PM UTC+4, djandus wrote:Whenever I first learned {soi}, I h= ad a similar thought, but slightly different. It's not to take SOI and make= it JOI, because that's basically completely undesired. Instead, it would s= ay:

Use SOI like JOI between sumti, but only = ;between sumti. (SOI thus allows {ku} elision) SOI, like JOI, is allowed to= make a SOI series. ({ko'a soi ko'e soi ko'i} is allowed.) SOI asserts that= all sumti in the series can be swapped in any order without changing the v= alidity of the overall bridi. Otherwise, you can remove all SOI (and insert= the possibly elided {ku} where necessary) and parse the bridi exactly. (So= every sumti still falls into the place structure as if SOI wasn't there, e= xcept that the components of the series can be swapped and replaced in any = order.)

The benefit is that
mi prami do = soi vo'a vo'e
is shortened to
mi soi do prami
And even more beneficial are longer statements, such as
mi bevri= lo tanxe ku ti soi tu ca'o bi cacra ca lo cabdei
"I carried boxe= s there and back for eight hours today."
(In the current system, = the placement of {soi} is rather annoying as well, as it kind of... sucks, = no matter where you put it.)

The main reason I had= for the idea was that Lojban goes through so much effort to allow any plac= e structure order that it is always the case that {soi} could b= e between the necessary sumti, with proper rearranging. Secondarily, it all= ows the extension of "vice-versa" to include multiple items. (The current S= OI uses the restriction of requiring exactly two items to help with VOhA el= ision.)

However, this type of change sorely disagr= ees with current usage
Pardon, current usage? Does a= nybody use it? How many times in the corpus it is met? Even L4B mentions it= as unsettled and the CLL has two different examples without proper explana= tions. It sounds more like a waste of precious cmavo space.
, so a new word would be more prope= r than a replacement.

On a complete side note, I a= lso dislike the current SOI process as it feels like it was created with la= me reasons behind it. I get the feeling that somebody came up with VOhA for= reflexives and somebody didn't like that a whole series of words was being= created for one purpose. That, or maybe somebody liked that {vo'a vo'e} pa= rallels "vice-versa" phonetically. Both of which are pretty lame reasons to= not think of a better way of doing things.

And on= a final side note, I would also like to mention that the reciprocity shoul= d be able to be expressed without filling the places, as in the current:
{mi prami soi vo'a vo'e} for "I love something (and it loves me)"
The way I would do that with my proposal would be:
{mi s= oi vo'e prami}, where vo'e fills the place it represents.
(Once a= gain, if anyone actually likes this proposal, we would need a word other th= an {soi} to use.)

mu'o mi'e djos

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To view this discussion on the web visit https://groups.google.com/d/msg/lojban/-/Rc= Mlhi8Frp0J.
=20 To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
------=_Part_301_29564695.1345315941526--