I use Ubuntu 14.04, and work with Fcitx all the time. It is great! I use it with three languages: Hindi, Bengali, and Sanskrit.
Fcitx is working very well, but there is an issue with it and I do not know whether to call it a bug or a design flaw. Whatever it is, it needs to be fixed. It is a problem that seems to occur with Fcitx in any app I’ve used it in– gedit, TB, Libre Office. The issue is that when it is enabled and one is typing using it, then it is a common practice to have to disable it for a few English words, and then again enable it to resume typing in Fcitx. Well, what happens is that when one has typed a word in Fcitx and hits space to create a separation between the last word and the next word, then if at that point one does ctrl-space to disable Fcitx, the final letter of the previous word gets erased.
The reason I see this happening is that up to that moment, the line underneath the previous word’s last letter is still there, indicating that although I’ve hit the space bar, Fcitx still hasn’t let go of the previous word’s last letter– and so when I do ctrl-space, that last letter gets deleted. It doesn’t happen with all words; only if the last word ends in what is called an inherent “a”–which is very often the case in Hindi, Bengali, and Sanskrit– then it happens. It never happened like this when I was using scim all those years, so I suspect it is an issue in Fcitx. scim is not working properly in Ubuntu 14.04, so I have switched to Fcitx.
I have looked hard for a Fcitx reporting site, but could not find one. Can you let me know where to report this so that those in charge of fixing bugs can look into the solution.
Hello again,
I’ve been using fcitx for the past three weeks with great success. (There was only the problem reported above in my previous post above, to which you’ve replied that that matter is fixed in the next version of fcitx. I’ll have to wait for Ubuntu to bring that into their repositories.)
But today a very serious problem suddenly arose. The letters are all working fine, but the punctuation, such as — ,.:;”-()[]{} — all of those have become defective when fcitx is enabled. What happens is that any time I type one of the puncuation keys, the cursor jumps around 2-3 spaces ahead before placing the punctuation mark, and after the punctuation mark again jumps 2-3 space ahead for the next letter to be typed. That places around 6 spaces between every word where there is punctuation. That’s in gedit. And in Thunderbird, it jumps like that even when I hit the space bar between words! Can you guide me how to fix this? All my work is frozen until I can get this fixed.
I don’t think this is a bug, because everything was working fine before. It is perhaps some setting that needs to be fixed?
@Swarup I don’t quite understand your problem, let me have a guess..
Did you enable the full width character? (Check the tray menu for state) And you can check the global config to see if there’s a key assigned to trigger it (It should be empty by default now though).
You are a life saver! That is all it was– the full width character was enabled. I have no idea what that is, and I had no idea that it had gotten enabled. For one day my life turned into one type of hell as I tried to figure out what in the world had happened to my wonderful fcitx. I had a feeling it was some sort of setting that got changed– and indeed it was. Now thanks to your insight, eveything is back to normal.
About这里应该加一句：“因为内存分配小又常常部署新玩意儿，所以网站间歇性失灵……”
[Reply]额……你吐槽效率真高。。
[Reply]踩一下。
[Reply]你这里许多文字做了模糊特效？
css的text-shadow，文字没有模糊。只需一行- -b
话说我还真没用opera测试过这个页面……嗯，测试发现和文字和我的firefox看起来一样，不过背景有断裂= =b。
另外看这个opera真卡。。。。
[Reply]好久没有来拜访了……上了学才发现依然会忙的……也懒得写博了。wordpress好用么？blogbus让我越来越不习惯了……
[Reply]还行吧
不过要考虑功夫网因素
这个空间是我自己买的
[Reply]忽然觉得点阵字体有点难看了，建议换个字体吧。我在ubuntu里很少见到点阵字体，这里是难得一见的一个。
[Reply]@cmheia 我表示选择强制使用浏览器字体就可以了。
[Reply]– -我还以为女的…用这样的背景
[Reply]@Willin Wang 明显是宅男风格的……
[Reply]女性才用男的做背景呢。
一直都想让LINUX下的输入法支持直接出汉字，即不显示候选框
[Reply]又不知道怎么搞
好好搞~
[Reply]哟~ 难道你和 Twitter 上的 CSSlayer 是一个人？！
[Reply]@平芜泫 上面写的那么清楚。
[Reply]这样提供email的方式挺有意思的～
[Reply]我只是想看看我的UA。
[Reply]话说，这个先UA的更详细嘛
[Reply]签约了可以实现什么愿望呢？
还有@csslayer应该读成CSS Layer的吧233
[Reply]支持小企鹅！！！！！！
[Reply]我只是想說我沒裝 GnuPG 怎麼辦……
[Reply]不考虑弄個 reCAPTCHA Mailhide ?
[Reply]用火狐目前倒是没502…
[Reply]Test UA.
[Reply]看到了野生的OpenBSD党一个
[Reply]这个WP theme的背景是自动抓取的么?
[Reply]@.txt 手动设的啊
[Reply]怎么来搞这个,对这个还是有感情的。
[Reply]对了，我应该 @你的.. @csslayer
[Reply]@xixitie What?
[Reply]个人觉得内容块背景透明度小点比较好。这样的背景图片，加上透明度，文字的识别度很低，眼花缭乱看不下去。
[Reply]transifex上的Owncloud_Chinese协调员csslayer是你么
[Reply]过来看看PGP密钥的。。。
[Reply]顺便留名
I use Ubuntu 14.04, and work with Fcitx all the time. It is great! I use it with three languages: Hindi, Bengali, and Sanskrit.
Fcitx is working very well, but there is an issue with it and I do not know whether to call it a bug or a design flaw. Whatever it is, it needs to be fixed. It is a problem that seems to occur with Fcitx in any app I’ve used it in– gedit, TB, Libre Office. The issue is that when it is enabled and one is typing using it, then it is a common practice to have to disable it for a few English words, and then again enable it to resume typing in Fcitx. Well, what happens is that when one has typed a word in Fcitx and hits space to create a separation between the last word and the next word, then if at that point one does ctrl-space to disable Fcitx, the final letter of the previous word gets erased.
The reason I see this happening is that up to that moment, the line underneath the previous word’s last letter is still there, indicating that although I’ve hit the space bar, Fcitx still hasn’t let go of the previous word’s last letter– and so when I do ctrl-space, that last letter gets deleted. It doesn’t happen with all words; only if the last word ends in what is called an inherent “a”–which is very often the case in Hindi, Bengali, and Sanskrit– then it happens. It never happened like this when I was using scim all those years, so I suspect it is an issue in Fcitx. scim is not working properly in Ubuntu 14.04, so I have switched to Fcitx.
I have looked hard for a Fcitx reporting site, but could not find one. Can you let me know where to report this so that those in charge of fixing bugs can look into the solution.
Thanks,
[Reply]Swarup
@Swarup You can either use github / google code.
https://code.google.com/p/fcitx/issues/list
[Reply]https://github.com/fcitx/fcitx/issues
Ok, great– thank you so much. I’ll go ahead and report it there.
[Reply]Hello again,
I’ve been using fcitx for the past three weeks with great success. (There was only the problem reported above in my previous post above, to which you’ve replied that that matter is fixed in the next version of fcitx. I’ll have to wait for Ubuntu to bring that into their repositories.)
But today a very serious problem suddenly arose. The letters are all working fine, but the punctuation, such as — ,.:;”-()[]{} — all of those have become defective when fcitx is enabled. What happens is that any time I type one of the puncuation keys, the cursor jumps around 2-3 spaces ahead before placing the punctuation mark, and after the punctuation mark again jumps 2-3 space ahead for the next letter to be typed. That places around 6 spaces between every word where there is punctuation. That’s in gedit. And in Thunderbird, it jumps like that even when I hit the space bar between words! Can you guide me how to fix this? All my work is frozen until I can get this fixed.
I don’t think this is a bug, because everything was working fine before. It is perhaps some setting that needs to be fixed?
Thank you!
Swarup
[Reply]@Swarup I don’t quite understand your problem, let me have a guess..
[Reply]Did you enable the full width character? (Check the tray menu for state) And you can check the global config to see if there’s a key assigned to trigger it (It should be empty by default now though).
You are a life saver! That is all it was– the full width character was enabled. I have no idea what that is, and I had no idea that it had gotten enabled. For one day my life turned into one type of hell as I tried to figure out what in the world had happened to my wonderful fcitx. I had a feeling it was some sort of setting that got changed– and indeed it was. Now thanks to your insight, eveything is back to normal.
[Reply]不翻墙，上不来 斯密达～
[Reply]Nice blog and nice posts:)
[Reply]我也只是想看看UA –fcitx-googlepinyin
[Reply]“””
Fcitx
来和我签订契约，成为fcitx开发者吧！
Fcitx的bug请到 http://code.google.com/p/fcitx/issues/
Fcitx使用的讨论请到 https://groups.google.com/group/fcitx
Fcitx开发的讨论请到 https://groups.google.com/group/fcitx-dev
“””
Google Code的链接是不是应该更新了？
[Reply]围观扫墓（斜眼
[Reply]