i know this is old but it is genious so i have to ask

[yuitayuun]

as i'm studying english phonetics i thought about this concept for a bit, then i googled it and found your implementation. the idea sounds genious but i don't know how to find my compose key configuration in fcitx5, and i can't find anything online. could you help? i'm willing to switch to ibus or fcitx for it. sorry for the necro!

EDIT: I'm on arch wayland, using niri wm

[psvenk]

No worries; I'm glad that you've found this useful! Looking at my own setup, it seems that fcitx5 respects $XCOMPOSEFILE (which I set in my .profile; the file is in ~/.config/ibus/ only because I used to use IBus but it's generated from the output of this script). There isn't anything in my ~/.config/fcitx{,5}/ that references the Compose key, so this is probably what's controlling it; let me know if it doesn't work and I'll investigate further (and add appropriate documentation).

(For reference, I'm also running Arch with Wayland, using Sway WM.)

[g̥u̟ˀd lˠɐk]!

[psvenk]

I looked into it a bit more, and it seems that fcitx5 uses xkbcommon for Compose key handling, which in turn respects $XCOMPOSEFILE.

[yuitayuun]

thanks! I'll try setting that up tomorrow. I'd basically just have to point the script at the file? (i'll probably figure it out with trial and error)

[yuitayuun]

UPDATE
i am stuck on the "pointing the script" part
~ $ ./ipa-compose/ipa.py > Compose
Traceback (most recent call last):
File "/home/yuitayuun/./ipa-compose/ipa.py", line 66, in
_, glyph, keystrokes, ipa_no, usv, symbol_name, ipa_desc = data
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: too many values to unpack (expected 7)

EDIT: when i sliced it, it said it only has 1 variable

~ [1]$ python3 ./ipa-compose/ipa.py > Compose
Traceback (most recent call last):
File "/home/yuitayuun/./ipa-compose/ipa.py", line 66, in
_, glyph, keystrokes, ipa_no, usv, symbol_name, ipa_desc = data[7]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: not enough values to unpack (expected 7, got 1)

I tried pointing it both at an empty file and /usr/share/X11/locale/en_US.UTF-8/Compose
Polish (which is the keyboard i use) does not have a compose file so I assume i have to make one

[psvenk]

Sorry for the late response. It appears that the Keyman help site's layout has changed slightly, breaking the script — I've fixed it in a2adf71. The error you saw is since the CSS selector had become too general and matched all tables on the page (rather than just the appendix table at the end).

Could you try again on the latest commit? Let me know if it still complains or if fcitx5 is unhappy with it. You should be able to target it to any file as long as you set $XCOMPOSEFILE appropriately and restart your WM. (The canonical choice, which I think fcitx5 respects, would be ~/.XCompose; maybe try that first to make sure it's not an issue with environment variables being set properly.)

[yuitayuun]

My first trial kinda broke my nautilus (gnome’s file manager) so i havent done much with it since, i’ll take another shot at it when i inevitably reinstall my machine soon. Thanks for the responses. I kinda got an ipad for taking notes in my phonetics class (and god forsaken japanese haha) so it’s not a priority to me anymore and im very busy recently. Cheers!

(Will update when i do it)