Received: from mail-la0-f55.google.com ([209.85.215.55]:33367) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1YsEyG-0006oX-7L for lojban-list-archive@lojban.org; Tue, 12 May 2015 11:32:05 -0700 Received: by labgd6 with SMTP id gd6sf6507362lab.0 for ; Tue, 12 May 2015 11:31:53 -0700 (PDT) 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=mmxWeImO4iONcegfGr5bXbLBUVzYKh2E2Ek9HBdOhqY=; b=T7Bt6rwGIO79ySqB4TYQWQqUUgHJR8tyyA+0XIC925iw+cv0kZOLTJhKLLBgOngSQB zg4hTiPVumFwzDmZwoRSV6Ak9KO/+ad8KW989x5NkI1HwCH7djI2voF39jU6dfsfgVNh 1KEjDkmWLly6SUCF6OTO9KEBMqrhdVQVNiwL3HnR1tgUtr51JvCnZJ42Zn0ZLjG38E6H gCf2WZtx20Iorizaysx5/8G0TBQ94QmJFjzEA+lRMFuS5yCld2HIIFPqvmUk5m4T3g54 BSLB/KyLo3Tkfb5wf1xfDyCF/phjmnE6Y8mo2wis8CIOhwCcquC29XOEPNjoZzD2OCUE LIXw== X-Received: by 10.180.76.233 with SMTP id n9mr48239wiw.20.1431455513335; Tue, 12 May 2015 11:31:53 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.180.99.3 with SMTP id em3ls152993wib.48.gmail; Tue, 12 May 2015 11:31:52 -0700 (PDT) X-Received: by 10.180.98.130 with SMTP id ei2mr2628351wib.0.1431455512813; Tue, 12 May 2015 11:31:52 -0700 (PDT) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com. [2a00:1450:400c:c05::233]) by gmr-mx.google.com with ESMTPS id m3si147744wia.1.2015.05.12.11.31.52 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 May 2015 11:31:52 -0700 (PDT) Received-SPF: pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c05::233 as permitted sender) client-ip=2a00:1450:400c:c05::233; Received: by mail-wi0-x233.google.com with SMTP id di4so166040800wid.0 for ; Tue, 12 May 2015 11:31:52 -0700 (PDT) X-Received: by 10.194.109.229 with SMTP id hv5mr33349903wjb.119.1431455512720; Tue, 12 May 2015 11:31:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.221.167 with HTTP; Tue, 12 May 2015 11:31:32 -0700 (PDT) In-Reply-To: <548fdecf-87b7-4302-b4e9-360910eff760@googlegroups.com> References: <04cecf13-9f41-4589-9e37-e3987ef53330@googlegroups.com> <496eac79-991b-43a9-bc80-d3dac65cd246@googlegroups.com> <548fdecf-87b7-4302-b4e9-360910eff760@googlegroups.com> From: Gleki Arxokuna Date: Tue, 12 May 2015 21:31:32 +0300 Message-ID: Subject: Re: [lojban] Re: Possible polysemy clashes for "regular affixes" in lujvo? To: "lojban@googlegroups.com" Content-Type: multipart/alternative; boundary=047d7b60441a58f9da0515e6b502 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::233 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: 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.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --047d7b60441a58f9da0515e6b502 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2015-05-12 20:51 GMT+03:00 iesk : > This is an interesting observation. However, there already is an > established way to deal with such apparent conflicts of (possibly) > meanings: the correct meaning is defined by the authoritative dictionary. > The problem is deeper. There are jvajvo, naljvajvo and cimjvo (the distinction between the last too is vague). It's pretty straightforward to just declare all of lujvo naljvajvo/cimjvo but then the whole idea of lujvo is ruined. What's the purpose in them if they aren't automatically expandable into bridi? Mnemonics? But then there is no need in mapping rafsi to gismu. This is in fact what it was back in 1960 with Loglan. Then {pensku} could mean {pensycusku}, not {penmycusku}. However, usage has established some patterns with using rafsi that bring them to the level of slotting, i.e. a rafsi take a certain position with a certain function and meaning (it is theoretically possible that in different position the same rafsi would have slightly different functions and expansions but I can't recall anything similar). For example, {x1 rodgau x2 [x3]} is probably always expanded into {x1 gasnu lo su'u x2 broda [x3]}. At one point there was even a project (a successful one imo) that listed most used filjvo. Another usage pattern is with -sku lujvo. They are presumed to be naljvajvo= : smusku, retsku, spusku, piksku unexpectedly break their place structure and stick to the one from {cusku}: retsku =3D> cusku lo preti piksku =3D> cusku lo pinka and that's about that. The other lujvo in this series don't follow this pattern. However, we have the pattern, we know what place structure to expect. This is much more than just mnemonic hints of rafsi. I don't know exactly how zan- and mal- work. I have a feeling that they work more like {zankem-} and {malkem-} with the expansion: lo zanbroda =3D> lo broda noi zabna Another pattern is -pre, which can be (may be not) a calque of Standard Average European suffix for job. (ladrypre =3D milkman?). Obviously, these example are just islands in the Sea of Cimjvo Instability (and inpredictability). Nevertheless, they have to be described since mnemonics of rafsi helps remember lujvo to a very small degree. The most important aspect of any brivla is how its place structure parallels other words the speaker is already familiar with. > Tanru are coined on the fly. Lujvo mean what they mean. Cf. CLL 4.5, CLL > 4.10. > > So maybe the perception that there is a problem with lujvo stems from a > slight confusion of their function in the language? > > One solution I thought of might be to ditch the school of thought that al= l >> lujvo that have the same ve lujvo are equivalent and completely >> interchangeable >> Thus {zangasnu} could be {zabna fa lo nu X1 gasnu X2}, >> While {zabnygau} could be {X1 gasnu lo nu X2 zabna X3 X4} >> > > Kontra=C5=AD-Fundamenta, thus bad. (I believe it to be one of the > unnaturalistic traits of the language that word-forms as different as > {xamgyzmadu}, {xaurmau}, and {xagzma} may never acquire different nuances > of meaning. But that's how it is.) > > >> {ta'ocu'i pe'i} that Lojban as-is relies way too much on the short rafsi >> anyway, which may inhibit learning it naturally. For example, {snura} "t= o >> be safe/secure", often gets combined with {gasnu} to make {nurgau} "to >> secure/protect". But that relies on the student remembering the rafsi of= a >> not-quite-so-promiscuous gismu. It would probably be much easier to see = the >> connection if the "standard form" remains {snurygau}. >> > > You need to *know* the lujvo's meaning anyway (see above); the rafsi are > just kind of memory hooks. And would it be wise to tweak the language > around learners' difficulties in remembering parts of the language? > > -- > 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. > --=20 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+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. --047d7b60441a58f9da0515e6b502 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2015-05-12 20:51 GMT+03:00 iesk <pa.fae@gmx.de>:
This is an interesting observa= tion. However, there already is an established way to deal with such appare= nt conflicts of (possibly) meanings: the correct meaning is defined by the = authoritative dictionary.
The problem is d= eeper. There are jvajvo, naljvajvo and cimjvo (the distinction between the = last too is vague). It's pretty straightforward to just declare all of = lujvo naljvajvo/cimjvo but then the whole idea of lujvo is ruined. What'= ;s the purpose in them if they aren't automatically expandable into bri= di? Mnemonics? But then there is no need in mapping rafsi to gismu. This is= in fact what it was back in 1960 with Loglan.
Then {pensku} coul= d mean {pensycusku}, not {penmycusku}.

However, us= age has established some patterns with using rafsi that bring them to the l= evel of slotting, i.e. a rafsi take a certain position with a certain funct= ion and meaning (it is theoretically possible that in different position th= e same rafsi would have slightly different functions and expansions but I c= an't recall anything similar).

For example, {x= 1 rodgau x2 [x3]} is probably always expanded into {x1 gasnu lo su'u x2= broda [x3]}. At one point there was even a project (a successful one imo) = that listed most used filjvo.

Another usage patter= n is with -sku lujvo. They are presumed to be naljvajvo:
smusku, = retsku, spusku, piksku unexpectedly break their place structure and stick t= o the one from {cusku}:

retsku =3D> cusku lo pr= eti
piksku =3D> cusku lo pinka

and th= at's about that. The other lujvo in this series don't follow this p= attern.
However, we have the pattern, we know what place structur= e to expect. This is much more than just mnemonic hints of rafsi.

I don't know exactly how zan- and mal- work. I have a f= eeling that they work more like {zankem-} and {malkem-} with the expansion:=
lo zanbroda =3D> lo broda noi zabna

= Another pattern is -pre, which can be (may be not) a calque of Standard Ave= rage European suffix for job.
(ladrypre =3D milkman?).
=
Obviously, these example are just islands in the Sea of Cimj= vo Instability (and inpredictability).

Nevertheles= s, they have to be described since mnemonics of rafsi helps remember lujvo = to a very small degree. The most important aspect of any brivla is how its = place structure parallels other words the speaker is already familiar with.=

<= /div>

Tanru are coined on the fly. Lujvo mean what = they mean. Cf. CLL 4.5, CLL 4.10.

So maybe t= he perception that there is a problem with lujvo stems from a slight confus= ion of their function in the language?

One solution I th= ought of might be to ditch the school of thought that all lujvo that have t= he same ve lujvo are equivalent and completely interchangeable
Thus {za= ngasnu} could be=C2=A0{zabna fa lo nu X1 gasnu X2},
While {zabnyg= au} could be=C2=A0{X1 gasnu lo nu X2 zabna X3 X4}
<= div>
Kontra=C5=AD-Fundamenta, thus bad. (I believe it = to be one of the unnaturalistic traits of the language that word-forms as d= ifferent as {xamgyzmadu}, {xaurmau}, and {xagzma} may never acquire differe= nt nuances of meaning. But that's how it is.)=C2=A0
=C2=A0
{ta'ocu'i pe'i} that Lojban as-is relies way too much= on the short rafsi anyway, which may inhibit learning it naturally. For ex= ample, {snura} "to be safe/secure", often gets combined with {gas= nu} to make {nurgau} "to secure/protect". But that relies on the = student remembering the rafsi of a not-quite-so-promiscuous gismu. It would= probably be much easier to see the connection if the "standard form&q= uot; remains {snurygau}.

You need to *know* the lujvo's meaning anyway (see above); the rafsi a= re just kind of memory hooks. And would it be wise to tweak the language ar= ound learners' difficulties in remembering parts of the language?
=

--
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+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.

--
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.
--047d7b60441a58f9da0515e6b502--