c466e55

.tickets/5-row-support.md deleted (view file)

@@ -1,16 +0,0 @@-Pinchord does not have built-in support for boards with 5 rows on each side, like the sweep.--Ortholinear NKRO boards with 2 or more thumb keys and 5 rows should be supported, and out of the box.--This would lower Pinchord's hardware constraints, and allow Pinchord to work on the proportionally large number of ortholinear NKRO boards that were not designed for steno, like the sweep.-------These boards could be supported by moving `&` above `+` moving `e` to the right `*`, moving `^` to the left asterisk, and making `&/` capitalize the next word.--Currently, both the Plover and Javelin implementations reset the capitalization and space suppression state before every stroke (via `{}`), so this behavior would need to be toggleable.--This layout would be nearly as feasible and efficient as using Pinchord with a Uni or Picosteno, the only difference being that you have to split capitalization into a prefix stroke (some users want to do this anyway)--- This would also allow the stenoob and tinymod to work!-- Still not as good as something like a starboard but for people that already have those boards that'd be very nice

.tickets/README.md deleted (view file)

@@ -1,14 +0,0 @@-Pinchord's tickets--All of these need worked on, if you're looking for somewhere to contribute :p--If something isn't here, don't hesitate to suggest it to me!--## Tickets--See release.md for things that need done before release--Other things to figure out:--- space-naked-finals.md-- reverse-lookup.md

.tickets/chord-format.md deleted (view file)

@@ -1,30 +0,0 @@-A standard format for Pinchord chords.--## Symptoms--There are currently two main implementations of Pinchord being maintained alongside each other.-This is not only much more work to maintain for me, but also forces Pinchord derivations to choose-between two bad choices: support their derivation for a single platform (plover or javelin), or-maintain them both, which, from experience, slows down development more than it should.--Really, there is no way to mod Pinchord without choosing one (or maintaining two) format.--## Why--- There is no single format that can be used to mod Pinchord-- Pinchord sits on 2 hosts - Plover and Javelin, which are two very different engines-- Pinchord wants the lowest barrier to adoption possible, and choosing only one host reduces the number of people that can use Pinchord-- Not all keyboard firmwares can be modified to run Pinchord, and not everyone wants to mess with their firmware, many would rather just install an app.-  The opposite is true for other people, who would rather have the system run on their keyboard without the hassle of needing to run an app.--Goals:-1. Allow you to trivially mod Pinchord-2. Work across both Plover and Javelin-3. Be stable forever so that pre-release users can continue to use the version they're on after release--Pinchord should act more as a chorded typing platform, and the default chords should just sit on top of that like any other chords would.--Uses:-- Downloading someone else's system without already having Pinchord-- Modifying the default Pinchord chords (or anyone else's)-- Switching to someone else's sytem while already using Pinchord or another system

.tickets/closed/fix-brief-suffixes.md deleted (view file)

@@ -1 +0,0 @@-Moved to fix-brief-affixes.md

.tickets/closed/format-chords.md deleted (view file)

@@ -1,6 +0,0 @@-Format `chords.edn`, and the python dictionary chords.--- Re-format `chords.edn` to show `&`, `^`, and `*` outlines next to their non-alternate counterparts.-- Remove all the commas (not sure how they even got there)--Closed because this isn't important.

.tickets/closed/improve-graphics.md deleted (view file)

@@ -1,8 +0,0 @@-Some potential issues with the layout graphics (https://grahp.dev/pinchord-full-v25.png)--1. They're overwhelming-2. They show _all_ chords, even ones that aren't important to someone first learning the layout-------Closed, Not really a part of this repo lol.

.tickets/closed/plover-python-dict.md deleted (view file)

@@ -1,9 +0,0 @@-Plover python dictionary for Pinchord.--- [x] Include the python dictionary Plover plugin in the Pinchord plugin--The dictionary should be easy to edit so that anyone can go and change the chords :)-------2026/31/1 Done

.tickets/contractions-dict.md deleted (view file)

@@ -1,11 +0,0 @@-Add a dictionary to one-stroke contractions.--My idea is to use `AOIU^` plus whatever the normal chord would be?--`AOIU^PKF` -> I'd-`SWRAOIU^R` -> you're-`SHAOIU^L` -> she'll--- Doesn't feel very "pinchordy"-- This would have to work for all pronouns, that doesn't sound like an easy task :p-- These are just briefs, they are not mandatories nor the write-outs for these contractions. Those use the symbols dict

.tickets/contractions.md deleted (view file)

@@ -1,25 +0,0 @@-Pinchord currently cannot write contractions such as "it's", "he'll", "can't", etc. in one stroke per syllable, which is a goal of Pinchord.-------You could potentially add contraction finals, but I think they're impossible to place reasonably well.--You could also make a contractions brief dictionary that looks something like this:--`AOIU^PKF` -> I'd-`SWRAOIU^R` -> you're-`SHAOIU^L` -> she'll--(see contractions-dict.md)--Of course, this somewhat defeats the purpose of Pinchord, as you'd need to create briefs for all pronouns and contractions.--While these are technically briefs and not write-outs, I don't think that distinction is particularly important when these are the default outlines you use.--The cleanest option is, of course, to do nothing, and keep contractions taking usually 3 strokes, or 2 more than the number of syllables. However, contractions are very common, and this would be a clear place Pinchord is strictly less efficient than serial typing.--I think a contractions dict plus write-outs using the punctuation dictionary would be the best way to go about this.--It would also be possible to make naked finals not suppress space anymore, and to make strokes like `/-L` to `'ll`...--There are a limited number of spellings like that, so that might be good.

.tickets/emit-all-misstrokes.md deleted (view file)

@@ -1,13 +0,0 @@-Currently, whether or not a misstroke actually translate to and emits anything depends on whether the stroke you accidentally pressed is valid or not.--Due to the way Pinchord's Javelin orthospelling dictionary works, a stroke that contains any chords that are not in the dictionary will translate to `{}`, which is not added to the undo stack.--However, if you happen to hit a chord that is not the one you intended, but is a valid chord in the dictionary, your stroke will translate to something, and will be added to the undo stack.--This means that after you realize you've made a mistake, you have to react to whether the stroke actually translated into anything, and only undo it if it did.-------Fixing this would require not using the Javelin orthospelling dictionary.--I haven't made a ticket for it, but I am currently writing a javelin script to do this.

.tickets/extensible-chords.md deleted (view file)

@@ -1,11 +0,0 @@-There is no trivial way to extend Pinchord, to share your extensions, or to use other people's extensions.--Very little about Pinchord's implementation is specific to the particular chords that Pinchord uses, and Pinchord is meant to be extended and modified to fit the particular use case of a user.--The way to solve this would be to make a standard format for chords that works on both Plover and Javelin that is trivial to extend by users.-------Implementing a single chord format that can be used on both Plover and Javelin is tricky.--I think the best way to do it might be to work from what Javelin can do, and to build a Plover plugin to read that dictionary. This might not be the nicest format to work with, but I don't see a better way to do this on Javelin.

.tickets/fix-brief-affixes.md deleted (view file)

@@ -1,8 +0,0 @@-Affix keys `#`, `+`, `e`, and `s` don't work for briefs on both the Plover and Javelin implementations.--This is because Pinchord uses a Plover plugin and Javelin orthospelling file for its main logic, including `#+es`, meaning any user dictionaries on top of the python and orthospelling dictionaries don't interact with the affix keys.--On Javelin, you may be able to set `#` and `+` to send console commands like `process_strokes KPA`--On Plover, retro remove space does work on _strokes_, but there is not "retro capitalize last stroke", only a "retro capitalize last word" (which won't work for multi-word strokes)-

.tickets/mods-dict.md deleted (view file)

@@ -1,7 +0,0 @@-Pinchord needs a way to write numbers, symbols, movement, and modifiers.-------This could be implemented as a JSON dictionary, or somehow integrated into the chords format (chord-format.md) so that the mods could also be modified and shared easily.--This would be bets implemented as a JSON dictionary

.tickets/plover-plugin-default-keymaps.md deleted (view file)

@@ -1,3 +0,0 @@-Add default keymaps for the plover plugin--Right now there is just one for keyboard, not for any of the steno protocols.

.tickets/plover-plugin-registry.md deleted (view file)

@@ -1,3 +0,0 @@-Getting Pinchord into the Plover plugins registry so you don't have to enter a Git URL.--See plover-plugin.md

.tickets/plover-plugin.md deleted (view file)

@@ -1,3 +0,0 @@-- [x] Python Dict-- [ ] plover-plugin-default-keymaps.md-- [ ] plover-plugin-registry.md

.tickets/release.md deleted (view file)

@@ -1,18 +0,0 @@-Checklist for releasing Pinchord.--Release means that a version is stable and you can continue to use it forever without issue.--It doesn't mean that nothing can change after that, though of course a lot more care should be taken to changing things.--Generally, after release, it will be intended that people stick with the version they learn even if a new one comes out.-They can switch if they'd like to, but it probably wouldn't be worth the effort.--Checklist:-- [ ] chord-format.md-- [ ] mods-dict.md--From README.md:-- contractions.md-- plover-plugin.md-- emit-all-misstrokes.md-- fix-brief-affixes.md

.tickets/reverse-lookup.md deleted (view file)

@@ -1,3 +0,0 @@-- zipsegv's patch in the discord-- Helpful for plover users-- Nice to get an algorithm for this

.tickets/space-naked-finals.md deleted (view file)

@@ -1,7 +0,0 @@-Naked finals should include a space like every other stroke and bank does.--They currently don't so that `/-S` can be a cheap stroke, but `/+-S` is also an almost equally cheap stroke.--I'm not really sure, `/-S` could definitely be made a special exception, but that would be quite confusing.--For consistency, it's quite weird that it works like this.