|
Carl, I will have Claude do these tasks, and if possible will have it/him make a Python standalone script that all can use. (On the reference to the PDF, I got what the differences are--very clearly stated there; and I fed the whole thing to Claude, but I have assigned Claude the task to doing it yet.) Harry On Sun, 19 Jul 2026 01:11:27 -0400, Carl Distefano wrote: > Reply to note from harrybinswanger <dmarc-noreply@xxxxxxxxxxxxx> Sat, 18 Jul 2026 09:16:41 -0400 > > Harry, > > > I'm up and running on Linux Mint! > > Glad to hear it. Send a screenshot; I'm curious to see what it looks like. > > > Next up: translating from XyWrite .kbd file to the new XyScript > > form. > > Part 3 of the Reference (reference.pdf) sums it up pretty well. See especially Section 3.1. The principles are simple. Single characters are assigned the same way as in XyWrite: 30=A. Commas are no longer used to separate strings of characters; simply wrap strings in double quotes: 17="Hello, World!". Single commands are the same as before: 30=AB. Multiple commands are separated by semicolons: 31=SA;AB. As in XyWrite, a semicolon at the start of a line makes the whole line into a comment. For inline comments, use the pound sign plus a space, "# ", which is the new-XPL comment symbol: > > 31=SA;AB # This saves, then aborts, the file > > However, you can't do this with single characters: > > 30=A # This inserts the letter "A" > > will not work; however, the following will: > > 30="A" # This also inserts the letter "A" > 30=INSERT A # So does this > > > How do we use U2 routines in XyScript? > > There's no carryover. You'll have to rewrite them in XyScript's own scripting language. See xyscript.lib for examples. > > > Any plans for a "Making the Transition" PDF? > > No concrete plan at the moment. It's a good idea, though. > > -- > Carl Distefano > cld@xxxxxxxxxx > |