jrbowden
jrbowden
The opcodes `empmatchbefore` and `empmatchafter` are used in the UEB tables but are not documented. Please can they be added to documentation?
The match opcode can match on a variety of character attributes, e.g. `%a` for alphabetic, `%#` for digits etc. Not all character attributes are currently available to test with `%`...
Further improvements to UEB: - Following discussion at ICEB, back translating braille dot 3 should be ordinary apostrophe U+0027 rather than U+2019. This is consistent with other tables and also...
We currently have several "simple" and very useful opcodes such as word, sufword, midword, etc. It would be great to know exactly what they are looking for before and after...
most opcodes are case insensitive, suggest a prefix which makes what follows case sensitive, for those occasional rules which require case sensitivity. An example might be that contractions not used...
Suggest that the match opcode should be case insensitive throughout. Currently, different operands of the match opcode are case sensitive or insensitive. ```match pre-pattern characters post-pattern dots``` ```pre-pattern``` and ```post-pattern```...
### Issue type UX/Interaction bug (incorrect behaviour) ### Description with steps to reproduce Steps: Setup: 1. Assume a score with some notes on it. e.g. bars 1 and 2 just...
In UEB, if a string of letters is also a "shortform", then a "grade 1 indicator" is also required to prevent misreading. Example: ab is the shortform for "about", so...
In UEB, any word written fully capitalized is terminated by a non-alphabetic sign, see Rules of Unified English Braille 8.4.2. Thus: AA's should be written in UEB as ⠠⠠⠁⠁⠄⠎ AA'S...
I have found several probably related problems for backtranslating. Although I found the problems with UEB, I believe the problems are in the engine, not the table. 1. Issue #434...