Daniel Swanson

Actually, we could make it so that a certain `` could be marked as defining a delimiter, and whenever that element is seen, it resets ``. I'll have to think...

`lt-proc` could record the original capitalization and put that in word-bound blanks which could then be used to determine that.

I had forgotten to handle escaped characters in lemmas. d71762b fixes the immediate issue on my end, but I'm leaving this issue open for the moment to remind myself that...

``` echo "P'edon" | lt-proc -w '/home/daniel/apertium-data/apertium-br-fr/br-fr.automorf.bin' | cg-proc '/home/daniel/apertium-data/apertium-br-fr/br-fr.rlx.bin' ^P'edon/pa+bezañ$ echo "P'edon" | lt-proc -w '/home/daniel/apertium-data/apertium-br-fr/br-fr.automorf.bin' | cg-proc '/home/daniel/apertium-data/apertium-br-fr/br-fr.rlx.bin' | apertium-tagger -g -d br-fr.prob Warning: There is not coarse...

If it's the first part that is unrecognized or if it's not an MLU, there is no issue.

#113 fixes br-fr for me.

Since you're going in the fra->oci direction, wouldn't trimming be about whether `jouer` was present on the left side of the bidix?

The point has been brought up several times that analyzing punctuation significantly increases the number of patterns. It seems to me that adding shortcuts for common patterns would mitigate this...

One thing in particular that comes to mind on the subject of punctuation is in -recursive to have something like ``` QUOTES: (@lpar )@rpar, '@apos '@apos, "@quot "@quot; QUOTED: n,...

Though we do already have `lt-print -H` to switch from `ε` to `@0@`.