Releases: sammdot/rtfcre
v2.0.1
v2.0
v2.0.0-dev4
Fix lexical-core issue
v2.0.0-dev3
Plover relies on normalized steno strokes not having a number key if there are numbers in the stroke, and this was breaking compatibility between it and RTF files formatted for professional steno machines. This release normalizes steno notation.
v2.0.0-dev1
This release adds support for the \cxplvrortho
control word, which allows Plover to do orthographically-aware attachments. This is incompatible with previous behavior, in which all attachments were considered ortho-aware. Now \cxplvrortho
has to be specified in order to be treated as ortho-aware.
{\*\cxs EURB}{\*\cxplvrortho}\cxds ish -> "EURB": "{^ish}",
{\*\cxs *EURB}\cxds ish -> "*EURB": "{^}ish",
v1.3.0
v1.2.2
v1.2.1
While version 1.2 included support for non-ASCII translations, I inadvertently left the steno part unescaped. This would continue to cause issues for plover-korean and similar theories that use non-ASCII stroke labels. This release fixes that issue.
{\*\cxs ㅎㄹ}\u54624{\*\cxcomment Before -- escaped translation, unescaped steno}
{\*\cxs \u12622\u12601}\u54624{\*\cxcomment After -- escaped steno}
v1.2
This version introduces these new features:
- Non-ASCII steno strokes are now supported (#2).
\cxsystem
now uses this library's version string when converting from JSON, rather than leaving it empty.
It also includes the following bug fixes:
- Dictionaries with a non-text entry at the very end now parse correctly (#1).
- Empty dictionaries and dictionaries with only one entry now parse correctly (#1).
- The longest key calculation is no longer off by one; this prevented Plover from looking up translations in dictionaries where entries have only one stroke.