Sender: bpfk-list@googlegroups.com
Received-SPF: fail (google.com: domain of mark@kli.org does not designate 96.56.207.26 as permitted sender) client-ip=96.56.207.26;
Subject: Re: [bpfk] Officially updating "Complete Lojban Language" grammar
 book. An official LLG proposal passed. Your help needed.
To: bpfk-list@googlegroups.com
References: <391988c7-80ac-45c1-9549-8c22ebf6a113@googlegroups.com>
 <20190807173307.GL11404@nvg.org>
From: "Mark E. Shoulson" <mark@kli.org>
Message-ID: <bdf122ba-16dd-0dea-47f5-aadd2224442d@kli.org>
Date: Wed, 14 Aug 2019 19:24:32 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <20190807173307.GL11404@nvg.org>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Reply-To: bpfk-list@googlegroups.com
Precedence: list
Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com
X-Spam_score: -3.0
X-Spam_score_int: -29
X-Spam_bar: ---

Not quite directly relevant to this, but also regarding hyphens:=C2=A0 I=20
recall long LONG ago, when I was making a lujvo of vofli+litru, (to=20
express just "flying along"; it looks like vofli alone would have worked=20
okay, but it may have had a different place structure then, or maybe I=20
just didn't realize it.=C2=A0 Not the point), with the rafsi -voi- plus=20
-li'u-, obviously I need a consonant hyphen to get the required=20
consonant cluster, but the rules stipulated that it *had* to be -r-,=20
thus, voirli'u. which at least to my articulatory organs felt quite=20
awkward.=C2=A0 It winds up being closer to 4 syllables than 3; the -r-=20
becomes vocalic, or nearly so.=C2=A0 Not so if I had been allowed to say=20
*voinli'u.=C2=A0 Is there a reason to forbid giving the speaker a choice=20
regarding the consonant-hyphen, given that there are only two(?) allowed=20
anyway?

~mark

On 8/7/19 1:33 PM, Arnt Richard Johansen wrote:
> coi lojbo
>
> ni'o
> mi mo'u tcidu le nu galfi be cy ly ly kei stidi liste .i da'a le se stidi=
 cu se zanru mi .i dei noi notci cu pinka po'o pa le se stidi .i ca ku mi n=
a'e tolcru ri
>
> ni'o
> stidi lo nu vimcu zoi gy
>     It is illegal to add a hyphen at a place that is not required by this
>     algorithm.
> gy gi'e jmina zoi gy
>     It is possible to optionally add an y-hyphen between the consonants o=
f any
>     permissible consonant pair e.g. for stylistic purposes or for the eas=
e of
>     pronunciation.
> gy
> .i lo mukti be le se go'i cu na filsmu .i .e'u ko ga'i nai sitna lo purci=
 ke casnu se cusku ku le se stidi
>
> ni'o
> ji'a le se stidi cu simlu lo ka jai tolsarcu je xlali .i sa'e ju'o cu'i l=
e cnino javni cu fanta tu'a lo fu'ivla
>
> --
> Hello Lojbanis,
>
> I have read the list of change proposals to CLL. All the proposals except=
 one are fine by me. This message is a comment on one of the proposals. I a=
m not vetoing it at this time.
>
> It is suggested to replace:
>     It is illegal to add a hyphen at a place that is not required by this
>     algorithm.
> with:
>     It is possible to optionally add an y-hyphen between the consonants o=
f any
>     permissible consonant pair e.g. for stylistic purposes or for the eas=
e of
>     pronunciation.
>
> The motivation for this is not clear. If you could possibly cite past dis=
cussions in support of this proposal, that would be nice.
>
> Furthermore, the proposal appears to be unnecessary and detrimental. To b=
e precise, it seems to me that the new rules would prevent some fu'ivla.
>

--=20
You received this message because you are subscribed to the Google Groups "=
BPFK" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bpfk-list+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/=
bpfk-list/bdf122ba-16dd-0dea-47f5-aadd2224442d%40kli.org.