openstenoproject/plover

Dictionary on One Computer Via Dropbox Works Fine, But Shows Errors on The Other

Closed this issue · 3 comments

gdwaynewarner commented

Describe the bug
A shared dictionary in a dedicated folder on DropBox works fine on my laptop (MacBook Pro), but appears broken on my iMac.

To Reproduce
I have been using this exact setup for quite a while now with no issues -- until I had to replace my iMac a few months back.

The only thing I'm doing is writing something on the iMac and getting untrans when I should be getting actual words or phrases.

Steps to reproduce the behavior:

Connect my writer to the iMac

Write something (usually works).

Expected behavior

What I write should be represented on the iMac correctly.

Screenshots
Here's a screenshot of the errors I'm getting:
plover_dictionary_issue
If applicable, add screenshots to help explain your problem.

As my laptop is not doing that, here's one of the words that are messed up in the above screenshot:
plover_non_messed_up_word

Operating system
Mac OS High Sierra (10.13.6)

  • Plover Version [e.g. 3.x, 4.x, weekly]
    iMac's Plover Info:
    iMac_Plover_Version

MacBook Pro's Plover Info:
MacBook_Pro_Plover_Version

Hardware

If applicable, let us know what machine you're experiencing the issue with and how it's connected to Plover, as well as a screenshot of the machine configuration inside Plover.
N/A

benoit-pierre commented

And the solution is all there in the warnings and how the dictionary editor highlights those invalid steno entries:

  • HOE*LGTS → HO*ELGTS
  • K*OEUBG → KO*EUBG
  • KR*OEUBG → KRO*EUBG
  • KR*UPB RR → KR*UPB/RR
  • Mc → ???
  • R*OEUBG → RO*EUBG
  • SKPRE*S → SKPR*ES
  • SKWA_RPBD → SKWA-RPBD
  • TK*OEPB → TKO*EPB
  • TKPWA*UB TKPWA*OBG -> TKPWA*UB/TKPWAO*BG
  • TPH*EUD → TPHO*EUD
gdwaynewarner commented

Okay, so how come (most of) those same entries in the dictionary on my MacBook Pro work and look the same?
bug_report_from_working_dictionary
?

aerickt commented

In the newer version, Plover will check your dictionaries for invalid steno strokes and output an error if any exist (like the ones you've seen). Invalid steno strokes won't output their translation in either version of Plover, the only difference between versions is whether Plover will notify you about these errors. The correct thing to do would be to fix these invalid entries like Benoit described.

  • 👍2