Bug 1222160 - Incorrect symbol for kk (Kazakh) m17n layouts
Summary: Incorrect symbol for kk (Kazakh) m17n layouts
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus-m17n
Version: 29
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Mike FABIAN
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-15 22:57 UTC by yerlaser
Modified: 2018-12-18 06:47 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-12-18 06:47:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description yerlaser 2015-05-15 22:57:58 UTC
Description of problem:
I use ibus-m17n for my language kk - Kazakh.
Because our country plans migration to latin script I created a new m17n layout table for phonetic entry.
I add my new mim file to /usr/share/m17n and my new phonetic input works.

However, in the language selector on the top panel, the short name (symbol) of the language shows as an arabic letter.
It should be "kk", like e.g. "en" for English.

I found a fix for it.
The package ibus-m17n contains a wrong config file.
/usr/share/ibus-m17n/default.xml

It contains the following lines:

        <engine>
                <name>m17n:kk:*</name>
                <symbol>قا</symbol>
        </engine>

The lines are wrong because it sets the arabic symbol for all custom keyboard layouts while the correct symbol is "kk".

Those lines should be changed to the following:

         <engine>
                <name>m17n:kk:*</name>
                <symbol>kk</symbol>
        </engine>
        <engine>
                <name>m17n:kk:arabic</name>
                <symbol>قا</symbol>
        </engine>


This way it only shows arabic symbol for the arabic layout.

Please advise what I should do to have it fixed in Fedora permanently.

Comment 1 yerlaser 2015-05-16 19:19:59 UTC
I created a Google Code issue 1781 in the upstream project.

https://code.google.com/p/ibus/issues/detail?id=1781

Comment 2 Fedora End Of Life 2016-07-19 19:34:40 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Jan Kurik 2016-07-26 04:14:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 4 Fedora End Of Life 2017-11-16 19:12:44 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2018-02-20 15:30:03 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 6 Mike FABIAN 2018-12-18 06:14:35 UTC
I fixed it upstream: https://github.com/ibus/ibus-m17n/pull/1

The fix is in ibus-m17n-1.4.1

Comment 7 Mike FABIAN 2018-12-18 06:47:51 UTC
The fixed package is already in rawhide.

I just submitted an update for f29: https://bodhi.fedoraproject.org/updates/FEDORA-2018-b10cae47d5


Note You need to log in before you can comment on or make changes to this bug.