Bug Report: Dictionaries Getting Corrupted

93 views
Skip to first unread message

Glen Warner

unread,
May 27, 2017, 4:48:50 AM5/27/17
to Plover
While using the new version of Plover, I decided to reboot my Mac, and when I started Plover again, a few of the dictionary entries I use while writing Cheap and Sleazy were changed.

For instance, one of my entries gives me this:

<p class="body">

My HTML editor completes that line, so it should look like this:

<p class="body"></p>

 ... which is why my dictionary entry for that looks like so:

{^}<p class="body">{^} {-|}

As you might guess, whatever I stroke in after that should be right between those two "><" symbols.

Unfortunately, after the reboot, that entry, and several others, looked like this:

{^ <p class="body"> ^} {-|}

... which means that whatever I type in there looks like this:

  <p class="body"> </p>

I don't know how well this will be represented when I post, but in that paragraph above, there should be a space before you see that <p class="body"> bit.

 You can see what the damaged dictionary looks like here:


Yes, it's a little thing, but very annoying when it's not expected, so a fix would be good!

System specs: 2008 iMac running Mac OS 10.10.5, with Plover version 4.0.0.dev1+20.g60a373f 

Also, when I was typing that version number in there, I discovered that my stroke for the decimal point -- {^.^} -- changed to {^.^^} for some odd reason.

--gdw

Glen Warner

unread,
May 27, 2017, 4:53:26 AM5/27/17
to Plover
Whoops! I forgot to post a screenshot of what the fixed dictionary looks like:

 Here you go:



--gdw
 

Ted Morin

unread,
May 27, 2017, 6:17:01 AM5/27/17
to Plover
But reports should be opened on GitHub to make it easier to talk them.


As a workaround, you could define these strokes in a JSON dictionary.

--
You received this message because you are subscribed to the Google Groups "Plover" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ploversteno+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Glen Warner

unread,
May 28, 2017, 9:10:46 PM5/28/17
to Plover
On Saturday, May 27, 2017 at 3:17:01 AM UTC-7, Ted Morin wrote:
But reports should be opened on GitHub to make it easier to talk them.


As a workaround, you could define these strokes in a JSON dictionary.



Thanks for the reminder, Ted! Just made the report.

 I'm not a big fan of .json dictionaries, mostly because I have yet to find a good way to convert an .rtf file to a .json file on the Mac. I did find a couple online tools but they didn't actually do anything, so that was a bit of a waste of time ... but it has been a few months since that last search ...

--gdw

Ted Morin

unread,
May 28, 2017, 9:35:44 PM5/28/17
to Plover
Why not just start a new dictionary (in json) for things like html editing?

--

Glen Warner

unread,
May 28, 2017, 9:57:14 PM5/28/17
to Plover
On Sunday, May 28, 2017 at 6:35:44 PM UTC-7, Ted Morin wrote:
Why not just start a new dictionary (in json) for things like html editing?

I could probably do that, but it is also affecting all of my punctuation in my main dictionary as well.

--gdw 
Reply all
Reply to author
Forward
0 new messages