Linux FAQ Lines and the IBus/Fcitx Guide
FAQ states scope; download anchors releases; the guide handles framework work.
Direct answer: On Linux, read the FAQ first to confirm Translation IME support scope; if you need desktop framework setup, open the IBus or Fcitx guide next. FAQ gives scope notes—framework guides handle on-desk setup.
1 FAQ for scope, guide for execution
FAQ works like signage; the IBus/Fcitx guide reads like implementation notes for Linux input stacks.
Treating a FAQ sentence as the full manual is how people get stuck on Wayland quirks, permission prompts, or partial app blocks. Signage helps, but you still need the map.
If release entry points were never opened through the download page, stop tuning frameworks until versions align.
2 Signals that merit opening the guide
Missing candidates, switch no-ops, single-app failures, or absent IME listings rarely resolve from FAQ blurbs alone.
Reconfirm the public download path first, then walk the Linux guide against your symptom instead of looping uninstalls.
3 Suggested Linux reading order
Download → FAQ support line → IBus/Fcitx guide → source-check guide if trust is uncertain.
When escalating, include distro, desktop session, pages already read, and exact behavior—not only “Linux failed”.
Continue Checking
FAQ
FAQ mentions Ubuntu 20.04+. Do I still need the Linux guide?
FAQ summarizes visible support scope. Desktop integration, frameworks, and switching still belong in the Linux-focused guide.
Will this article list distro-specific install commands?
No. Commands, package names, or repositories not documented on-site will not be invented here.
How is this different from the Linux source-check guide?
Source-check guides focus on trusting the download chain. This note focuses on routing from FAQ bullets into framework setup guidance.
Use the Linux release entry on Download when installing
If you are ready to install or update, return to the download page and verify the current public version, platform notes, and on-site release information.