News for hackers. Stuff that matters.
Re:WinCompose – A Compose Key for Windows by lithiumfrost on Friday August 13, 2021 @12:17PM (#28170876)
For one, the character coverage is much broader than what's typically found on an international keyboard.

I use it all the time for typing arrows and other symbols, for example. YMMV but I also find it mnemonically better, from time to time I can just guess what the right Compose sequence is.

Re:WinCompose – A Compose Key for Windows by shawnz on Friday August 13, 2021 @01:07PM (#28171602)
Wouldn't it be better to just create a new keyboard layout featuring the composed keys you want, rather than running software constantly in the background to achieve the same thing?

See here for example: https://dailydoseoftech.com/how-to-create-a-custom-keyboard-...

Re:WinCompose – A Compose Key for Windows by jtvjan on Friday August 13, 2021 @01:25PM (#28171823)
Not really. I don't know in advance which symbols I want to type, and even then I'd have to learn where I put the symbols on the custom layout, while the compose sequences I can usually guess. Considering the amount of background processes the typical Windows system runs, having one additional program really doesn't make a difference.
Re:WinCompose – A Compose Key for Windows by shawnz on Friday August 13, 2021 @01:28PM (#28171843)
I don't necessarily mean that each individual user of the software should do this. I mean, why not just create a new layout instead of developing this? Or as a user, why not just use a layout someone else has already developed which has logical choices for the composed keys?

EDIT: Some compelling arguments in favour of the app in this thread. Thank you

Re:WinCompose – A Compose Key for Windows by Symbiote on Friday August 13, 2021 @01:55PM (#28172151)
You'd swiftly run out of practical combinations.

On the 1 key, I have 1 and !. Maybe I could add ¹ and ₁, with AltGr and Shift+AltGr (or Ctrl, or something). Maybe ½ and ¼?

With Compose, I have ¹, ₁, ½, ⅓, ¼, ⅕, ⅙, ⅐, ⅛, ⅑, ⅒, ①, ⑩, ⑪, … ㊶ which involve the 1 key. I do not need to look up the sequences for these, as they're intuitive: Compose ^ 1, Compose _ 1, Compose 1 2, … Compose ( 4 1 ).

Re:WinCompose – A Compose Key for Windows by shawnz on Friday August 13, 2021 @02:09PM (#28172303)
You could maybe use AltGr combined with dead keys to accomplish that, but I suppose it would be limited to combinations of two keys (plus the modifier).

EDIT: Actually, it seems Windows supports chained dead keys, so I think you could accomplish longer sequences with a plain old Windows keyboard layout definition too. But that's not supported with MSKLC.

Re:WinCompose – A Compose Key for Windows by sterlind on Friday August 13, 2021 @01:42PM (#28172028)
you can't compose keyboard layouts, so you'd either have to stick with only QWERTY or generate separate enhanced layouts for Azerty + Dvorak + etc. discoverability would also be harder, and you'd have to hold down every key in the combo instead of pressing them in sequence holding the compose key, so you couldn't distinguish /ae/ vs /ea/ and you'd get carpal tunnel.

side-note: X11 layouts are really frustrating. there's a hard constraint of one key combo -> one Unicode character, which makes it impossible to output multiple characters. I run into this with Lushootseed, which has /ƛ̕/ (glottalized barred lambda encoded as barred lambda + accent marker), but you'd never write it without the accent in that language.

Re:WinCompose – A Compose Key for Windows by bmn__ on Friday August 13, 2021 @07:26PM (#28176118)
> there's a hard constraint of one key combo -> one Unicode character, which makes it impossible to output multiple characters.

The orthodox solution for this problem is an IME.

Quickest path to success is via editing a new map file /usr/share/m17n/lut.mim (see Blackfoot and Inuktitut in the same directory for examples of multiple character output) and then using the m17n plugin for fcitx or scim or ibus.

Re:WinCompose – A Compose Key for Windows by frosted-flakes on Friday August 13, 2021 @01:46PM (#28172069)
Because a Compose key allows you to type any of thousands of characters, which (a) isn't possible with a custom keyboard layout, and even if it was, (b) would be very difficult to learn.
Re:WinCompose – A Compose Key for Windows by shawnz on Friday August 13, 2021 @02:25PM (#28172444)
What makes this easier to learn? I think you could implement the same kinds of sequences by using AltGr combined with dead keys.
Re:WinCompose – A Compose Key for Windows by frosted-flakes on Friday August 13, 2021 @05:06PM (#28174521)
So you're going to turn every key on the keyboard into a dead key? Also, the compose file can easily be customized, and some entries output multiple characters or involve non-character keys like the arrows. How is that going to work with a static keyboard layout?
Re:WinCompose – A Compose Key for Windows by shawnz on Friday August 13, 2021 @05:11PM (#28174574)
Only AltGr + [the key] would be a dead key, not the bare key itself. Perhaps a tool could be made to convert compose files into Windows keyboard layout definitions with this strategy

That's a good point about non-character keys though, I don't think that could be supported with this method.

Re:WinCompose – A Compose Key for Windows by account42 on Friday August 20, 2021 @08:35AM (#28245290)
> some entries output multiple characters

Too bad that Qt broke support for that in version 5 and has never fixed it.

Re:WinCompose – A Compose Key for Windows by bradrn on Friday August 13, 2021 @09:37PM (#28176990)
I agree! This is exactly what I ended up doing: https://github.com/bradrn/Conkey
Re:WinCompose – A Compose Key for Windows by shawnz on Friday August 13, 2021 @10:00PM (#28177126)
Nice! Thank you for this.