ibus-speech-to-text will provide voice dictation capabilities to any application supporting IBus input methods in #Fedora Linux 42, using VOSK for local voice recognition.
ibus-speech-to-text will provide voice dictation capabilities to any application supporting IBus input methods in #Fedora Linux 42, using VOSK for local voice recognition.
ibus-typing-booster is now 77% translated to #Kabyle language, thanks to @Taflelli
Contribute to FLOSS on #Fedora Weblate : https://translate.fedoraproject.org/projects/ibus-typing-booster/
Heh. #Bodhi #Linux's native IME went weird and everything. Suddenly, it can only see one variant of a keyboard layout.
So, I tried to install #iBus again, play around with it (which I no longer remember what I did). iBus can type in Hangeul (finally, it didn't work before) but can't type in Baybayin for some weird reason (all xkb files are correct).
In the end, I mixed Bodhi's native keyboard and iBUS. Type baybayin, I switch keyboard through Bodhi's keyboard app; type Hangeul I switch keyboard through iBUS.
As much as I like Bodhi Linux, I'm not going to use this again because of this IME issue. For one, they shouldn't force people to use their native IME/keyboard app. I just can't find a way to make iBUS work properly, and it has been an issue since 2016/2017 as far search engine results are concerned, and no one found a “fix”.
Or maybe, it's not Bodhi's fault, but Moksha or Elementary. I don't know. This is why Gnome, is so popular, you have a choice and it just works.
Found the issue here — after libuim.so
showed up in some stack traces for other things that were crashing (e.g. Element), I installed ibus
and uninstalled uim
, and now everything works again. .
And apparently in some contexts I am now able to do the Super + . shortcut to pull up an emoji picker!
"/~/.pam_environment" に #Fcitx を使う設定を書いたら #iBus に戻れなくなっちゃった的なブログエントリを読み、 #環境変数 ってどういう風に書き込まれているんだ?と疑問に思い出した #Linux
バカには使えないものになりつつあるLinuxの日本語入力環境 https://arimasou16.com/blog/2020/09/01/00325/
Linux デスクトップの環境変数、どこに設定してますか? - インゲージ開発者ブログ https://blog.ingage.jp/entry/2021/05/31/070000
@screwtape No not really except some module packages. Typically #fcitx #ibus, together with #rime are popular in the #Linux world. #rime supports Windows, MacOS and Linux. I use fcitx + rime on #FreeBSD so that might be a good sign for #OpenBSD.
https://github.com/fcitx/fcitx
https://github.com/ibus/ibus
https://github.com/rime/home
IBusのAnthyを使って、ちっちゃい『あ』や『イ』などはどうやって入力するの?
例えば、『フェディバース』の『ェ』と『イ』
『FE』を入力すると『フェ』を出さない…
Aaah #ibus a corrigé le bug des points de code Ctrl+Shift+U (unicode) et Ctrl+Shift+E (emoji), ce bug empêchait de saisir ces caractères… bien content que ce soit de nouveau fonctionnel !
Ah, they joys of C!
#ibus (the input method I use) may have a working, or completely broken, emoji picker, depeding on what order the compiler decides to initialise things, and what things it optimises away.
(also, maybe GLib's type registration system is too complicated to use correctly?)
(issue with details, patch)
OTOH, I love that I could fix it on my machine by just dropping the patch under /etc/portage/patches/app-i18n/ibus-1.5.27/
and rebuilding the package #gentoo #linux
Normal English text contains a great many characters that don't come on the ordinary keyboards I use.
And occasionally I want to write a name or phrase which doesn't use English orthography, right there in my English-language text.
That's why every operating system needs a good #FreeSoftware Input Method Engine, and a good stock of Input Methods to choose from so you can quickly switch to a different writing system and then back again.
I am #ThursdayThankful for #IBus https://en.wikipedia.org/wiki/Intelligent_Input_Bus
ce qui est super dur pour résoudre des bugs de système d'exploitation, même quand on est dev, c'est de savoir quelle partie du bouzin est concerné par le bug pour aller ensuite le rapporter au bon endroit.
la je sais pas si c'est la config clavier de #debian, #cryptsetup, #ibus, ou encore #plymouth.
en tous cas ça fait partie des choses qui montrent à quel point les logiciels ne sont testés que dans des contextes anglophones et non chiffrés
Strangely, with the #ibus input method, some compose key sequences are no longer working for me in xterm and rxvt-unicode, although they work in Firefox and other #GTK apps. For example, I cannot input anything that includes < or > in the sequence, but all others seem to work. And the same sequences with < ad > work too when unsetting XMODIFIERS before starting xterm. (Usually it's set to "@im=ibus".)
Using ibus 1.5.23.
#Linux #OpenSource
Sadly, the IBus ctrl + . shortcut for inserting emoji also conflicts with GNOME’s ctrl + . shortcut for *drumroll* inserting emoji. So, when GNOME is being used, the distribution should really disable or change the IBus shortcut as GNOME’s graphical emoji picker overlay is far superior to the IBus’s.
Also, I think I’m going to end up changing 1Password’s shortcut as I want to be able to use the GNOME emoji picker popover on web forms too.
Using Debian 11 for the first time, I immediately noticed the graphical compose key support. Sure, it's buggy in web browsers (double-typing letters in certain “web applications”), but it gives visual feedback for every keystroke so I'm fine with that.
Did you know that x11-ibus leaks several GiB of memory? Me neither!
And when I restart ibus, it (apparently unrecoverably) breaks… openbox? The mouse? X itself? Who knows? (And that doesn't even fix the leak.)
So… how do I turn off #ibus?
#IBus is a usefully modular, well supported text input method engine. for GNU+Linux desktop.
What input method do you recommend for general “everything on an English-language keyboard plus all the punctuation, alphabets, special symbols, etc. that modern text should have available”?
I've used ‘rfc1345’ for a very long time, but it's never going to be modern and it's time to move on. Maybe ‘latex’? Or what?
Ideally the exact same input method should work in #Emacs too.
Help me, #LazyWeb!