Bert Frees
Bert Frees
@rimas-kudelis OK good! I'm not even sure I should tag it as a bug because often the intended behavior of a feature in Liblouis is not totally clear, and sometimes...
After looking into it a bit more I think we can't classify it as a bug. It's just the result of how the `numericnocontchars` opcode was implemented. When a `numericnocontchars`...
Added the `documentation` label because this is really not clear in the documentation. I think we should remove the old way of handling numbers to make things easier to document.
The "⠠" is added here because "z" is in your `numericnocontchars` rule. Why does "z" need to be a numericnocontchar?
> But it is not directly after a digit - they're separated by dot. Yeah this is just how it works if you define the dot as a `numericmodechars`. Typically...
Thanks. For clarity, could you add tests for the following cases? - "2:bb" - "2.1" - "2.a"
@BueVest Could you perhaps turn this into a test?
Actually what Liblouis does makes sense I think. Maybe not in your case, but I think your case is a bit unusual. If you don't define any capitalization opcodes, Liblouis...
So basically there are three cases that need to be supported: - "empty" capsign (SBS use case) - capitalization as defined by uplow rules (current default when capsign absent) -...