On 23 November 2012 18:49, Ma Xiaojun <damage3...@gmail.com> wrote: > They made something even more surprising; white listing input engines > and properties input engines can expose. > > The first one does affect us, though a patch would be easy to write. > We have decent packages for every working IBus engines in our > repository (except ibus-libpinyin, it may requires IBus 1.4.99, I'm > not sure). We also have our own way of shipping input methods > packages. Then what? GNOME force downstreams to follow them. > https://bugzilla.gnome.org/show_bug.cgi?id=688914#c10 > > Even if they offered a gsettings key for show_all_sources. It is by > definition non-discoverable. Worse, it will show XKB duplicates, > useless m17n engines, ... That probably make the input source list > unnecessarily much longer.
It's very easy for Ubuntu as a distro to change a gsettings default (that's what ubuntu-settings and ubuntu-gnome-default-settings do). And it doesn't sound like it would be too difficult to patch gnome-shell to support a few more ibus properties. But for now, we don't have to worry too much about either of those concerns since I believe there's universal agreement that Ubuntu should stick with ibus 1.4 until the other concerns are addressed (at the least, support for separate layout per window and incompatibility with non-ibus input methods). Jeremy -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss