. ui coi ro do
I'm Daniel Evans, and I figured that I would share my thoughts on the lojban place structure. I've been thinking about it for a few weeks, so I finally sat down today for about four hours and typed up a really rough paper about it.In a nutshell, I say it should be trashed. Thrown away. Why? Read the paper, and then tell me what you think :)
I'll preface it (I did say this in the paper as all) with this: I don't think it's an awful system. Nor am I gonna be angry if everybody hates it. Keep in mind that I just blazed through a ten page paper, and didn't take a whole lot of time to revise my thoughts. I just wanted to get my thoughts down and organize them for myself. Doing so was best achieved by writing a paper about it, and that ended up being too much work to keep it to myself. I'm interested by what others think. It would be unbelievably cool if my ideas could be implemented, but I don't necessarily expect it.It is attached to this post. Enjoy!
Something that bothers me about your paper, which as it stands is quite good, is that you only deal with an extremely small portion of Lojban. You don't touch at all on lujvo, which are what place structures are really for. In the case of purely compositional lujvo, e.g. kansi'u, the place structure lets you infer without any ambiguity or metaphor what the resulting place structure of the lujvo will be, based solely on the knowledge of the component gismu. As for memorizing the place structures of component gismu, one must simply realize that Lojban already *has* a case system. Simply put, rather than having named cases, we have numbered cases, and in many cases, there is a lot of parallelism between gismu of the same semantic category.Consider {morji}, {djuno}, {smadi}, {sruma}, {jijnu}, {jimpe}, {senpi}, {birti}, {krici}, and {jinvi}.morji = x1 remembers fact x2 about x3djuno = x1 knows fact x2 about x3 by epistemology x4smadi = x1 guesses x2 about x3jijnu = x1 intuits x2 about x3jimpe = x1 understands fact x2 about x3senpi = x1 doubts that x2 is truebirti = x1 is sure that x2 is truekrici = x1 believes that x2 is true about x3jinvi = x1 opines that x2 is true about x3 on grounds x4In the "knowledge" family, which above isn't even complete, one immediately notices the parallelism. This family along with the "family" family (family-relation = x1 is the <type of relationship> of x2 by bond/tie x3; e.g. bersa) and the foods and animals family (food/animal = x1 is a <food/animal> of type/species/etc. x2) make up an extremely large portion of the gismu list.Now, I concede that even within a family, there are some exceptions, such as birti and senpi, which don't have an "about" place at all, or jinvi and djuno which are the only ones with an x4. Even in the food and animals family, there are some notable oddballs such as lanme ( = x1 is a sheep of species x2 of flock x3). However there being a difference in the number of places *usually* isn't that much of a big deal. If someone accidentally fills in an x3 of birti, any decent listener will understand what is meant, due to the overarching systematic nature of the family to which it belongs. On the other hand, when lujvo are made (according to the rules, that is) oddball places may unfortunately need to be included, which can lead to unexpected place structures in the resulting lujvo.e.g. jboxlajivdunsi'u = x1 are equal in that they opine that lojban is bad for x2 by standard x3 on grounds of belief x4.If one forgets that xlali has a standard place in the x3, then if they try to fill in the belief place of jinvi, things can get messy.Still, I don't know how your proposed case system would cooperate with lujvo (or would it simply drop lujvo from the language?) So I can't say that the status quo is any better or worse.Finally, semantic families don't always work. {cpedu}, {minde}, and {picki} are in the same family, I'd say, but have place structures divergent in rather irritating ways.cpedu = x1 requests x2 of x3 in manner x4minde = x1 orders x2 to x3picki = x1 begs x2 to x3However, if one takes into account the emphasis difference, (when ordering something to happen, the person whom is ordered is more important, and therefore moves closer to the front,) then it becomes easier to remember. Also, cpedu2 being the action requested is more useful for translating "He asked for a glass of water." Indeed, in that case, the person of whom that action (giving a glass of water) is far less important (it could be anyone, so in truth, we're just dropping the place entirely by context).That being said, I strongly push towards efforts to regularize the gismu list in order to make the numeric case system more self-consistent. One of Lojban's major issues is a lack of self-consistency, as pointed out by gleki in his thread about "four different vocabularies."
However, the existence of this multiple vocabularies is not a problem intrinsic to the nature of Lojban, and is thus a whole other can of worms when contrasted with the issues with place structure.In sum, I believe that trashing place structure is overall a bad idea.
Place structure is central to Lojban's ideology, in my opinion, and removing it from Lojban would be like taking the Lojban out of Lojban.
Named case systems are used in other conlangs, and if those are more pleasant to you, then perhaps those you should try those out, too.
mi zmadu do lo ni barda (I exceed you in property of being big) => mi poi zilkarbi do cu barda (I compared to you is big).
On Wed, Mar 27, 2013 at 11:17 AM, la gleki <gleki.is...@gmail.com> wrote:<snip>mi zmadu do lo ni barda (I exceed you in property of being big) => mi poi zilkarbi do cu barda (I compared to you is big).
ka, not ni. ni is quantity, ka is property.
On 27 March 2013 16:52, Jonathan Jones <eye...@gmail.com> wrote:On Wed, Mar 27, 2013 at 11:17 AM, la gleki <gleki.is...@gmail.com> wrote:<snip>mi zmadu do lo ni barda (I exceed you in property of being big) => mi poi zilkarbi do cu barda (I compared to you is big).
ka, not ni. ni is quantity, ka is property.Although this is completely unrelated to the thread -- then again so is your reply, too -- the abstraction suggestions in the gimste are not prescriptive.
(You can dig around the archives to see that Lojbab himself has said this.)Some of us have adopted a system of abstractions that is more self-consistent, and indeed, that system puts a quantity abstractor in zmadu3. What gleki said isn't wrong; it simply doesn't conform to your style of Lojban.
.i mi'e la tsani mu'o
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mi zmadu do lo ni barda (I exceed you in property of being big) => mi poi zilkarbi do cu barda (I compared to you is big).
ka, not ni. ni is quantity, ka is property.Although this is completely unrelated to the thread -- then again so is your reply, too -- the abstraction suggestions in the gimste are not prescriptive.
I know this. I'm a big proponent of same.
(You can dig around the archives to see that Lojbab himself has said this.)Some of us have adopted a system of abstractions that is more self-consistent, and indeed, that system puts a quantity abstractor in zmadu3. What gleki said isn't wrong; it simply doesn't conform to your style of Lojban.
Actually, no. It is wrong, because he is translating ni as property. "(I exceed you in property of being big)". I wasn't saying he needed to put a property there, I was saying that ni is /not/ a property., it's a quantity.
That {mi poi zilkarbi} thing gets into the "as" issue that we had previously; I'm pretty skeptical as to whether it's appropriate.
I just find it silly that rather than use place structure, a simple 3-ary structure, we're introducing relative clauses, and lujvo, and BAI... "Let's make things more complicated to make them simpler." It seems to counterintuitive.
I just wanted to get my thoughts down and organize them for myself. Doing so was best achieved by writing a paper about it, and that ended up being too much work to keep it to myself. I'm interested by what others think. It would be unbelievably cool if my ideas could be implemented, but I don't necessarily expect it.It is attached to this post. Enjoy!
. ui coi ro doI'm Daniel Evans, and I figured that I would share my thoughts on the lojban place structure. I've been thinking about it for a few weeks, so I finally sat down today for about four hours and typed up a really rough paper about it.In a nutshell, I say it should be trashed. Thrown away. Why? Read the paper, and then tell me what you think :)
I'll preface it (I did say this in the paper as all) with this: I don't think it's an awful system. Nor am I gonna be angry if everybody hates it. Keep in mind that I just blazed through a ten page paper, and didn't take a whole lot of time to revise my thoughts. I just wanted to get my thoughts down and organize them for myself. Doing so was best achieved by writing a paper about it, and that ended up being too much work to keep it to myself. I'm interested by what others think. It would be unbelievably cool if my ideas could be implemented, but I don't necessarily expect it.
It is attached to this post. Enjoy!
--
And places can? Surely, if so, then prepositions or affix cases can.
On Fri, Mar 29, 2013 at 11:59:54AM -0700, John E Clifford wrote:
> From: MorphemeAddict <lyt...@gmail.com>
>
> > Yes, places can, because each place of each selbri can be defined uniquely.
>
> And so can each preposition/case.
>
Sure, but it probably doesn't make sense to define a preposition for klama1,
one for klama2, one for citka2, one for gerku2 and all the other places out there.
On Saturday, March 30, 2013 3:20:30 AM UTC+4, v4hn wrote:On Fri, Mar 29, 2013 at 11:59:54AM -0700, John E Clifford wrote:
> From: MorphemeAddict <lyt...@gmail.com>
>
> > Yes, places can, because each place of each selbri can be defined uniquely.
>
> And so can each preposition/case.
>
Sure, but it probably doesn't make sense to define a preposition for klama1,
one for klama2
Also, reading your replies and arguments for the retention of the current system makes me see that it isn't so bad. So, I guess, thanks!
--