----- Original Message -----
On 07/08/16 20:41, Bastien Nocera-san wrote:
> I think that the emoji input method should be a separate input method, so
> that most users would have the choice between inputting using the keyboard
> layout that matches their keyboard, and a separate input method for
I think the emoji typing does not depend on XKB but is used frequently and I
don't think it should be separated.
It is on every other platform I can think of.
If the engine should be enabled by default for any languages, I think
would make sense that the XKB engines also enable emoji and switching
would be more cost than switching input modes.
Once this feature is implemented, the translatable annotations also can be
implementable for input method engines.
I think other platforms does not separate engines for emoji typing.
> The IBus XKB engine is not discoverable (it's not listed in
> & Language settings) and the keyboard shortcut to input emojis is also not
> discoverable. Having a separate input method is likely the better way to
> implement this.
I replied this.
You haven't. You're implementing this without any regards for prior art and
design work that's been done. You certainly can implement this internally
however you want, but the end result has to match certain expectations, and
designs. Your implementation won't, and as a result won't be discoverable.