3 ms·
My experience suggests that there are a handful of people who can read, write and speak the language fairly well, using it, when they choose, as their primary m
by RiderOfGiraffes 17y ago
My experience suggests that there are a handful of people who can read, write and speak the language fairly well, using it, when they choose, as their primary means of communication.
Most of the discussion falls into two types.
The first type is when a newbie tries to transliterate into lojban, and often says something they don't mean. This is common with anyone learning another language, it's just that in lojban one can be much more precise about what was wrong, because there's a formal grammar. Common confusions are mixing "verbs" with "nouns", neither of which have an exact matching concept in lojban, hence for some it's tough to get a grip on what's going on.
The second is debating the semantics. What does this word, explicitly created for lojban, actually mean? What's the difference between a pot and a jar? How, in English, do we decide which word to use? What is the defining characteristic of each?
These are often held up as criticisms of the language, but I think unfairly so. They provoke debates in epistomolgy, semantics and pragmatics, and touch on many of the questions that will need to be answered by the machine translation, semantic web and artifical intelligence challenges.
And what's the point in learning a language that's just a re-coding of your native language?
The other undeniable short-coming is that there is no underlying "culture." Much of the interest in learning, say, Russian, comes from the cultural insights. There is none of that in lojban.
Lojban isn't ready for generic, general purpose communication. It's still growing. If all you want is a tool, don't go there.
If you want mind-expanding concepts and debate, have a look.
- frig 17y agoCan you give a slightly non-trivial lojban sentence with translation? I'd prefer it be one you create so I can more easily ask you questions about it (as opposed to a web example).
- RiderOfGiraffes 17y agoHow complex is "slightly non-trivial" ? Hmm. Here's a recent example: le se viska be mi cu xamgu Translation: The thing(s) I (or we) see is/are/were/will be good. Probably from context, more colloquially: What I see is good. Be advised: not only am I not an expert, I class as a newbie with dangerous knowledge. I have read, understood and worked with the formal machine grammar, and I have written some tools to work with parsed utterances. I have not, and probably never will, have any command of the vocabulary. I'm happy to try to answer questions, and will defer those that are beyond me to one of the lists on which I lurk.
- frig 17y agoThanks for the sentence, that's certainly nontrivial enough (I was just trying to dodge 2-3-word-sentences like "jesus wept" or "i like milk", which rarely show anything interesting at the grammatical level). Not-mocking: there's an apparent lack of number ("thing(s)", "I (or we)"). Is it closer to true that: - the grammatical root of this apparent lack of # is shared between "thing(s)" and "i (or we)" ...or that: - "thing(s)" is a gloss of some word that's ~ "specific things not specifically specified" - "I (or we)" is a gloss of some word that's ~ "who I speak for" (or some other deictic term that's ~ first-person but otherwise underspecified) ...or to some other possibility? Additionally: Given that it's a designed language I'm curious about what underlying intent (whatever it is that explains why the answer is what it is, instead of being something else). (Disclaimer: wiki's lojban articles have resolved a lot of my other questions, but before I asked you I'd only looked at lojban's wiki's articles, which are mostly unhelpful.)
- dbrock 17y agoShort answer: the latter is more true. The reason why {mi} is unmarked for number is simply that it’s defined that way. In Lojban, everything is unmarked for number by default. It’s actually quite rare to see things explicitly marked for number, as it’s usually either irrelevant or obvious from context. The pronoun {mi} is technically unmarked for number, but is restricted to refer to people that the speaker represents, just as you guessed. For example, it would usually be weird or incorrect to use {mi} to mean “we” in the sense of “me and you”, since representing the very people you are talking to is a rare situation — although theoretically you could come up with examples where it would make sense. So in practice {mi} is usually singular. On the other hand, {do} (which means “you”) is as often plural as it is singular. There are other pronouns that mean “me and you”, “me and others”, “you and others”, and “me, you, and others” — respectively, {mi’o}, {mi’a}, {do’o} and {ma’a} — which is another reason why the need for plural {mi} seldom arises.
- frig 17y agoThanks. I figured grammatical # as such would be discarded as unnecessary but the notion of plurality raises semantic issues that natural language sidesteps by ambiguity. Disclaimer/Personal Background (trying to be brief): I've often been told I've got an unusual cognitive style (for lack of better term) and I've often felt very much as if there's an impedance mismatch between how my thoughts are structured and how language operates; in essence, at the word-or-sentence level everything I hear or read is very polyvalent and vague, and only take on a concrete meaning to me if I get multiple paraphrases of it...it's putting all the variants into superposition and seeing which parts reinforce or cancel shows me the contour of the actual meaning (which itself is not necessarily ever actually "represented in words" so much as "gets the outline of its semantic boundaries painted"). In the abstract this leaves me with an interest in the idea of something like lojban but very mixed initial reactions: it's possible an artificial language with more-precise meanings would eliminate my need for doing verbal interferometry across multiple paraphrases but on the other hand I have a lifetime's experience feeling very uncomfortable without tons of redundancy and repetition-with-alteration, which seems to be what lojban is trying to eliminate in its use. Too much info, I'll stop there. I do have two more questions if you have time. #1 is historical: what's the process by which the core sets of things like spatial relationships or tenses or shapes or so on came to be enumerated? EG: if I were doing a language in this form I'd go through all the languages I could get my hands on and try to get good lists of all their fundamental categories (eg: spatial prepositions and "classifiers", like you have in swahili and chinese (+ languages with heavy chinese contact) (cf: http://www.jstor.org/pss/413103 http://www.jstor.org/pss/413103 ) and then try to factor them into semantic atoms. I'd consider this approach bottom-up (see what's out there, and then try and simplify and unify them) and contrast it with a more top-down approach (trying to derive a finite set of spatial relations ab initio via pure reasoning); it'd also be a good set of "unit tests" for your final set of core concepts, making sure that none of these words' senses are not really expressible in terms of your base concepts. How did the lojbanists derive their tenses / spatiotemporal prepositions / etc.? Is there a good "history of the design of lojban" that speaks to this? Question #2: at a practical level how would you decompose "There are dogs in the kitchen" into lojban? If I had to break it into predicates it'd probably be the conjunction: - CONTAINS("containment-type T","kitchen","entity collection E") - T ~ whatever containment type you have that is ~ "contains within its spatial bounds -- but not structurally -- for an indeterminate time period" - COUNT(E) > 0 - ENTITY-COLLECTION-TYPE(E,X), where X ~ "collection treated as collection due to spatiotemporal circumstance and descriptive convenience" (EG: E is an entity collection b/c there are label(s) they all share, namely being instance-of dog and contained-in-the-kitchen in the same way; there's no assertion of any other source of entity-identity beyond the circumstances this utterance is describing; contrast to say "baseball team" or "deck of cards", etc., which are entity-collections with a more-persistent and "intentional" identity) - forall e in E IS-INSTANCE-OF("instance-of-type IoT",e,"dog") - "instance-of-type" ~ whatever instance-of you have that is ~ "is a concrete instantiation of an abstract type not otherwise specified (eg: an actual 'dog', not 'Pomeranian') - + some temporal modifier to explain like "the described circumstance started before I made this utterance and I do not think it has ceased, yet" ...but I'd assume some of the intended distinctions are usually left implicit or inferred; what's a good lojban decomposition?
- DanielStraight 17y agoFirst of all, let me get something out of the way. There are no languages that are just re-coding of other languages. I understand the idea behind Lojban but you've already conceded my point. Lojban is not a suitable language for communication.
- RiderOfGiraffes 17y ago> There are no languages that are just re-coding > of other languages. That's true, but it's "less true" of Italian/Spanish or Russian/Bulgarian than it is of, say, Russian/Swedish. I suspect that we are in complete agreement, and might argue only about precision of expression in our opinions. And I didn't say lojban is unsuitable for communication. There are a few people who use it exclusively when communicating with each other. It is not yet ready for generic, general-purpose communication, just as the newest computer programming language isn't ready for mainstream use by those not interesting in the language so much as getting things done. But again, I suspect we are/would be in "violent agreement" about most of these points. I contend that lojban is, regardless, mind-expandingly interesting. For some.
- arran4 17y agohttp://www.youtube.com/watch?v=nU8DcBF-qo4 http://www.youtube.com/watch?v=nU8DcBF-qo4 As long as the languages are relatively similar and you don't push it too hard.
- dbrock 17y agoThere are many people who can converse fairly well in real-time written Lojban (although vocabulary is limited, and some parts of the language are generally not used). Due to audio-visual isomorphism, being able to converse in written Lojban almost implies being able (theoretically) to converse in spoken Lojban. However, people are generally much less used to speaking and hearing Lojban, so spoken conversations are usually somewhat difficult (definitely far from fluent).
- DanielStraight 17y agoRight. It's been around since 1955 (in spirit at least, in the form of Loglan) and the best anyone can muster is to converse "fairly well" in "real-time" but not in spoken conversation. In other words, it's a language no one can speak. Klingon speakers are even more fluent than Lojban speakers. I'm not trying to say Lojban is stupid. It's not. It's cool. It fills an interesting niche in the language world. However, I'm not convinced it's speakable. Remember the quote by Kernighan: "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." I would argue that speaking a language is at least twice as hard as inventing it or writing it in a non-real-time fashion, so if you create the most complicated language you can still manage to write (however laboriously), you are by definition not smart enough to speak it. Lojban is that language.
- RiderOfGiraffes 17y agoLojban is not designed to be complicated. The important parts of the BNF grammar are about a page, and easily understood in an hour or so of properly directed study. The hard parts are the vocabulary and the mind-set. It is specifically designed to be different, but even then, there are sufficient similarities that it doesn't have to feel completely alien. Some people present it as such because they think it will attract people, but I know that sometimes familiarity is a better draw. It can be presented either way. And people tend to say uncomplicated things in Klingon, whereas most lojban speakers are exploring saying very complicated things - you're not comparing like with like. Further, although gatherings of Klingon speakers are fairly common - piggy-backing on Star Trek conventions - gatherings of lojban speakers are rare. Even so, there are several people who speak it fairly fluently, and the number is growing (in some sense). It is often criticised (I'm not saying you are doing so) for being something other than what people think it "ought" to be. This is a marketing issue. I think it's interesting, and, like learning Lisp, it has expanded my mind in interesting ways.