[BRLTTY] SPEAK_NEXT_WORD and word boundaries in Debian Trixie

[Eric Scheibler]

Dave Mielke <Dave at mielke.cc> schrieb am 26.01.2026,  4:13 -0500:
> Would you like ASPK_DEL/REP/INS_CHARS to stay on m,comma,period or do you think they should move up to j,k,l and that the ones currently on j,k,l should move to the lower row?

I don't use any of them besides ASPK_INS_CHARS. Therefore no, I don't think a change is necessary here. At least I don't
care much if the keyboard shortcut is modifier+. or modifier+l.

> Could you please experiment with these values and let me know which ones work best? The rate for navigating by character, word, and line are separate. Right now they're hard-coded. Look in ktb_translate.c for case BRL_CMD_SPEAK_PREV_CHAR. Starting from there you'll find the three values.

My values:

``` Programs/ktb_translate.c
        case BRL_CMD_SPEAK_PREV_CHAR:
        case BRL_CMD_SPEAK_NEXT_CHAR:
          return MSECS2PREFS(250);

        case BRL_CMD_SPEAK_PREV_PWRD:
        case BRL_CMD_SPEAK_NEXT_PWRD:
        case BRL_CMD_SPEAK_PREV_WORD:
        case BRL_CMD_SPEAK_NEXT_WORD:
          return MSECS2PREFS(250);

        case BRL_CMD_SPEAK_PREV_LINE:
        case BRL_CMD_SPEAK_NEXT_LINE:
          return MSECS2PREFS(400);
```

> While they're hard-coded for now, being as it's an experiment, I'm not one for leaving it like that. What do you think of making all three of them separate choices in the Speech submenu?

Yes, definitely a good idea, please do so. These values will vary, among others, depending on ones speech rate setting.

Cheers
Eric