Sender: lojban@googlegroups.com
Received-SPF: pass (google.com: domain of ilmen.pokebip@gmail.com designates 2a00:1450:400c:c0c::22e as permitted sender) client-ip=2a00:1450:400c:c0c::22e;
Subject: Re: [lojban] Spaces in jbovlaste
To: lojban@googlegroups.com
References: <b8da37b0-bc48-417f-ad27-6ba85424a312@googlegroups.com>
From: Ilmen <ilmen.pokebip@gmail.com>
Message-ID: <3c86d96b-e0ea-af6b-2ee8-51d4e0741fe5@gmail.com>
Date: Thu, 27 Jul 2017 13:04:33 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <b8da37b0-bc48-417f-ad27-6ba85424a312@googlegroups.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
X-Spam_score: -4.1
X-Spam_score_int: -40
X-Spam_bar: ----

If spell checkers are only concerned with identifying what is a correct=20
word and what isn't, then you should disregard Jbovlaste entries=20
containing whitespace (they are multi-words lexemes), or even better,=20
check all the words that compose them to see if any of them is missing=20
from your spell-check whitelist (I strongly suspect there exists bu and=20
zei compounds containing words that appears nowhere else in the=20
dictionary=E2=80=A6).

"re zei zgabube" is indeed a sequence of three words. It is present in=20
the dictionary because it is an independent lexeme, you cannot=20
accurately derive its meaning from its parts. This occurs all the times=20
in natlangs, think for example to the English "take off".

As for cmavo sequences, people are allowed to chain them up without=20
whitespaces in between (this causes no ambiguity), although nowadays it=20
seems more common to always separate them with whitespaces. For a=20
spell-checker, two strategy are possible: the lazy one would be to=20
enforce the style of putting whitespaces between every cmavo, thus=20
marking e.g. "lonu" as incorrect; the second strategy, more involved,=20
would be to check any unknown letter string to see if it matchs a=20
sequence of cmavo, and allow it if it does (e.g. if the program hits=20
"calonu" and is able to find it can be a sequence of cmavo ca+lo+nu,=20
only then it would allow it). But I don't know if the software you're=20
using is able to do that without an explicit and systematic list of all=20
allowable cmavo strings=E2=80=A6

If the software were to need an explicit and exhaustive list of allowed=20
words, I guess it wouldn't be very handy to use for very synthetic=20
languages (e.g. Turkish, Quechua, Greenlandic=E2=80=A6), which might have a=
n=20
infinite number of valid words.

=E2=80=94Ilmen.


On 27/07/2017 10:49, sukender1@gmail.com wrote:
> coi ro do
>
> I found entries with spaces in jbovlaste. This is an issue for spell=20
> checking dictionaries (actually in "aspell"). I know that spaces are=20
> not relevant when parsing Lojban, but they're still important for=20
> human reading. This is why I would not like a rule like "import every=20
> entry and remove spaces everywhere"...
>
> So, I understand that it may be normal for compound cmavo, like "tai=20
> da'i", but can't these be written without space ("taida'i") without=20
> breaking the reading flow?
> However, some entries seem very strange to me, such as "re zei=20
> zgabube". Aren't these 3 separated words??
>
> Thank you for your explanations.
>
> co'o
>

--=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 https://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.