Skip to content

Rmk207 MCCS codes for virtualkeyboards plus eliminate IPA homoglyphs#2688

Open
rmkaplan wants to merge 4 commits into
masterfrom
rmk207--MCCS-codes-for-VIRTUALKEYBOARDS-plus-eliminate-IPA-homoglyphs
Open

Rmk207 MCCS codes for virtualkeyboards plus eliminate IPA homoglyphs#2688
rmkaplan wants to merge 4 commits into
masterfrom
rmk207--MCCS-codes-for-VIRTUALKEYBOARDS-plus-eliminate-IPA-homoglyphs

Conversation

@rmkaplan

Copy link
Copy Markdown
Contributor

This adjusts the display and keyboard mappings to take account of the arrow/caret interchanges, and to eliminate the confusion in the Unicode mappings because XCCS associates the same glyphs with IPA codes and other codes (as discussed in PR #2687).

This is independent of the NSDISPLAYSIZE issue and fonts, in that it chooses the default keyboard font based on its height. However, for reasons that I don't yet understand, the labels on the keyboard (NEXT, EXPAND) seem to be in a bigger font, even though as best as I can tell, those are specified as Helvetic 5, which is not involved in any of this font stuff.

As a separate point: The French keyboard seems a little goofy, in that shift d does produces a circumflex-o and not capital D. And shift e is also odd.

There is still a black box in the logic keyboard. Is there an image anywhere of what character is supposed to be there?

This also modernizes the keyboard display windows, so they can be dragged around by their title bars.

@rmkaplan

Copy link
Copy Markdown
Contributor Author

Actually, the problem with the labels appears only with the enlarged NS fonts, even though I don't think NS is involved there. This is compatible with current master in that regard.

One other virtualkeyboard issue: the keyboard displays have the left panel taken over from the dandelion or daybreak, with a bunch of labeled buttons that are not connected to any actions. Some of them could make sense and could be armed for Tedit or Sedit (e.g. Undo, Find, Cut, Open), but I think it would be better just to eliminate those buttons. A lot of the labels on the function key and number pad also aren't meaningful.

(BTW: What does "RDMND" stand for?)

@pamoroso

Copy link
Copy Markdown
Member

On Linux Mint 22.1 Cinnamon the arrows are now displayed correctly and the labels fit within the function keys. However, F10 is missing the label LOOKS.

The logic keyboard is displayed in this screenshot. Now the left arrow just to the left of RSHIFT is displayed as _.

@nbriggs

nbriggs commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

The Daybreak/Dandelion left keys should all be tied to the keyboard bits that were originally attached to the physical keys on those machines. Likewise the top function keys and the right keypad. The Lyric/Medley (?) release notes should have the key number mappings. If you wanted to change anything, making the display of the additional keyboard sections optional on a FLG would make sense. Removing them would not be helpful, especially if you have code that was written to use those keys.

@nbriggs

nbriggs commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

"RDMND" is Right DiaMoND.

@pamoroso

Copy link
Copy Markdown
Member

I wasn't clear, I meant that left arrow just to the left of RSHIFT in the DEFAULT keyboard is displayed as _.

@pamoroso

Copy link
Copy Markdown
Member

Apologies again for the confusion, it's the LOGIC keyboard I meant, not the default one.

@rmkaplan

Copy link
Copy Markdown
Contributor Author

"RDMND" is Right DiaMoND.

OK, then, what is/was Right diamond?

Apologies again for the confusion, it's the LOGIC keyboard I meant, not the default one.

That's another MCCS update, I'll do that.

On your earlier image, the key to the left of that arrow key has a small empty-set symbol, I now see a black box there. What do you see now?

On the F10-LOOKS, we have now defined it so that F10 is the way of typing underscore. We can change that back to LOOKS, for old times sake. But then you wouldn't be able to type an underscore when this is switched in.

@pamoroso

Copy link
Copy Markdown
Member

At commit 91a12c7, I see the DEFAULT and LOGIC keyboards like this:

vkeyboards

The black box is still there and the left arrow is fixed. As for F10 and LOOKS it makes sense, thanks.

@rmkaplan

rmkaplan commented Jul 11, 2026 via email

Copy link
Copy Markdown
Contributor Author

@rmkaplan

rmkaplan commented Jul 11, 2026 via email

Copy link
Copy Markdown
Contributor Author

@nbriggs

nbriggs commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

I'm just at a place where I can see the images -- Those are Sun keyboards (type-4, I think) -- check this against the Lyric/Medley release notes. In theory, I suppose the virtual keyboards should adapt to the actual physical keyboard you have, but we haven't got that information coming through in a way that it can easily be used (there's a 3(?) bit field that indicates the keyboard type). Sun keyboards had a diamond key to the right of the space bar. Please don't remove bits of the keyboard layouts until we can work out a proper plan for how it should work.

@nbriggs

nbriggs commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

This is the Sun type-4 keyboard that VirtualKeyboards assumes you're working with. image
Maiko/Medley never accounted for international versions of the Sun keyboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants