openstenoproject / plover_stroke Goto Github PK

All distributions of this software should include a copy of the license, or else they cannot be redistributed.

From Jeff on the Plover Discord:

The machine is translating everything as expected, but Plover is mistranslating (or not translating) a number of briefs. Most simply, the FPLT brief shows up as "-FPLT" in Word, rather than a period.

Aerick's response:

I think what's happening here is Plover expects -FPLT but the period stroke is defined as FPLT
so any entries that only use the right side keys will have to be reassigned

After reading the RTF/CRE spec, it seems to be much more lenient about including hyphens in outlines where the keys are already unambiguous:

A hyphen is used in cases where there may be confusion between an initial and final consonant. For instance, to differentiate between the strokes /RBGS [Plover: R-BGS] and /-RBGS [Plover: -RBGS].

After some regex magic Jeff returned with not quite everything resolved:

So my regex approach corrected about 6,000 entries, and things in Plover are way better now--but still not perfect, because this dictionary is also missing hyphens in many left+right strokes, like THR-R for "there are" ...nuts.

In this case we see the same issue, in which both Rs are there and so the hyphen isn't strictly necessary, but the outline isn't getting parsed correctly.

We should be able to handle these cases as well, in order for RTF (and others) dictionaries from professionals and CAT systems to work without needing major changes. Plover's steno notation as implemented in this library is unambiguous, yes, but the input dictionaries with not-quite-canonical outlines should be considered valid as well and normalized into our notation.

TL;DR: plover_stroke is too strict about hyphen usage, and some RTF/CRE dictionaries are failing to validate because of it.

#H-B doesn't work in Plover, only 4-B does.

However this plugin reports the normalized form of 4-B as #H-B.

(it could also be a Plover bug for not recognizing #H-B; however making the normalized RTFCRE form different between Plover and this library is not a good idea)