dx-packages team mailing list archive

[Rolf Leggewie <1043627@xxxxxxxxxxxxxxxxxx>]

raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".

** Changed in: unity (Ubuntu Raring)
       Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1043627

Title:
  [SRU] Add XIM Support to Nux

Status in Nux:
  Fix Released
Status in Nux 2.0 series:
  Fix Committed
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Committed
Status in nux package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in nux source package in Quantal:
  Won't Fix
Status in unity source package in Quantal:
  Won't Fix
Status in nux source package in Raring:
  Won't Fix
Status in unity source package in Raring:
  Won't Fix

Bug description:
  [Impact]

  As 12.04 is an LTS, many users decide to stay with that version until
  the next LTS version is available. Many of those users require
  different input methods to comfortably input characters in their
  language. We do support IBus for some of the languages, but others are
  still using XIM as the input framework. Those users cannot input in
  their language using their standard input methods. This means using
  the Dash and HUD is much more troublesome or even impossible in normal
  cases.

  We think that even though it is essentially a new feature, it can be thought that the lack of support for non-IBus additional input methods is a bug in a way.
  It is a big change, but with proper testing, we would ensure that the addition does not introduce any new regressions.

  This addition would make many MANY users happy, which can be seen at
  least by the number of affected people in LP: #983254.

  Also, the change is needed by OEM. It is a big change, but it's
  crucial for CJK - Kyrlin has voiced the proposition to use fctix as
  the default input method, which _needs_ XIM support in Nux and Unity.

  [Test Case]

  1. Install fctix-pinyin
  2. Run im-config and enable fctix as the default IM
  3. Reboot your machine
  4. Open the dash and input non-latin characters using fctix
     -> Non latin characters (Chinese in this case) should appear on screen.

  [Regression Potential]

  In an impossible scenariu, broken IBus input or input in overall in Nux input fields.
  The good thing about the XIM support is that it's rather isolated, so potential breakage of the XIM code won't impact normal Nux workflow. Just XIM input might not work.

  The author of the code, Brandon, also mentions that new regression
  potential is low as the XIM code is not being used by default. As XIM
  is not the default, when IBus is present - without explicitly setting
  XIM in im-config, the XIM parts are not even accessed.

  [Other Info]

  The same functionality is already available in the newer Unity
  releases.

  Original description:

  Right now the only input method (IM) that works with Unity/Nux is
  IBus. This means anyone who uses a different IM would have to switch
  to IBus in order to type in their language.

  This is something that needs to be fixed and will make Unity/Nux
  friendlier to those who use different IMs. If you do not use an IM
  then this will not affect you.

  XIM was the very first IM framework for the X window system, which
  means most IMs are supported by it.

  A List of IMs that will be supported by this branch (There could be more):
  http://en.wikipedia.org/wiki/List_of_input_methods_for_UNIX_platforms

  All of those under XIM will now work in Unity and Nux with this
  branch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/1043627/+subscriptions