[Fedora-i18n-bugs] [Bug 1051405] New: inscript2 layouts are not supported in ibus-typing-booster
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1051405
Bug ID: 1051405
Summary: inscript2 layouts are not supported in
ibus-typing-booster
Product: Fedora
Version: rawhide
Component: ibus-typing-booster
Assignee: apatil(a)redhat.com
Reporter: asaini(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: apatil(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
mfabian(a)redhat.com
Description of problem:
inscript 2 is enhanced version of inscript layout but it is not supported in
ibus-typing-booster
Version-Release number of selected component (if applicable):
ibus-typing-booster-1.2.7-1.fc19.noarch
How reproducible:
everytime
Steps to Reproduce:
1. try to select inscript 2 punjabi from regional and language settings
2.
3.
Actual results:
inscript 2 not available
Expected results:
it should be there
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=4mOvztvc67&a=cc_unsubscribe
8 years, 3 months
[Fedora-i18n-bugs] [Bug 675503] New: Commit Hangul character with space key -> Move the character.
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Commit Hangul character with space key -> Move the character.
https://bugzilla.redhat.com/show_bug.cgi?id=675503
Summary: Commit Hangul character with space key -> Move the
character.
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Linux
Status: NEW
Severity: high
Priority: unspecified
Component: ibus
AssignedTo: tfujiwar(a)redhat.com
ReportedBy: sangu.fedora(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: tfujiwar(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com
Classification: Fedora
Description of problem:
Commit Hangul character with space key -> Move the character.
Version-Release number of selected component (if applicable):
1.3.99.20110127-1.fc15.x86_64
How reproducible:
always
Steps to Reproduce:
1. input with hangul input method
2. 가가 (rkrk)
3. click space key
Actual results:
가 가
Expected results:
가가
Additional info:
ibus-hangul-1.3.0.20100329-4.fc15.x86_64
glib2-2.27.93-1.fc15.x86_64
gtk2-2.24.0-1.fc15.x86_64
gtk3-2.99.3-1.fc15.x86_64
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
8 years, 3 months
[Fedora-i18n-bugs] [Bug 1145725] New: Swing Java app loses keyboard input when used with ibus
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1145725
Bug ID: 1145725
Summary: Swing Java app loses keyboard input when used with
ibus
Product: Fedora
Version: 21
Component: ibus
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: rjt(a)zygous.co.uk
QA Contact: extras-qa(a)fedoraproject.org
CC: extras-qa(a)fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, nomnex(a)gmail.com,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
I've cloned an older bug because I'm effectively seeing the same problem,
albeit with a newer version of ibus and with PhpStorm instead of Freemind. I
think the Java app itself is irrelevant, it's the fact that it's a Java app
that's pertinent.
The symptoms are as described below, to whit: after running the app for a while
(some hours) it refuses to respond to the keyboard any longer. Using the mouse
still works. Restarting ibus-daemon causes PhpStorm to crash (it used to be
that restarting the daemon would fix the problem for a while, but no longer).
Restarting PhpStorm does resolve the problem for a time.
+++ This bug was initially created as a clone of Bug #800736 +++
Description of problem:
Please help with directions (package, or upstream bug tracker):
I have first reported a bug about the Freemind package, in 2011, after losing
keyboard input when using Japanese
see:
http://sourceforge.net/tracker/?func=detail&aid=3178894&group_id=7118&ati...
I have a limited understanding of interaction between the different software,
but reading a similar issue ibus+java applications, see:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/481656 and
http://code.google.com/p/ibus/issues/detail?can=2&q=&colspec=ID%20Compone...
(closed)
It seems that ibus, when used with Java applications, causes the lose of
keyboard input.
Version-Release number of selected component (if applicable):
ibus 1.4.1
OpenJDK
freemind 0.9 (Java application)
Fedora 15
How reproducible: always
Steps to Reproduce:
1. Open freemind (ibus working)
2. either input English (my default language) either Japanese
3.
Actual results:
after some time, any key press is ineffective in the Java application. The
workaround is to turn off ibus.
Expected results:
Input Japanese (using ibus) in Freemind.
Additional info:
--- Additional comment from fujiwara on 2012-03-07 01:33:33 EST ---
Which shortcut keys do you try to use?
--- Additional comment from nomnex on 2012-03-07 04:48:37 EST ---
no shortcut.
Ibus is running, I start Freemind. I can input English, or Japanese, but after
a (short) time, any key press stop working in the Java application (I can only
mouse click on the menus.)
It only affects the Freemind GUI, outside of it, I can type.
To re-gain keyboard input in Freemind, I must stop ibus. Then I can type again
in Freemind. If I restart ibus, I can't input Japanese in the Freemind window
(I can's select Japanese input[MOZEC or ANTHY] as long as Freemind window is in
focus. If I click on a another window, I can select Japanese input as usual).
If I want to input Japanese again in Freemind, I must first terminate Freemind,
and re-open it.
--- Additional comment from nomnex on 2012-03-12 01:48:05 EDT ---
It there a way I can help debugging this on my end? I have no message when I
launch Freemind from the terminal, and when the bug occurs.
After a few minutes of usage, I can not type anything in Freemind. The keyboard
is not responsive. The only workaround is to quit ibus.
can you reproduce the issue, or am I the only one affected by this problem?
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.6) (fedora-63.1.10.6.fc15-i386)
OpenJDK Client VM (build 20.0-b11, mixed mode)
Thank you.
--- Additional comment from fujiwara on 2012-03-12 02:19:14 EDT ---
I don't think ibus does not work with Java applications.
I guess a Freemind bug or setting failures something. I'm a bit busy for F17.
It would be nice if you could confirmed the behavior with jedit.
--- Additional comment from nomnex on 2012-03-13 10:47:03 EDT ---
(In reply to comment #4)
> I guess a Freemind bug or setting failures something. I'm a bit busy for F17.
Of course, I understand.
> It would be nice if you could confirmed the behavior with jedit.
I installed jedit jar (all platform) in my user directory for a test run. It
may not be the proper installation, because Java path was not defined. I did
not find a rpm jedit.
Running $ jedit, I can input Japanese fine.
This is the exact symptom I experience when I use Freemind & ibus:
--start--
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/481656
I use ThinkingRock, a Java application, and after some time the keyboard input
stops working for this application, meaning I can still use my mouse to
manipulate the program, but I cannot type anything. When closing the iBus
Daemon the input works again after some seconds. Also restarting the Java
application helps to postpone the problem until it occurs again some minutes
later.
I'm using Ubuntu 9.10 with version 1.2.0.20090927-2ubuntu2 of iBus and version
2.2.1 of ThinkingRock. My Java version is 6-15-1.
Please notice: I do NOT want to input Chinese or Japanese or anything like it.
I just want to normally use my keyboard. I also have NO input method selected,
I have the input methods turned OFF.
I have yet to test this behavior with other Java applications (maybe it's a bug
in ThinkingRock?), so I'd be happy if somebody can confirm this bug for other
Java applications. Because the solution is to quit the iBus Daemon, I suspect
iBus to be the problem.
--end--
a ibus developer commented on the launchpad bug: Peng Huang (shawn-p-huang)
#comment 3
--- Additional comment from nomnex on 2012-03-13 19:46:53 EDT ---
I think I found the problem:
- This notebook suffers a LXDE panel bug (known bug).
- My other notebook with integrated GPU Intel and similar F-15 LXDE is not
affected by the LXDE panel bug. I tried Freemind + ibus and it worked fine.
>From this starting point, I changed ibus preferences: Show icon on system tree
(Cleared)
It seems to work! I don't lose input in Freemind after a few minutes.
On question: I lost the ability to turn ibus input on-off with a mouse click
(the input, not the daemon). What is the command line to turn ibus input
on-off?
Thank you again.
--- Additional comment from nomnex on 2012-03-14 02:27:34 EDT ---
It does not work...
after a few hours (vs. a few minutes, before) the bug is here again. The
keyboard cannot input anything in the Freemind window, unless I kill
ibus-daemon. Gosh.
--- Additional comment from nomnex on 2012-03-26 05:36:50 EDT ---
The cause of the input problem was: LXPANEL.
Changing panel (XFCE) on my system solved the issue. I can input Japanese in
Freemind.
See for information: https://bugzilla.redhat.com/show_bug.cgi?id=803098
Thank you.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=54erDBHhqt&a=cc_unsubscribe
8 years, 5 months
[Fedora-i18n-bugs] [Bug 648350] New: Proper Bold for Lohit Devanagari
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Proper Bold for Lohit Devanagari
https://bugzilla.redhat.com/show_bug.cgi?id=648350
Summary: Proper Bold for Lohit Devanagari
Product: Fedora
Version: rawhide
Platform: All
OS/Version: All
Status: NEW
Severity: medium
Priority: low
Component: lohit-devanagari-fonts
AssignedTo: psatpute(a)redhat.com
ReportedBy: ujjwol(a)fedoraproject.org
QAContact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
psatpute(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Created attachment 456789
--> https://bugzilla.redhat.com/attachment.cgi?id=456789
Picture showing the bold and regular typeface
Description of problem:
The existing font provided Lohit Devangari only contains the regular version.
It does not contain the bold version. When the computer generates bold using
the regular font, and the results are ugly. The siro-rekha is broken and many
other stuffs are also broken.
Version-Release number of selected component (if applicable):
How reproducible:
Exactly reproducible
Steps to Reproduce:
1.See any hindi/nepali/marathi/sanskrit pages in firefox with bold text
2. type devanagari text in openoffice and bold it
Actual results:
The a broken lohit devanagari font is displayed.
Expected results:
A well maintained bold should be shown.
Additional info:
The typographic value is lost when bold is used though it is still readable.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
8 years, 5 months
[Fedora-i18n-bugs] [Bug 1146124] New: [abrt] ibus: bus_dbus_impl_dispatch_message_by_rule(): ibus-daemon killed by SIGSEGV
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1146124
Bug ID: 1146124
Summary: [abrt] ibus: bus_dbus_impl_dispatch_message_by_rule():
ibus-daemon killed by SIGSEGV
Product: Fedora
Version: 21
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: sgraf(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Version-Release number of selected component:
ibus-1.5.9-1.fc21
Additional info:
reporter: libreport-2.2.3
backtrace_rating: 4
cmdline: ibus-daemon --xim --panel disable
crash_function: bus_dbus_impl_dispatch_message_by_rule
executable: /usr/bin/ibus-daemon
kernel: 3.16.3-300.fc21.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (8 frames)
#0 bus_dbus_impl_dispatch_message_by_rule at dbusimpl.c:1901
#1 bus_dbus_impl_connection_filter_cb at dbusimpl.c:1578
#2 on_worker_message_about_to_be_sent at gdbusconnection.c:2429
#3 _g_dbus_worker_emit_message_about_to_be_sent at gdbusprivate.c:497
#4 continue_writing at gdbusprivate.c:1492
#5 continue_writing_in_idle_cb at gdbusprivate.c:1553
#10 gdbus_shared_thread_func at gdbusprivate.c:273
#11 g_thread_proxy at gthread.c:764
Potential duplicate: bug 850539
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=xu0fUFUTuT&a=cc_unsubscribe
8 years, 6 months
[Fedora-i18n-bugs] [Bug 1016989] New: [ml_IN] non-standard sequence sequence for stacked chillu-N and RRA in Lohit Malayalam font should be removed
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1016989
Bug ID: 1016989
Summary: [ml_IN] non-standard sequence sequence for stacked
chillu-N and RRA in Lohit Malayalam font should be
removed
Product: Fedora
Version: rawhide
Component: lohit-malayalam-fonts
Assignee: psatpute(a)redhat.com
Reporter: samjnaa(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com
This is related to bug #1016984 which I reported just now.
As per TUS 6.2 chapter 9.9 p 321 (p 351 of PDF) the correct sequence to get the
display of stacked chillu-N on top of RRA in Malayalam is: CHILLU N + VIRAMA +
RRA. That is: ൻ്റ = 0d7b 0d4d 0d31. However, currently Lohit Malayalam font
does not support this sequence. In bug #1016984 I have requested to add it.
Apart from that, note that currently the sequence being used to display stacked
chillu-N on top of RRA in Lohit font is ന്റ = 0d28 0d4d 0d31. This is
non-standard. It is inadvisable to retain this sequence as having two
canonically non-equivalent sequences display the same is a security issue of
confusability.
My request from the POV of being standard-compliant would be to remove this
sequence.
However I am sure (based on personal email communication) there will be
objection from people such as Santosh Thottingal since they do not agree with
the standard on this matter. They maintain that NA + VIRAMA + RRA is the
correct sequence to get this display.
I have told them that if they disagree with the standard then they should
discuss the matter on the Unicode and try to make the Unicode Technical
Committee accept their view. Otherwise such sequences will just be
standards-non-compliant and the existing diversified situation will only be
aggravated.
Certainly the current standard-prescribed sequence should be included to be
standards compliant. For that I have already filed the separate bug. For 100%
compliance the old non-standard should be removed. To track that I am filing
this bug now.
In the face of community objection, it is up to the project maintainer to
decide about this.
Version-Release number of selected component (if applicable):
2.5.4
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=4mzVmSKdWJ&a=cc_unsubscribe
8 years, 6 months
[Fedora-i18n-bugs] [Bug 1028911] New: [zh_TW]'Chinese<->English' switch does not work when clicking on the Chewing menu list.
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1028911
Bug ID: 1028911
Summary: [zh_TW]'Chinese<->English' switch does not work when
clicking on the Chewing menu list.
Product: Fedora
Version: 20
Component: ibus-libpinyin
Severity: high
Assignee: pwu(a)redhat.com
Reporter: lijli(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Depends On: 1028905
+++ This bug was initially created as a clone of Bug #1028905 +++
Description of problem:
'Chinese<->English' switch does not work when clicking on the Intellignet
Pinyin menu list.
Version-Release number of selected component (if applicable):
ibs-chewing-1.4.3-4.fc20.x86_64
libchewing-0.3.4-4.fc20.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Install latest Fedora20 tc6 build.
2. Add an input source which has (Intelligent Pinyin) in the name.
3. Click on the Chewing menu on the top right of desktop.
4. Click on Chines/English (中CN/英EN, 中/英)from the list to switch the input of
'Chinese-English'.
Actual results:
'Chinese<->English' switch does not work when clicking on the Chewing menu
list.
Expected results:
It should auto switch for 中CN/英EN, 中/英.
Additional info:
Please see the attached screenshot.
--- Additional comment from Lijun Li on 2013-11-11 03:07:34 EST ---
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1028905
[Bug 1028905] [zh_CN]'Chinese<->English' switch does not work when clicking
on the Intellignet Pinyin menu list.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=mXuMqdUFbL&a=cc_unsubscribe
8 years, 10 months