I have been loyal to opera since opear 6. It was a major innovator. For example, multiple tab browsing, mouse gesture, and speed dial was their invention.
However, for us, CJK linuxer, riding with opera was and is bumpy. While with other browsers you can just install and play, you have to manually set a environment to make it works, or use Google to dig out "forbidden" qt4 or static build.
Now came to the era of 10.5x, great, there is no known way to enable input methods. No ibus, QT_IM_MODULE, xim, not at all.
Finally, when I reach the opera forum, their answer is something like, "No, not yet, please wait until we are ready for final." Well, just hope I don’t have to wait too long.
Current I maintain both zhcon and fbterm.
Even zhcon development is inactive at the moment, but it is still remembered and even embraced by many CJK console users. The pros of zhcon over fbterm:
- Provides vga mode, no need to enter framebuffer mode.
- Has various buildin input methods.
- Supports GB2312 GB2312, GBK, etc.
Cons of zhcon
- Support utf8 through iconv gb2312 -> utf8, it causes characters missing
- Input methods fails on x86_64
To sum up, if you are using GB2312 encoding on a i386 machine, then zhcon works for you. But if you want utf8, or you have x86_64 machines, then bad luck.
On the other hand, fbterm supports utf8, no need to mock font setting, and the latest version support screen rotation! This is convenient to me, as I no longer need to bend my neck to check the output.
Although fbterm still haven’t have officical input methods, but given that fbterm is under active development, and Peng Huang mentioned that he has a successful story of using ibus in fbterm, I am confident that fbterm will replace zhcon.