Daniel Swanson

So far I was using the same capitalization processing as the existing tools, which have `AA`, `aa`, and `Aa` as the only possibilities (so, check first char and last if...

Probably related to #63 Naturally, it works fine on Linux Mint (lttoolbox and apertium both on most recent master commit) because no tagger bug is allowed to be simple.

Looks like you're right about it being in 0942975. The function that `apertium-transfer` used for handling case before that commit, if told to set the case to `aa`, would only...

recursive blank handling has been updated and should be approximately equivalent to t*x blank handling (it frequently deals with much longer sequences than t1x, so the blanks wind up offset...

Somehow or other I'm still getting a different number of line breaks in t*x for br-fr (and I can be sure it's t*x because rtx in an otherwise identical pipeline...

-separable has essentially the same formalism as monodix and includes an explicit way to write ``, so it should work just fine. -recursive has roughly the same issues as t*x,...

What about postprocessing with a separate transducer? ```xml blah ``` ```bash daniel@computer-name-here:~$ lsx-comp lr prefix.lsx prefix.bin main@standard 8 10 daniel@computer-name-here:~$ echo "^tinamit$" | lsx-proc prefix.bin ^tinamit$ daniel@computer-name-here:~$ lsx-comp rl prefix.lsx...

see https://github.com/apertium/apertium-zul/commit/2a011974f0aa39087ed9d344882fa4fe3a738893 for my rearranging idea in practice.

As I mentioned in https://github.com/apertium/apertium-lex-tools/issues/88, beginning-of-text is pretty easy but beginning-of-sentence probably has to be language-specific. Here we have the added consideration of what happens if you try to manipulate...

A possibly cleaner solution that I just came up with: Have an element like `` that can be used in conditionals and evaluates to `true` if there are no words...