Keyman 11 Beta Feedback


#21

Note that km-config only installs the keyboard into IBus. The step to “install the Input Source in Region & Language Settings.” is needed for it to be used in gnome-shell.

https://help.gnome.org/users/gnome-help/stable/keyboard-layouts.html.en is the Gnome instructions for adding an input source.

For your French example on a system installed as English which doesn’t have French language installed in Manage installed languages on Region & Language settings. First you install the eurolatin keyboard in “Keyman Keyboards”. Then go to the Region & Language settings. The input source will be in Otherand it is called French (EuroLatin (SIL))


#22

Thanks, Daniel, for those pointers. Here’s what I ended up doing:

  • opened “Settings”, “Region & Language”

  • clicked on the “+” below “Input Sources”

  • clicked on the three dots to expand the list (since there are a number of flavo(u)rs of English installed)
    image

  • scrolled down to “Other” and clicked on it
    image

The first time I got to this point, Settings froze up and I had to terminate it and start over. The second time it worked, bringing up a long list of languages. I typed in “french” and scrolled to the “French (EuroLatin (SIL))” entry.
image

I clicked on that entry, then the “Add” button in the top right corner of the dialog. The new item was added to “Input Sources”:
image

and a dropdown selection list was added:
image

Thanks,
David


Linux Keyman keyboard
#23

That looks like a great capture for the docs when they get online… :slight_smile:


#24

Just some general questions/feature requests (I haven’t try version 11, as am still familiarizing with version 10).

  • Is there any automation tool to test a list of keystrokes? Because I have a complex keyboard and when I changed something I want to make sure it still correct for the rest of the stuff that I tested correctly before.

  • And then for context offset, it would be nice to have something like ‘context(1-3)’ instead of ‘context(1) context(2) context(3)’

  • Is it a bug that I cannot do a redo (Ctrl+Y), or is it on purpose? I can do Undo (Ctrl+Z), but redo doesn’t seem to work.

  • It seems that the keyboard rules only work if someone typed it in succession. In other word ‘a’ + ‘b’ > ‘c’ would work if typed in succession, but if I type ‘a’ and go to another line, and go back to ‘a’, typed ‘b’, I would get ‘ab’. So it doesn’t look up what’s the character before, if it’s not typed in succession?

Thank you for the excellent program.


#25

Keyman Developer 11 replaces the underlying code editor with Monaco (a la Visual Studio Code). Using the latest 11.0.1306.0 beta, I can Redo (Shift+Ctrl+Z)

Contexts (and deadkeys) are intentionally cleared when navigating to different lines.


#26

To clarify this a little: modern applications, such as Microsoft Word, that fully support the Text Services Framework, have the ability to report the context to Keyman so contextual input is maintained when moving around the document. Deadkeys are always cleared when location is updated, as they are ephemeral state markers.


#27

Keyman Developer does include a ‘regression testing’ tool. It is in need of some tender loving care as it is getting a bit old, but it does still work. We plan to introduce more robust and extensive unit testing for keyboard layouts in a future version of Keyman Developer.

If you would like to suggest this as a future feature, please visit https://github.com/keymanapp/keyman/issues/new/choose.

I’m really glad Keyman Developer is working for you :slight_smile:


#28

When packaging, selecting keyboard - add, the add window shows briefly and then disappears into the background. I have to press “esc” to cancel it because I can’t find a way to switch to it. Alt-tab doesn’t work to switch to it. Similarly, “help - about” also briefly shows and then fades behind the application. (keymandeveloper-11.0.1307.0 on Windows 7 SP1)

UPDATE: Must have been a UI-library glitch. Closing the program and restarting it fixed that problem. The “hidden in the background” problem started happening to other areas where it had worked earlier…


#30

Sounds like a weird issue. Glad it’s gone away … but let us know if it recurs!


#31

Thank you everyone for your feedback. We’re closing this thread now that Keyman 11 is released.

You can continue to provide feedback in new posts.


closed #32

unpinned #33