pinchord-10 Brief Affixes
Pinchord · pinchord.git · Tickets · Changelog
A Pinchord Ticket (Completed):
Ticket · History
- August 8, 2026 Add all the things (title: Brief Affixes)
Changes
@@ -0,0 +1,35 @@+---+title: Brief Affixes+permalink: pinchord/brief-affixes/+ticket: open+redirect_from:+ - pinchord/fix-brief-affixes/+---++*A [[pinchord-tickets|Pinchord Ticket]] (Open):*++## Symptom++The affix keys `#`, `+`, `e`, and `s` do not work for user-defined outlines, including briefs, in [[Pinchord|Pinchord]] for Plover and Javelin.++## Problem++Pinchord's main dictionary, including the capitalization and spacing logic, is implemented using a Javelin orthospelling yaml file and a Plover Python dictionary. Both of these are separate mechanisms from briefs, which are generic dictionary entries. Both Plover and Javelin don't have a native way to express prefix keys like Pinchord's `#` and `+` keys, so these keys must be implemented some other way.++## Implementation++This must implemented independently for Plover and Javelin, and shipped at the same time to keep parity.++### Javelin++In the past, I tried capturing steno key presses and releases via a Javelin script, but this is a hacky workaround, and caused problems with the Javelin web tools.++The creator of Javelin brought up adding prefixes to the Javelin system configuration, similar to how suffixes currently work.++Because Javelin doesn't have prefixes, Pinchord doesn't use the system suffixes, which would correctly work for `e` and `s` with user defined outlines. If prefixes are added, this would solve the issue.++System suffixes are "on the list, just not at the top", so I'll be waiting to move forward with this.++### Plover++Plover has more customization available than Javelin, so this should be easier. I haven't looked into implementing affixes on Plover, but it should be possible. - September 13, 2026 Edited
Changes
@@ -8,9 +8,13 @@ *A [[pinchord-tickets|Pinchord Ticket]] (Open):* +**Ticket** \| [[pinchord-brief-affixes-history|History]]+ ## Symptom -The affix keys `#`, `+`, `e`, and `s` do not work for user-defined outlines, including briefs, in [[Pinchord|Pinchord]] for Plover and Javelin.+The affix keys `#`, `+`, `e`, and `s` do not work for user-defined entries, including briefs, in [[Pinchord|Pinchord]] for Plover and Javelin.++The prefix keys `#` and `+` can be used on their own in the stroke before a user entry, and the entry's translation will obey these prefixes. This is a bug, as Pinchord is meant to be stateless. ## Problem - October 20, 2026 Change formatting
Changes
@@ -12,7 +12,7 @@ ## Symptom -The affix keys `#`, `+`, `e`, and `s` do not work for user-defined entries, including briefs, in [[Pinchord|Pinchord]] for Plover and Javelin.+The affix keys `#`, `+`, `e`, and `s` do not work for user-defined entries, including briefs, in [[Pinchord]] for Plover and Javelin. The prefix keys `#` and `+` can be used on their own in the stroke before a user entry, and the entry's translation will obey these prefixes. This is a bug, as Pinchord is meant to be stateless. - October 21, 2026 Update the rest of the ticket pages to use numbers (renamed from pinchord-brief-affixes.md, status: none → open, category: none → triaged, type: none → bug)
Changes
@@ -1,15 +1,13 @@ --- title: Brief Affixes-permalink: pinchord/brief-affixes/-ticket: open+status: open+category: triaged+type: bug redirect_from: - pinchord/fix-brief-affixes/+ - pinchord/brief-affixes/ --- -*A [[pinchord-tickets|Pinchord Ticket]] (Open):*--**Ticket** \| [[pinchord-brief-affixes-history|History]]- ## Symptom The affix keys `#`, `+`, `e`, and `s` do not work for user-defined entries, including briefs, in [[Pinchord]] for Plover and Javelin. - October 23, 2026 Remove trailing slashes
Changes
@@ -4,8 +4,8 @@ category: triaged type: bug redirect_from:- - pinchord/fix-brief-affixes/- - pinchord/brief-affixes/+ - pinchord/fix-brief-affixes+ - pinchord/brief-affixes --- ## Symptom - October 24, 2026 Update the brief affixes ticket
Changes
@@ -8,30 +8,22 @@ - pinchord/brief-affixes --- -## Symptom+## Symptom(s) -The affix keys `#`, `+`, `e`, and `s` do not work for user-defined entries, including briefs, in [[Pinchord]] for Plover and Javelin.+The affix keys `#`, `+`, `e`, and `s` do not work for user-defined entries, including briefs. The prefix keys `#` and `+` can be used on their own in the stroke before a user entry, and the entry's translation will obey these prefixes. This is a bug, as Pinchord is meant to be stateless. ## Problem -Pinchord's main dictionary, including the capitalization and spacing logic, is implemented using a Javelin orthospelling yaml file and a Plover Python dictionary. Both of these are separate mechanisms from briefs, which are generic dictionary entries. Both Plover and Javelin don't have a native way to express prefix keys like Pinchord's `#` and `+` keys, so these keys must be implemented some other way.+Affix keys do not work on user-defined entries. ## Implementation -This must implemented independently for Plover and Javelin, and shipped at the same time to keep parity.+Pinchord's main dictionary, including the capitalization and spacing logic, is implemented as a Python dictionary. This is an entirely separate mechanism from briefs, which are regular dictionary entries. -### Javelin+Plover has no way to natively express prefix keys, so these must be implemented as a part of the plugin. -In the past, I tried capturing steno key presses and releases via a Javelin script, but this is a hacky workaround, and caused problems with the Javelin web tools.+Plover plugins can register extensions, which are able to adorn lookup. This can be used to strip affixes from the stroke, and then add them back to the translation after lookup. -The creator of Javelin brought up adding prefixes to the Javelin system configuration, similar to how suffixes currently work.--Because Javelin doesn't have prefixes, Pinchord doesn't use the system suffixes, which would correctly work for `e` and `s` with user defined outlines. If prefixes are added, this would solve the issue.--System suffixes are "on the list, just not at the top", so I'll be waiting to move forward with this.--### Plover--Plover has more customization available than Javelin, so this should be easier. I haven't looked into implementing affixes on Plover, but it should be possible.+This has the downside that the extension needs to be enabled in the `Plugins` tab when setting the plugin up for the first time. After implementing this, [[Setting up Pinchord]] needs to be updated. - October 24, 2026 Edited (status: open → closed)
Changes
@@ -1,6 +1,6 @@ --- title: Brief Affixes-status: open+status: closed category: triaged type: bug redirect_from:@@ -8,22 +8,32 @@ - pinchord/brief-affixes --- -## Symptom(s)+*Closed, fixed in [[Pinchord Changelog#Pinchord Pre-release 31|Pre-release 31 v3]]* -The affix keys `#`, `+`, `e`, and `s` do not work for user-defined entries, including briefs.+## Symptom++The affix keys `#`, `+`, `e`, and `s` do not work for user-defined entries, including briefs, in [[Pinchord]] for Plover and Javelin. The prefix keys `#` and `+` can be used on their own in the stroke before a user entry, and the entry's translation will obey these prefixes. This is a bug, as Pinchord is meant to be stateless. ## Problem -Affix keys do not work on user-defined entries.+Pinchord's main dictionary, including the capitalization and spacing logic, is implemented using a Javelin orthospelling yaml file and a Plover Python dictionary. Both of these are separate mechanisms from briefs, which are generic dictionary entries. Both Plover and Javelin don't have a native way to express prefix keys like Pinchord's `#` and `+` keys, so these keys must be implemented some other way. ## Implementation -Pinchord's main dictionary, including the capitalization and spacing logic, is implemented as a Python dictionary. This is an entirely separate mechanism from briefs, which are regular dictionary entries.+This must implemented independently for Plover and Javelin, and shipped at the same time to keep parity. -Plover has no way to natively express prefix keys, so these must be implemented as a part of the plugin.+### Javelin -Plover plugins can register extensions, which are able to adorn lookup. This can be used to strip affixes from the stroke, and then add them back to the translation after lookup.+In the past, I tried capturing steno key presses and releases via a Javelin script, but this is a hacky workaround, and caused problems with the Javelin web tools. -This has the downside that the extension needs to be enabled in the `Plugins` tab when setting the plugin up for the first time. After implementing this, [[Setting up Pinchord]] needs to be updated.+The creator of Javelin brought up adding prefixes to the Javelin system configuration, similar to how suffixes currently work.++Because Javelin doesn't have prefixes, Pinchord doesn't use the system suffixes, which would correctly work for `e` and `s` with user defined outlines. If prefixes are added, this would solve the issue.++System suffixes are "on the list, just not at the top", so I'll be waiting to move forward with this.++### Plover++Plover has more customization available than Javelin, so this should be easier. I haven't looked into implementing affixes on Plover, but it should be possible. - October 24, 2026 Edited
Changes
@@ -10,30 +10,22 @@ *Closed, fixed in [[Pinchord Changelog#Pinchord Pre-release 31|Pre-release 31 v3]]* -## Symptom+## Symptom(s) -The affix keys `#`, `+`, `e`, and `s` do not work for user-defined entries, including briefs, in [[Pinchord]] for Plover and Javelin.+The affix keys `#`, `+`, `e`, and `s` do not work for user-defined entries, including briefs. The prefix keys `#` and `+` can be used on their own in the stroke before a user entry, and the entry's translation will obey these prefixes. This is a bug, as Pinchord is meant to be stateless. ## Problem -Pinchord's main dictionary, including the capitalization and spacing logic, is implemented using a Javelin orthospelling yaml file and a Plover Python dictionary. Both of these are separate mechanisms from briefs, which are generic dictionary entries. Both Plover and Javelin don't have a native way to express prefix keys like Pinchord's `#` and `+` keys, so these keys must be implemented some other way.+Affix keys do not work on user-defined entries. ## Implementation -This must implemented independently for Plover and Javelin, and shipped at the same time to keep parity.+Pinchord's main dictionary, including the capitalization and spacing logic, is implemented as a Python dictionary. This is an entirely separate mechanism from briefs, which are regular dictionary entries. -### Javelin+Plover has no way to natively express prefix keys, so these must be implemented as a part of the plugin. -In the past, I tried capturing steno key presses and releases via a Javelin script, but this is a hacky workaround, and caused problems with the Javelin web tools.+Plover plugins can register extensions, which are able to adorn lookup. This can be used to strip affixes from the stroke, and then add them back to the translation after lookup. -The creator of Javelin brought up adding prefixes to the Javelin system configuration, similar to how suffixes currently work.--Because Javelin doesn't have prefixes, Pinchord doesn't use the system suffixes, which would correctly work for `e` and `s` with user defined outlines. If prefixes are added, this would solve the issue.--System suffixes are "on the list, just not at the top", so I'll be waiting to move forward with this.--### Plover--Plover has more customization available than Javelin, so this should be easier. I haven't looked into implementing affixes on Plover, but it should be possible.+This has the downside that the extension needs to be enabled in the `Plugins` tab when setting the plugin up for the first time. After implementing this, [[Setting up Pinchord]] needs to be updated. - October 24, 2026 Rename tickets to <project>-<number> <title> (renamed from pinchord@10.md, title: Brief Affixes → none)
Changes
@@ -1,5 +1,4 @@ ----title: Brief Affixes status: closed category: triaged type: bug - October 24, 2026 Replace ticket status, category and resolution with ticket (status: closed → none, category: triaged → none)
Changes
@@ -1,6 +1,5 @@ ----status: closed-category: triaged+ticket: dismissed type: bug redirect_from: - pinchord/fix-brief-affixes - October 26, 2026 Edited
Changes
@@ -1,5 +1,5 @@ ----ticket: dismissed+ticket: completed type: bug redirect_from: - pinchord/fix-brief-affixes