> Despite the name, what constitutes a “loglang” is rather undefined.
The term “loglang” has a fairly well accepted definition these days: a language with monoparsing semantics. That is to say, every utterance in the language uniquely maps to exactly one semantic statement within some logical formalism (the exact choice of logic may differ from language to language).
Your descriptive features of loglangs either fall under this property (e.g. self-segregating, which is a necessary precondition for strict monoparsing), or are arguably not properties of loglans per se (e.g. elimination of non-coding elements, audiovisual isomorphism; these are just generally true of engineered languages as a matter of course). Aside: Loglan/Lojban is anything but ergonomic :)
I think you are missing the most important question: why are you making a new loglang? Why not just use or extend Toaq or Lojban?
Also, why loglang at all? What is this post doing on a rationalist website? I can think of many answers to that, but your justification is missing.
You’re right! I totally forgot to talk about monoparsing. I really shouldn’t have missed that.
I don’t like the design choices that Lojban and Toaq made. The latter much less so, but there are still aspects I dislike. I wanted to see if I could, if not do better, at least go in a different direction. It’s why I use Livagian or Eberbanian style grammar with no “main verb”, and use agglutinative morphology rather than analytic.
You can post anything on LessWrong as a personal blogpost. From the LessWrong FAQ:
What can I post on LessWrong?
Posts on practically any topic are welcomed on LessWrong. I (and others on the team) feel it is important that members are able to “bring their entire selves” to LessWrong and are able to share all their thoughts, ideas, and experiences without fearing whether they are “on topic” for LessWrong. Rationality is not restricted to only specific domains of one’s life and neither should LessWrong be.
However, to maintain its overall focus while still allowing posts on any topic, LessWrong classifies posts as either Personal blogposts or as Frontpage posts. See more in the post on Personal Blogpost vs Frontpage Posts.
> Despite the name, what constitutes a “loglang” is rather undefined.
The term “loglang” has a fairly well accepted definition these days: a language with monoparsing semantics. That is to say, every utterance in the language uniquely maps to exactly one semantic statement within some logical formalism (the exact choice of logic may differ from language to language).
Your descriptive features of loglangs either fall under this property (e.g. self-segregating, which is a necessary precondition for strict monoparsing), or are arguably not properties of loglans per se (e.g. elimination of non-coding elements, audiovisual isomorphism; these are just generally true of engineered languages as a matter of course). Aside: Loglan/Lojban is anything but ergonomic :)
I think you are missing the most important question: why are you making a new loglang? Why not just use or extend Toaq or Lojban?
Also, why loglang at all? What is this post doing on a rationalist website? I can think of many answers to that, but your justification is missing.
You’re right! I totally forgot to talk about monoparsing. I really shouldn’t have missed that.
I don’t like the design choices that Lojban and Toaq made. The latter much less so, but there are still aspects I dislike. I wanted to see if I could, if not do better, at least go in a different direction. It’s why I use Livagian or Eberbanian style grammar with no “main verb”, and use agglutinative morphology rather than analytic.
You can post anything on LessWrong as a personal blogpost. From the LessWrong FAQ:
Just FYI you posted to the front page, not your personal blog.