There wasnt any reason= able consistency and there isnt. Take {mz} but {nz}, {ms} and {ns}.

2014-12-11 19:30 GMT+03:00 Alex Burka <aburka@seas.upenn.e= du>:

The preprocessor thing doesn't make a ton of sense to m= e. Does anyone else support this "dialectal variation"? We don't preprocess= {ie} to {i'e}, so I don't see the point in changing ?{jie} to {ji'e}. They= 're quite different sounds, and moreover different syllable counts, so you'= ll be complecting the stress and word segmentation rules as well as breakin= g audiovisual isomorphism.

As for the larger question, I don= 't have a very strong opinion. I lean towards consistency (that would be ba= nning it or allowing it everywhere). If we do allow it, maybe the sibilants= should still be an exception for ease of pronunciation (I don't have troub= le with ?{guaspi}, but ?{jiespi} and ?{ciaspi} are difficult).
So if we're approval-voting: 1.1.2 + 2. But I'm open to being = convinced otherwise.

mu'o mi'e la durkavore
<= div>
=20 =20
On Thursday, December 11, 2014 a= t 8:41 AM, Gleki Arxokuna wrote:

2014= -12-11 16:16 GMT+03:00 John Cowan <cowan@mercury.ccil.org>:
Gleki Arxokuna scripsit:

> I vote for this. + I prefer it to be just a synonym (dialect variation= of
> the same sequence but with a {'} inside. co'o zo guaspi

I can live with this, but I'd prefer to ban it altogether.
=

It depends on in what way should it be ban= ned.
I vote for banning it from the formal grammar however,= I vote for the preprocessor to be able to autocorrect {jie} back to {ji'e}= . Speech recognition must be able to recognize both variants.

--
John Cowan http://www.ccil.org/~cowan &nbs= p; cowan@ccil.or= g
Clear? Huh! Why a four-year-old child could understand t= his report.
Run out and find me a four-year-old child. I can't make head or tail<= br> out of it. --Rufus T. Firefly on government repo= rts

--
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 post to this group, send email to bpfk-list@googlegroups.com.
Visit this group at http://groups.google.com/group/bpfk-list.
For more options, visit https://groups.google.com/d/optout.

--
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 post to this group, send email to bpfk-list@googlegroups.com.
Visit this group at http://groups.google.com/group/bpfk-list.
For more options, visit https://groups.google.com/d/optout.

=20 =20 =20 =20

=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 post to this group, send email to bpfk-list@googlegroups.com.
Visit this group at http://groups.google.com/group/bpfk-list.
For more options, visit https://groups.google.com/d/optout.