Comment #10 on issue 787 by [email protected]: [ibus-table]基于ibus-table的输 入法无法记忆繁简模式
http://code.google.com/p/ibus/issues/detail?id=787
There's no ibus-gconf package in the ibus package hierarchy (at least anymore, there may have been one before).
The bug I mentioned just prevents any table engine with invalid characters in its name (in this case spaces) from saving any settings at all. So we need to fix the table files regardless. The table file to db converter program (engine/tabcreatedb.py in the ibus-table package) should also idealky be fixed to check for invalid NAME field values in table txt files to prevent this from happening.
There doesn't seem to be a binding for gconf_valid_key from gconf.c in the python bindings; however, the restrictions are that keynames must all be ascii (ord(c)<=127) and mustn't contain any of the following: " \t\r\n\"$&<>,+=#!()'|{}[]?~`;%\\" (taken from invalid_chars in gconf.c).
-- You received this message because you are subscribed to the Google Groups "ibus-devel" group. iBus project web page: http://code.google.com/p/ibus/ iBus dev group: http://groups.google.com/group/ibus-devel?hl=en
