Fcitx: Input Method Editor Made Easy On Linux

ありがとう!!!

ありがとうございました

it works, thx man.

does this work on wayland

Sadly I only ever got rime to work and it's dictonaries kinda suck

最近Linuxを使い始めたのでとても助かりました。
動画を作ってくれてありがとう。

Followed all the instructions, can't switch between Japanese IM and my defaut Bépo (French) at, all . This is fustrating. [EDIT, a couple hours later] Scratch that, one good update and a reboot later, Fcitx somehow started running perfectly. Not on St, but it's really cool. ありがとうございます！

I'm stuck at the bit where you type really quick to open something up and edit the thing and mention Zsh, bash and fish. basically. How do I do this on a Steam Deck?

So I'm not getting the input to work inside of my terminal. Works everywhere else though. Any help appreciated :)

Try buying a Chinese keyboard 😅

Some times it's not just to avoid having a special keyboard, Simplified Chinese is always written using an IME, using pinyin

Life saver bro thank you

thx bro

best tutorial

I don't get how to make fcitx to toggle between 3 languages, EN, DE, JP. It just toggles between two languages? Any ideas?

is there a way to get it to display romanji alongside the hirigana / katakana

Bro you saved me alot thank you so much

really appreciate the video!

ありがとうごさいます

for those who's wondering the meaning of the words in the thumbnail, it means "Dumb Foreigner"

is there a way to tell fcitx to input the japanese text as you type it? instead of telling you what you're currently typing inside that popup box i want it to actually insert the text into the textbox as i type? i know that was possible since i had it enabled, but for some reason one day it just switched off or smth idk?

Thank you for sharing. I installed the JP input method according to your steps. I can't switch the JP input method on the alacrity terminal, but it can be on the browser. What should I do to make the terminal switch the JP input method?

Wouldn’t it be easier to buy an Apple iPad mini?

there is so many holes in this tutorial for people who doesnt have a boner for the terminal and just wanna install and use the input method that they want to use. almost as if linux users just like to tweak their os infinitely rather than use a computer as a tool for doing actual stuff

How do I add mozc as an input method from the command line?

why did you decide to go with fcitx instead of fcitx5?

I have tried to replicate the same process you have. So far it's failed in 2 VMs as well as my host system. Everything should be working perfectly but it seems that it's not working in the end.

The little widget appears and is able to open up once i sourced the dotfile. I was able to add the Mozc keyboard as well. But the switching command doesn't let it function how it should. Can someone help me? It's for my sister's japanese uni work

liked, favorited and subscribed

Install the entire 1.1 GiB of noto fonts and you are good to go

ありがとうおざいました

煩いですね？　ありがとうございます

How do i autostart ? Noob here

How do you use fcitx on a terminal emulator like Kitty? Everything works on other windows. ありがとう。

how would i open the profile?

Setting the environment variables in .bash_profile didn't work for me in Manjaro.
Writing them instead in /etc/environment (as the arch wiki suggests) did.
Thanks for the express guide!

I'm having a stupid trouble with IntelliJ, which captures the raw keys I've defined in my custom keyboard layout. So, for example, I've defined [Caps+L] as [Right] so that I can navigate on my compact 60% keyboard, which IntelliJ does not understand since it captures [Caps] followed by [L], instead of capturing the equivalent [Right] arrow key. I can use my custom keyboard configuration just fine with Emacs, but IntelliJ would be nice to have integrated as well.

I'm a complete newbie on this sort of stuff and I don't know what would be the starting point for such kind of thing, assuming that there's a way to sort out this matter, which I also do not have a clue about. Any ideas?

For those interested, my custom keyboard layout is googled like this: github frgomes carpalx hyena
Note: at the time of this writing, the latest and greatest version of the layout still needs to be pushed onto the kernel.

Thanks!

Thanks a lot! That saved me a lot of hassle!

Few years back i installed mozc on ubuntu with no problems but after switching to arch i had no luck getting any sort of japanese input working.
This finally fixed it
ありがとうございます

You made my day! I study japanese too ... :))
ありがとございました

btw even if you buy physical japanese keyboard (JIS layout), you still need some sort of input method to convert to 漢字.
my personal favorite is uim (and SKK) since i find it most configurable without too much plugins, and because of uim-fep

it might be easier to just use some tools like `im-config' if you are using display managers.
It worked for me on gdm but not on startx.
If you are using startx its probably easier to config everything manually, but you might be able to
get away with just sourcing some relevant scripts inside /etc/X11/Xsession.d/

You might need to change your locale to something of utf-8 variant that is not C (like en_US.UTF-8 or ja_JP.UTF-8 for that matter), to get uim working on some older program that only utilizes XIM which was the case for me.

One thing to correct, you can't get the "Japanese" keyboard, because the number of characters are much more than the key you have on the keyboard. Though, there does exist some keyboard layouts (it's still on software side instead of hardware) that may directly produce Katanana and Hiragana, you won't be able to type Kanji with it. Input method editor is always required for languages like Chinese/Japanese.

Also as fcitx developer I'd like to know which part of fcitx5 change that you don't like about?

For me fcitx has always been the most annoying thing to configure on a new system 🤦

What was the issue that you were having with uim?

I didn't think that putting export lines in your shell environment would translate over to your xsession (unless you are starting x as a child of a shell, but then I didn't think source would work).

If you are interested in trying uim out, all I had to do to get it working was to stick this in my .xprofile:

export GTK_IM_MODULE='uim'
export QT_IM_MODULE='uim'
uim-xim &
export XMODIFIERS='@im=uim'

You then have to set it up with /uim-pref-(gtk3?|qt5)/

Wont work in the terminal, though. For that you need uim-fep, which I never got around to setting up. uim-fep runs $SHELL as a child, so you can call get your terminal to start it, and then it will start the terminal. IIRC my terminal was intercepting choice of conversion key stroke... and I never got around to working around it.

Nice! By the way, how are you learning Japanese?

Is it possible to use vim key like alt+[hjkl] instead of up/down/lt/rt to select words in fctix?

fcitx5，wonderful！

Its 2021 entering hindi is tough as its a alpha syllabary or abugidā. We have total 36 consonants which are half consonants or alphabets when we add a vowel it become a full consonants. Which is a syllabary. When two or more consonants come together it will be a half consonants.
Until a vowel mark is added depends on the place like i (कि) (ki)will be added to the left y will be added to the right (की) (kī a long AND super hard i) and ā or hard a will be to the right(का) (kā). A which is ă us just a letter क. When it is a e sound it is added in the top के when æ is put not hard e it is placed in the same place as ke but with double stroke कै( looks like ő of mygar.) We use the classical pronunciation of latin with some major changes. There are total of 15 vowels represent by 11 symbol and a consonant harmony. Even it is at down when the is a u sound कु ku
हमारी भाषा कठीन है। not due to script but due to the spelling and grammar and sounds and cases. As e is said as a English a. I is said as a e.