Firstly, I'd like to apologise for vanishing when I had things to do. I've been ill for a while, and I'm not entirely better yet, but I'm hoping I can pick things up again now.
Secondly, someone was offering to take over the Plover debianisation from me. Could you remind me who you were? I can show you the work I'd done if you want to compare it, or I can just sign it all over to you.
Thirdly, someone was asking about the API I was working on. (I forget who that was, too.) I got rather a lot of it finished, but it's not working yet. Let me know if you have any suggestions or improvements. The idea was that a particular endpoint, if given a parameter "t" with some English-language text in it, would return a JSON dictionary with keys as follows:
"ok": 1 for success, 0 for failure.
"message": a message from the server (usually the empty string if "ok"==1)
"outlines": a list of steno outlines as strings (see below)
and possibly some other keys as yet undefined.
The steno outlines are in the usual format, with the exception that the asterisk, and all right-hand keys which share a letter with left-hand keys, are remapped according to the table below. The hyphen is nevertheless included exactly as if it were necessary to disambiguate the left and right sides. This enables client-side code both to display the outlines to humans, and to act upon them, in a manner as simple as possible. Including the asterisk in the remapping also allows outlines to be used as element IDs.
The remapping mentioned above is:
-P => 2
-T => 3
-R => 4
-S => 5
* => 6
This is mostly intended to be used as a back end for improving the steno demo webpage I made a few months back, but of course anyone's free to use it for their own purposes too. If folk are interested I'll get it working to prototype standard, put a working example online, and publish the code.
Best wishes,
Thomas