[Fedora-i18n-bugs] [Bug 954637] New: [faf] ibus-pinyin-1.4.99.20120808-3.fc17.i686 SIGSEGV in updateLookupTableLabel
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=954637
Bug ID: 954637
Summary: [faf] ibus-pinyin-1.4.99.20120808-3.fc17.i686 SIGSEGV
in updateLookupTableLabel
Product: Fedora
Version: 17
Component: ibus-pinyin
Severity: unspecified
Priority: unspecified
Assignee: pwu(a)redhat.com
Reporter: abrt-bot(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pwu(a)redhat.com,
shawn.p.huang(a)gmail.com
Category: ---
Description of problem:
Faf server recevied number of crash reports for this package.
Problem URL:
https://retrace.fedoraproject.org/faf/problems/bthash/641f0d29c69144eea0f...
Version-Release number of selected component:
ibus-pinyin-1.4.99.20120808-3.fc17.i686
Additional info:
first occurence: 2013-01-03 09:01 UTC
reports count: 10
executable: /usr/libexec/ibus-engine-pinyin
Truncated backtrace:
# Function Path
Source
0 updateLookupTableLabel /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYBopomofoEditor.cc:214
1 updateLookupTable /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYBopomofoEditor.cc:244
2 PyZy::PhoneticContext::updateCandidates /usr/lib/libpyzy-1.0.so.0
3 PyZy::PhoneticContext::update /usr/lib/libpyzy-1.0.so.0
4 PyZy::BopomofoContext::updatePinyin /usr/lib/libpyzy-1.0.so.0
5 PyZy::BopomofoContext::insert /usr/lib/libpyzy-1.0.so.0
6 insert /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYPhoneticEditor.cc:267
7 PY::PhoneticEditor::insert /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYPhoneticEditor.cc:262
8 processBopomofo /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYBopomofoEditor.cc:144
9 processKeyEvent /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYBopomofoEditor.cc:169
10 processKeyEvent /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYBopomofoEngine.cc:118
11 _ibus_marshal_BOOLEAN__UINT_UINT_UINT /usr/lib/libibus-1.0.so.5
/usr/src/debug/ibus-1.4.99.20121109/src/ibusmarshalers.c:296
12 g_type_class_meta_marshal /usr/lib/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gclosure.c:975
13 closure_invoke_notifiers /usr/lib/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gclosure.c:280
14 g_closure_invoke /usr/lib/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gclosure.c:783
15 accumulate /usr/lib/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gsignal.c:3052
16 signal_emit_unlocked_R /usr/lib/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gsignal.c:3594
17 g_signal_emit_valist /usr/lib/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gsignal.c:3306
18 g_signal_emit /usr/lib/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gsignal.c:3358
19 ibus_engine_service_method_call /usr/lib/libibus-1.0.so.5
/usr/src/debug/ibus-1.4.99.20121109/src/ibusengine.c:823
20 ibus_service_service_method_call_cb /usr/lib/libibus-1.0.so.5
/usr/src/debug/ibus-1.4.99.20121109/src/ibusservice.c:403
21 call_in_idle_cb /usr/lib/libgio-2.0.so.0
/usr/src/debug/glib-2.32.4/gio/gdbusconnection.c:4698
22 g_idle_dispatch /usr/lib/libglib-2.0.so.0
/usr/src/debug/glib-2.32.4/glib/gmain.c:4658
23 g_main_dispatch /usr/lib/libglib-2.0.so.0
/usr/src/debug/glib-2.32.4/glib/gmain.c:2539
24 g_main_context_dispatch /usr/lib/libglib-2.0.so.0
/usr/src/debug/glib-2.32.4/glib/gmain.c:3075
25 g_main_context_iterate /usr/lib/libglib-2.0.so.0
/usr/src/debug/glib-2.32.4/glib/gmain.c:3146
26 g_main_loop_run /usr/lib/libglib-2.0.so.0
/usr/src/debug/glib-2.32.4/glib/gmain.c:3339
27 ibus_main /usr/lib/libibus-1.0.so.5
/usr/src/debug/ibus-1.4.99.20121109/src/ibusshare.c:297
28 set /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYPointer.h:43
29 main /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYPointer.h:38
30 __libc_start_main /lib/libc.so.6
/usr/src/debug/glibc-2.15-a316c1f/csu/libc-start.c:258
31 _start /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYMain.cc:192
This ticket was created automatically. If this report is malformed or not
helpful
please let us know on crash-catcher(a)lists.fedorahosted.org so we can improve
it.
--
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=fBEmUaibFw&a=cc_unsubscribe
10 years, 11 months
[Fedora-i18n-bugs] [Bug 954634] New: [faf] ibus-pinyin-1.4.99.20120808-3.fc17.x86_64 SIGSEGV in updateLookupTableLabel
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=954634
Bug ID: 954634
Summary: [faf] ibus-pinyin-1.4.99.20120808-3.fc17.x86_64
SIGSEGV in updateLookupTableLabel
Product: Fedora
Version: 17
Component: ibus-pinyin
Severity: unspecified
Priority: unspecified
Assignee: pwu(a)redhat.com
Reporter: abrt-bot(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pwu(a)redhat.com,
shawn.p.huang(a)gmail.com
Category: ---
Description of problem:
Faf server recevied number of crash reports for this package.
Problem URL:
https://retrace.fedoraproject.org/faf/problems/bthash/5f202794e08e4a432ce...
Version-Release number of selected component:
ibus-pinyin-1.4.99.20120808-3.fc17.x86_64
Additional info:
first occurence: 2012-12-31 23:24 UTC
reports count: 33
executable: /usr/libexec/ibus-engine-pinyin
Truncated backtrace:
# Function Path
Source
0 updateLookupTableLabel /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYBopomofoEditor.cc:214
1 updateLookupTable /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYBopomofoEditor.cc:244
2 update /usr/lib64/libpyzy-1.0.so.0
/usr/src/debug/pyzy-0.1.0/src/PhoneticContext.cc:161
3 updatePinyin /usr/lib64/libpyzy-1.0.so.0
/usr/src/debug/pyzy-0.1.0/src/BopomofoContext.cc:262
4 insert /usr/lib64/libpyzy-1.0.so.0
/usr/src/debug/pyzy-0.1.0/src/BopomofoContext.cc:75
5 insert /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYPhoneticEditor.cc:267
6 PY::PhoneticEditor::insert /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYPhoneticEditor.cc:262
7 processBopomofo /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYBopomofoEditor.cc:144
8 processKeyEvent /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYBopomofoEditor.cc:169
9 processKeyEvent /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYBopomofoEngine.cc:118
10 _ibus_marshal_BOOLEAN__UINT_UINT_UINT /usr/lib64/libibus-1.0.so.5
/usr/src/debug/ibus-1.4.99.20121109/src/ibusmarshalers.c:296
11 closure_invoke_notifiers /usr/lib64/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gclosure.c:280
12 g_closure_invoke /usr/lib64/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gclosure.c:783
13 accumulate /usr/lib64/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gsignal.c:3052
14 signal_emit_unlocked_R /usr/lib64/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gsignal.c:3594
15 g_signal_emit_valist /usr/lib64/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gsignal.c:3312
16 g_signal_emit /usr/lib64/libgobject-2.0.so.0
/usr/src/debug/glib-2.32.4/gobject/gsignal.c:3358
17 ibus_engine_service_method_call /usr/lib64/libibus-1.0.so.5
/usr/src/debug/ibus-1.4.99.20121109/src/ibusengine.c:823
18 call_in_idle_cb /usr/lib64/libgio-2.0.so.0
/usr/src/debug/glib-2.32.4/gio/gdbusconnection.c:4698
19 g_main_dispatch /usr/lib64/libglib-2.0.so.0
/usr/src/debug/glib-2.32.4/glib/gmain.c:2539
20 g_main_context_dispatch /usr/lib64/libglib-2.0.so.0
/usr/src/debug/glib-2.32.4/glib/gmain.c:3075
21 g_main_context_iterate /usr/lib64/libglib-2.0.so.0
/usr/src/debug/glib-2.32.4/glib/gmain.c:3146
22 g_main_loop_run /usr/lib64/libglib-2.0.so.0
/usr/src/debug/glib-2.32.4/glib/gmain.c:3339
23 ibus_main /usr/lib64/libibus-1.0.so.5
/usr/src/debug/ibus-1.4.99.20121109/src/ibusshare.c:297
24 main /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYPointer.h:38
25 __libc_start_main /lib64/libc.so.6
/usr/src/debug/glibc-2.15-a316c1f/csu/libc-start.c:258
26 _start /usr/libexec/ibus-engine-pinyin
/usr/src/debug/ibus-pinyin-1.4.99.20120808/src/PYMain.cc:41
This ticket was created automatically. If this report is malformed or not
helpful
please let us know on crash-catcher(a)lists.fedorahosted.org so we can improve
it.
--
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=o6200sTij9&a=cc_unsubscribe
10 years, 11 months
[Fedora-i18n-bugs] [Bug 969727] New: [abrt] ibus-1.5.2-3.fc17: call_in_idle_cb: Process /usr/bin/ibus-daemon was killed by signal 6 (SIGABRT)
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=969727
Bug ID: 969727
Summary: [abrt] ibus-1.5.2-3.fc17: call_in_idle_cb: Process
/usr/bin/ibus-daemon was killed by signal 6 (SIGABRT)
Product: Fedora
Version: 17
Component: ibus
Severity: unspecified
Priority: unspecified
Assignee: tfujiwar(a)redhat.com
Reporter: gigalamer(a)wp.pl
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.2-3.fc17
Additional info:
backtrace_rating: 4
cmdline: /usr/bin/ibus-daemon -r --xim
crash_function: call_in_idle_cb
executable: /usr/bin/ibus-daemon
kernel: 3.8.13-100.fc17.x86_64
runlevel: unknown
uid: 1000
ureports_counter: 1
var_log_messages: Jun 2 04:29:26 solaris abrt[11513]: Saved core dump of pid
2670 (/usr/bin/ibus-daemon) to /var/spool/abrt/ccpp-2013-06-02-04:29:26-2670
(51462144 bytes)
Truncated backtrace:
Thread no. 1 (2 frames)
#4 call_in_idle_cb at gdbusconnection.c:4685
#9 bus_server_run at server.c:143
--
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=hzQgcYy019&a=cc_unsubscribe
10 years, 11 months
[Fedora-i18n-bugs] [Bug 834971] New: ibus-table key input limitation makes it hard to input Traditional Chinese with Quick and Cangjie
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=834971
Bug ID: 834971
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: rawhide
Priority: unspecified
CC: i18n-bugs(a)lists.fedoraproject.org, jni(a)redhat.com,
me(a)kaio.net, shawn.p.huang(a)gmail.com
Assignee: jni(a)redhat.com
Summary: ibus-table key input limitation makes it hard to input
Traditional Chinese with Quick and Cangjie
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: petersen(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: ibus-table
Product: Fedora
This was originally brought up by Mathieu Bridon and other Hong Kong Fedora
users. The text below is adopted from his mail.
Here's a proposal to fix IBus Table for Hong Kong users.
Both Cangjie and Quick can be used to type Simplified and Traditional
Chinese, however, given their design, there isn't any combination of keys that
would conflict between those languages. In other words, any given
combination of character can only lead to results in one of those
languages, never more than one.
Given all that, it would make sense to simply remove altogether the IBus
filter for the Cangjie and Quick input methods in IBus.
Let's take an example.
In Cangjie, the combination "rji" can only return results in Traditional
Chinese. That means if a user types this combination of keys, he is
expecting results in Traditional Chinese because that's the language
he/she wants to type.
But with the current IBus filter, if the filter is set to only let
Simplified Chinese characters pass, he/she would not get any results.
In the same way, the combination "yri" can only return results in
Simplified Chinese, and the combination "fji" can only return results in
Japanese.
[ed: I have never heard of people using ibus-table for Japanese input]
This is by design of those two input methods: they were designed to
avoid conflicts.
As such, the filter just makes no sense for Cangjie and Quick, and it
should be simply removed for those two input methods.
Now, in the above I claimed that Cangjie and Quick were designed to have
absolutely zero conflicts, which was a little exaggeration.
In reality, conflicts happen. However, Cangjie and Quick were really
designed with the goal of minimizing conflicts, and they do it so well
that the actual rate of conflicts is 8.04% [1]. This is such a small
number, and it happens in so rare occasions, that it can just be
ignored.
It is also important to note that if 90% of Hong Kong people [2] use
Cangjie and Quick, many people (but much less than in HK) use them in
Taiwan, and almost no one use them in Mainland China or in Japan.
Out of those three, Hong Kong and Taiwan write Traditional Chinese,
Mainland Chinese write Simplified Chinese, and Japanese obviously write
Japanese. So those two input methods really are used almost exclusively
to write Traditional Chinese, which makes the aforementioned 8.04%
figure completely negligible.
As such, it doesn't change the argument at all: the current IBus filter
should be removed for the Cangjie and Quick input methods.
This is an absolute show-stopper for Hong Kong users at the moment
(well, not me, I can't write Chinese , and the simple act of removing
this filter for those two input methods would basically fix 90% of the
problems for 90% of the Hong Kong people.
Do you think you guys could fix this issue before the release of GNOME
3.6?
Of course, we'd be happy to provide a patch if you agree on the solution
and if you can provide some guidance.
[1] There's a scientific paper published on this, but it's unfortunately
only available in Chinese:
http://zh.wikipedia.org/wiki/倉頡輸入法
[2] Not just Linux users, actual **people**, as this is how everyone
learns to type at school in Hong Kong.
--
You are receiving this mail because:
You are on the CC list for the bug.
10 years, 11 months
[Fedora-i18n-bugs] [Bug 961298] New: [hi_IN] Gnu free fonts rendering issues in gnome-shell
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=961298
Bug ID: 961298
Summary: [hi_IN] Gnu free fonts rendering issues in gnome-shell
Product: Fedora
Version: 19
Component: gnu-free-fonts
Keywords: i18n
Severity: unspecified
Priority: unspecified
Assignee: limburgher(a)gmail.com
Reporter: psatpute(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: aalam(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
limburgher(a)gmail.com, mclasen(a)redhat.com,
orion(a)cora.nwra.com, pnemade(a)redhat.com,
psatpute(a)redhat.com, tagoh(a)redhat.com
Depends On: 956192
Category: ---
+++ This bug was initially created as a clone of Bug #956192 +++
Description of problem:
Rendering of Text in Gnome-shell (and gedit) is broken. (May need to move bug
for harfbuzz or pango?). but working as expected with Search (with
gnome-shell), and Run dialog (Alt+f2)
example Text [क्रियाएँ]
Version-Release number of selected component (if applicable):
lohit-devanagari-fonts-2.5.3-2.fc19.noarch
gnu-free-sans-fonts-20120503-5.fc19.noarch
gnu-free-fonts-common-20120503-5.fc19.noarch
gnu-free-mono-fonts-20120503-5.fc19.noarch
gnu-free-serif-fonts-20120503-5.fc19.noarch
How reproducible:
Steps to Reproduce:
1. Login into Hindi Desktop
2. Check "Acitivies" Rendering
3. Copy (क्रियाएँ) Text
4. Paste in Gedit
5. Press Window (Super) Key and Paste Text in Search
6. Alt + F2 and paste Copied text
7. Run firefox and Paste copied text
Actual results:
Rendering is wrong in step 2 (gnome-shell), 4 (gedit),
Expected results:
Rendering is correct for Step 5, 6, 7
Additional info:
1. If remove gnu-free-* fonts from system, rendering is fine
2. Bug #918478 is already fixed, but still issue is there for Rendering.
Few more results from terminal on desktop
1.
-
LANG=hi_IN.utf8
LC_CTYPE="hi_IN.utf8"
LC_NUMERIC="hi_IN.utf8"
LC_TIME="hi_IN.utf8"
LC_COLLATE="hi_IN.utf8"
LC_MONETARY="hi_IN.utf8"
LC_MESSAGES="hi_IN.utf8"
LC_PAPER="hi_IN.utf8"
LC_NAME="hi_IN.utf8"
LC_ADDRESS="hi_IN.utf8"
LC_TELEPHONE="hi_IN.utf8"
LC_MEASUREMENT="hi_IN.utf8"
LC_IDENTIFICATION="hi_IN.utf8"
LC_ALL=
--
2
-
[hindi@lenovox230 ~]$ fc-match
Lohit-Devanagari.ttf: "Lohit Devanagari" "Regular"
[hindi@lenovox230 ~]$ fc-match :lang=hi
Lohit-Devanagari.ttf: "Lohit Devanagari" "Regular"
[hindi@lenovox230 ~]$ fc-match :lang=mr
Lohit-Devanagari.ttf: "Lohit Devanagari" "Regular"
---
--- Additional comment from Jon Ciesla on 2013-04-25 00:15:45 IST ---
If it's not occurring everywhere, I'm not convinced the bug is with the fonts,
but with something farther down. Could you attach a screenshot(s) with
examples?
--- Additional comment from A S Alam on 2013-04-25 08:00:05 IST ---
Created attachment 739642
Screenshot for Issue
Blue Underline - Rendering is Correct
Red Underline - Rendering has issue
(sorry for delay in screenshot)
--- Additional comment from Jon Ciesla on 2013-04-25 20:37:01 IST ---
Alright, based on that I'm guessing harfbuzz.
--- Additional comment from Jens Petersen on 2013-04-26 06:56:17 IST ---
Probably we should not be using GNU Free for Hindi then?
Alam: other Indic scripts/langs are not affected??
--- Additional comment from Jens Petersen on 2013-04-26 09:02:58 IST ---
Presumably switching gedit to Lohit Devanagari fixes the rendering there.
--- Additional comment from Jens Petersen on 2013-04-26 09:15:13 IST ---
(In reply to comment #5)
> Presumably switching gedit to Lohit Devanagari fixes the rendering there.
Actually doesn't seem to be any Preferences UI now in gedit.
--- Additional comment from Pravin Satpute on 2013-04-26 10:49:13 IST ---
Created attachment 740222
FreeSans rendering issues with Harfbuzz NG
This is problem with FreeSans rather than Harfbuzz. Please check text
"प्रविण सातपुते क्षत्रिय क्रियांये " with Lohit Devanagari for correct
rendering.
Its probem with Rakara feature, if time permits i will provide patch for this.
--- Additional comment from A S Alam on 2013-04-26 19:31:25 IST ---
(In reply to comment #4)
> Probably we should not be using GNU Free for Hindi then?
>
> Alam: other Indic scripts/langs are not affected??
I can confirm Punjabi (Gurmukhi) has issues, other Pravin can confirm.
--- Additional comment from A S Alam on 2013-04-26 23:22:14 IST ---
Created attachment 740561
pref for gedit
Please click (or right click) on gedit icon (which is close to Activities in
gnome-shell) and you can get preferences.
--- Additional comment from Akira TAGOH on 2013-05-02 12:52:36 IST ---
need to have similar recipe for FreeSans like this for FreeSerif:
http://pkgs.fedoraproject.org/cgit/gnu-free-fonts.git/commit/?id=a6e0de29...
--- Additional comment from Pravin Satpute on 2013-05-09 10:45:28 IST ---
Created attachment 745547
Modified lohit devanagari conf file
After modifying lohit fontconf now i am getting
$fc-match serif:lang=hi
$fc-match sans-serif:lang=hi
$fc-match monospace:lang=hi
But still gnome-shell "activities" showing me FreeSans in output. Just
wondering from where it is coming.
--- Additional comment from Pravin Satpute on 2013-05-09 16:50:17 IST ---
Created attachment 745617
screenshot showing gnu-free-sans getting selected in gnome-shell for hi
--- Additional comment from Pravin Satpute on 2013-05-09 16:51:34 IST ---
Created attachment 745621
expected output, gnome-shell should select lohit as a default font
--
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=Qlp6f2cekZ&a=cc_unsubscribe
10 years, 11 months
[Fedora-i18n-bugs] [Bug 971886] New: typo in georgian fontconfig file
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=971886
Bug ID: 971886
Summary: typo in georgian fontconfig file
Product: Fedora
Version: 19
Component: google-noto-fonts
Severity: unspecified
Priority: unspecified
Assignee: psatpute(a)redhat.com
Reporter: notting(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com
Description of problem:
On install:
Fontconfig error: "/etc/fonts/conf.d/66-google-noto-sans-georgian.conf", line
21: mismatched tag
That line says:
<family>Noto Serif Georgian/family>
instead of
<family>Noto Serif Georgian</family>
Version-Release number of selected component (if applicable):
google-noto-serif-georgian-fonts-20130411-3.fc19.noarch
How reproducible:
100%
Steps to Reproduce:
1. Install the georgian fonts
--
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=U1J3yNTM5d&a=cc_unsubscribe
10 years, 11 months
[Fedora-i18n-bugs] [Bug 627193] New: [Indic] [Mail] [HTML] Underline is printed as Strike for Indic Text
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: [Indic] [Mail] [HTML] Underline is printed as Strike for Indic Text
https://bugzilla.redhat.com/show_bug.cgi?id=627193
Summary: [Indic] [Mail] [HTML] Underline is printed as Strike
for Indic Text
Product: Fedora
Version: 13
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: evolution
AssignedTo: mbarnes(a)redhat.com
ReportedBy: aalam(a)redhat.com
QAContact: i18n-bugs(a)lists.fedoraproject.org
CC: mbarnes(a)redhat.com, mcrha(a)redhat.com,
cooly(a)gnome.eu.org
Classification: Fedora
Target Release: ---
Created attachment 440885
--> https://bugzilla.redhat.com/attachment.cgi?id=440885
Screenshot with problme in Hindi
Description of problem:
While printing a mail (even save as PDF) with Body has Underline Indic text,
printed as Strike. As you increase size of font, Striking line moved toward
middle of Word.
Version-Release number of selected component (if applicable):
evolution-2.30.2-4.fc13.x86_64
gtkhtml3-3.30.2-1.fc13.x86_64
How reproducible:
Everytime
Steps to Reproduce:
1. run evolution
2. New Mail - > HTML format
3. input Indic character (इराक़HINDI के कई शहरों मेंENGNLISH धमाके हुए हैं,
जिनमें 30 लोगों के मारे जाने और अन्य)
4. Select +3, +2, +1 Size
5. Select Underline
6. Print (as PDF or Hard copy)
Actual results:
Indic Characters has problem, while English Characters are ok with underline
Expected results:
Underline should under the characters
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
10 years, 11 months
[Fedora-i18n-bugs] [Bug 965914] New: "/usr/bin/fcitx4-config" of fcitx-libs are preventing install fcitx-libs.i686 with fcitx-libs.x86_64
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=965914
Bug ID: 965914
Summary: "/usr/bin/fcitx4-config" of fcitx-libs are preventing
install fcitx-libs.i686 with fcitx-libs.x86_64
Product: Fedora
Version: 18
Component: fcitx
Severity: medium
Priority: medium
Assignee: liangsuilong(a)gmail.com
Reporter: fge(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
liangsuilong(a)gmail.com, robinlee.sysu(a)gmail.com
Description of problem:
When trying to install fcitx-gtk2.i686 (with x86_64 rpm installed also), it
failed with these errors:
===
Transaction Check Error:
file /usr/bin/fcitx4-config from install of fcitx-libs-4.2.7-1.fc18.i686
conflicts with file from package fcitx-libs-4.2.7-1.fc18.x86_64
Error Summary
===
Version-Release number of selected component (if applicable):
fcitx-libs-4.2.7-1.fc18
How reproducible:
100%
Steps to Reproduce:
1. yum install -y fcitx-libs.i686 fcitx-libs.x86_64
2.
3.
Actual results:
yum failed with conflicting file.
Expected results:
i686 rpm could installed aside with x86_64
Additional info:
/usr/bin/fcitx4-config is just shell script, try store it in fcitx rpm or new
rpm.
--
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=DROSyF5IEF&a=cc_unsubscribe
10 years, 11 months