WikiDiscuss

Elidable terminators are sometimes required for disambiguation, but they are always allowed, even when not required.

Pauses between words are sometimes required for disambiguation, but they are always allowed, even when not required.

Marking stress with caps is sometimes required for disambiguation, but it is always allowed, even when not required.

Using long rafsi in lujvo instead of the short ones is sometimes required due to morphology constraints, but it is always allowed, even when not required.

There seems to be a pattern there. What about hyphens?

y- and r-hyphens after CVC and CVV rafsi are sometimes required due to morphology constrains, but they are always allowed, even when not required... NOT! When not required they are not allowed!

This seems to go against the Lojban way of doing things, and it is also a burden for the user. You get used to a lujvo like {tosymabru} and when you try to form a new lujvo by adding an additional rafsi:
say {naltosymabru} it turns out it is not valid: it has to be {naltosmabru}. You get used to {ro'inre'o} and when you form {braro'inre'o} it turns out that's not a lujvo, either.

In the PEG grammar, I allowed -y- after any CVC, not only when it is required, mainly because that was easier than disallowing it when it wasn't necessary. It doesn't seem to be worth complicating the grammar for such an unnecessary and bothersome restriction.

I am now allowing the r-hyphen after any non-final CVV as well, because that is more user-friendly. In this case there is a small cost: we take some forms that would otherwise be fu'ivla and put them in lujvo-space, but lujvo have always had priority over fu'ivla so that's not a big deal (and it is not a noticeable chunk of fu'ivla-space anyway).

These are also fairly common mistakes people make when creating lujvo, so this move is actually supported by usage.

mu'o mi'e xorxes