[Fedora-i18n-bugs] [Bug 629872] New: imsettings sometimes failed to run ibus
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: imsettings sometimes failed to run ibus
https://bugzilla.redhat.com/show_bug.cgi?id=629872
Summary: imsettings sometimes failed to run ibus
Product: Fedora
Version: 13
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: tfujiwar(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Target Release: ---
It seems imsettings sometimes failed to run ibus-daemon with timeout when I
change the login languages (maybe user-dirs-update-gtk effects).
Having a timeout option for imsettings-start might be good.
The default timeout would be 2.5 sec.
The test case works good with me:
--- imsettings-0.108.1/imsettings/imsettings-request.c.orig
+++ imsettings-0.108.1/imsettings/imsettings-request.c
@@ -29,6 +29,11 @@
#include <glib/gi18n-lib.h>
#include <dbus/dbus-glib-lowlevel.h>
#include <dbus/dbus-glib-bindings.h>
+
+#ifdef HAVE_LOCALE_H
+#include <locale.h>
+#endif
+
#include "imsettings-request.h"
#include "imsettings.h"
#include "imsettings-utils.h"
@@ -236,10 +241,19 @@ imsettings_request_get_version(IMSetting
g_return_val_if_fail (IMSETTINGS_IS_REQUEST (imsettings), 0);
priv = IMSETTINGS_REQUEST_GET_PRIVATE (imsettings);
+#if 0
if (!dbus_g_proxy_call(priv->proxy, "GetVersion", &err,
G_TYPE_INVALID,
G_TYPE_UINT, &retval,
G_TYPE_INVALID))
+#else
+ if (!dbus_g_proxy_call_with_timeout (priv->proxy, "GetVersion",
+ 60000,
+ &err,
+ G_TYPE_INVALID,
+ G_TYPE_UINT, &retval,
+ G_TYPE_INVALID))
+#endif
g_warning(_("Failed to invoke a method `%s' on %s:\n %s"),
"GetVersion",
dbus_g_proxy_get_interface(priv->proxy),
@@ -317,7 +331,11 @@ imsettings_request_get_info_object(IMSet
IMSettingsInfo *retval = NULL;
GValueArray *ret = NULL;
GError *err = NULL;
+#ifdef HAVE_LOCALE_H
const gchar *locale = setlocale(LC_CTYPE, NULL);
+#else
+ const gchar *locale = NULL;
+#endif
g_return_val_if_fail (IMSETTINGS_IS_REQUEST (imsettings), NULL);
--
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.
13 years, 4 months
[Fedora-i18n-bugs] [Bug 628420] New: move none state from checkbox to selector
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: move none state from checkbox to selector
https://bugzilla.redhat.com/show_bug.cgi?id=628420
Summary: move none state from checkbox to selector
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: im-chooser
AssignedTo: tagoh(a)redhat.com
ReportedBy: petersen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Target Release: ---
Description of problem:
Now that we have 3 states by default in Fedora (none, ibus and xcompose)
I feel it would be simpler to drop the checkbox and move none
into the selector.
- No input method
- ibus
- X compose
(The order might depend on the defaults;)
Probably need a tooltip (or better an info box?)
with more explanation for each one.
--
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.
13 years, 4 months
[Fedora-i18n-bugs] [Bug 607502] New: Window title
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: Window title
https://bugzilla.redhat.com/show_bug.cgi?id=607502
Summary: Window title
Product: Fedora
Version: 13
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: im-chooser
AssignedTo: tagoh(a)redhat.com
ReportedBy: michael.monreal+bugs(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
The im-chooser window currently displays "IM Chooser - Input Method confi"
a) the title is cut off and the window cannot be resized
b) the window should not show branding ("IM Chooser")
c) the window title should be the same as used the .desktop launcher (=> "Input
Method" or, as a control center module "Input Method Preferences"
--
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.
13 years, 4 months
[Fedora-i18n-bugs] [Bug 596900] New: Position of changing lines needs improving in ja_JP.UTF-8
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: Position of changing lines needs improving in ja_JP.UTF-8
https://bugzilla.redhat.com/show_bug.cgi?id=596900
Summary: Position of changing lines needs improving in
ja_JP.UTF-8
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: man-db
AssignedTo: varekova(a)redhat.com
ReportedBy: mtasaka(a)ioa.s.u-tokyo.ac.jp
QAContact: extras-qa(a)fedoraproject.org
CC: varekova(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Created an attachment (id=417335)
--> (https://bugzilla.redhat.com/attachment.cgi?id=417335)
screenshot of fprintf(3) with both man-db and man
Description of problem:
See screenshot:
With man-db, when trying to see Japanese man page fprintf(3)
if some long line exists such line is split on unexpected positions
and as the result fprintf(3) manual page cannot be seen easily
with man-db.
With man (in F-13) long lines are split on expected positions.
Version-Release number of selected component (if applicable):
man-db-2.5.7-2.fc14.i686
How reproducible:
100%
Steps to Reproduce:
1. install man-pages-ja
2. man fprintf in LANG=ja_JP.UTF-8
3.
Actual results:
See screenshot
Expected results:
New line should begin at expected positions like in F-13 man
--
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.
13 years, 4 months
[Fedora-i18n-bugs] [Bug 569063] New: Ibus language bar remains visible even if IM is deactivated
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: Ibus language bar remains visible even if IM is deactivated
https://bugzilla.redhat.com/show_bug.cgi?id=569063
Summary: Ibus language bar remains visible even if IM is
deactivated
Product: Fedora
Version: 12
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ibus
AssignedTo: phuang(a)redhat.com
ReportedBy: dekacy10(a)hotmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Created an attachment (id=396789)
--> (https://bugzilla.redhat.com/attachment.cgi?id=396789)
Bar shadow displayed over a video
Description of problem:
The bar iBus displays when activated remains visible even when I deactivate the
input method. More specifically, a semi-transparent version of it. This is a
problem, especially when the user is trying to read or watch something
displayed in that area.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Install and enable ibus
2. turn on and then off an input methode
3. switch window
Actual results:
A semi-transparent shadow of the bar remains. Not clickable or anything.
Expected results:
Language bar disappears completely.
Additional info:
I have Metacity's composition feature on.
--
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.
13 years, 4 months
[Fedora-i18n-bugs] [Bug 517635] New: [ne_NP] fc-match showing "Lohit Hindi" instead of current Language
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: [ne_NP] fc-match showing "Lohit Hindi" instead of current Language
https://bugzilla.redhat.com/show_bug.cgi?id=517635
Summary: [ne_NP] fc-match showing "Lohit Hindi" instead of
current Language
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: lohit-fonts
AssignedTo: psatpute(a)redhat.com
ReportedBy: aalam(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, pnemade(a)redhat.com,
fedora-fonts-bugs-list(a)redhat.com,
psatpute(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
in Nepali Envirnment (gnome-desktop), fc-match is showing following informating
---
$echo $LANG
ne_NP.UTF-8
$fc-match
lohit_hi.ttf: "Lohit Hindi" "Regular"
---
Version-Release number of selected component (if applicable):
lohit-nepali-fonts-2.4.0-2.fc12
How reproducible:
100%
Steps to Reproduce:
1. login to Gnome-desktop with Nepali Language
2. open gnome-terminal
3. type 'fc-match'
Actual results:
lohit_hi.ttf: "Lohit Hindi" "Regular"
Expected results:
lohit_ne.ttf: "Lohit Nepali" "Regular" or something for Nepali
Additional info:
I have file /usr/share/fonts/lohit/lohit_ne.tff on system
--
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.
13 years, 5 months
[Fedora-i18n-bugs] [Bug 518161] New: "contains" expression seems not working on the fontconfig rule
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: "contains" expression seems not working on the fontconfig rule
https://bugzilla.redhat.com/show_bug.cgi?id=518161
Summary: "contains" expression seems not working on the
fontconfig rule
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: fontconfig
AssignedTo: besfahbo(a)redhat.com
ReportedBy: tagoh(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: besfahbo(a)redhat.com, pnemade(a)redhat.com,
fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Created an attachment (id=357904)
--> (https://bugzilla.redhat.com/attachment.cgi?id=357904)
sample fontconfig rule
Description of problem:
Even if the pattern contains strings that the rule specifies with "contains"
expression, it doesn't match.
Version-Release number of selected component (if applicable):
fontconfig-2.7.1-1.fc12
How reproducible:
always
Steps to Reproduce:
1.install lohit-hindi-fonts and lohit-marathi-fonts
2.put the attached rule into /etc/fonts/conf.d
3.fc-match "sans-serif:lang=mr"
4.fc-match "sans-serif:lang=mr-in"
Actual results:
3. lohit_mr.ttf: "Lohit Marathi" "Regular"
4. lohit_hi.ttf: "Lohit Hindi" "Regular"
Expected results:
the result of 3 and 4 should be:
lohit_mr.ttf: "Lohit Marathi" "Regular"
Additional info:
>From a debug log:
FcConfigSubstitute test pattern any lang Contains "mr"
FcLangSet mr-in contains mr
Missing bitmap ku-am
No match
I'm not really sure why fontconfig refers ku-am map here but apparently it
looks like fontconfig doesn't know what mr-in is.
Anyway, if no explicit lang pattern is given and applications calls
FcDefaultSubstitute(), lang will be set like mr-in from current locale
mr_IN.UTF-8 say.
--
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.
13 years, 5 months
[Fedora-i18n-bugs] [Bug 633069] New: [abrt] ibus-1.3.6-1.fc12: __init__.py:40:<module>:ImportError: /usr/lib/libXi.so.6: undefined symbol: XESetWireToEventCookie
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: [abrt] ibus-1.3.6-1.fc12: __init__.py:40:<module>:ImportError: /usr/lib/libXi.so.6: undefined symbol: XESetWireToEventCookie
https://bugzilla.redhat.com/show_bug.cgi?id=633069
Summary: [abrt] ibus-1.3.6-1.fc12:
__init__.py:40:<module>:ImportError:
/usr/lib/libXi.so.6: undefined symbol:
XESetWireToEventCookie
Product: Fedora
Version: 12
Platform: i686
OS/Version: Linux
Status: NEW
Status Whiteboard: abrt_hash:3714acd3
Severity: medium
Priority: low
Component: ibus
AssignedTo: tfujiwar(a)redhat.com
ReportedBy: matteo.pasotti(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
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: python /usr/share/ibus/ui/gtk/main.py
component: ibus
executable: /usr/share/ibus/ui/gtk/main.py
kernel: 2.6.32.21-166.fc12.i686.PAE
package: ibus-1.3.6-1.fc12
reason: __init__.py:40:<module>:ImportError: /usr/lib/libXi.so.6: undefined
symbol: XESetWireToEventCookie
release: Fedora release 12 (Constantine)
time: 1284128343
uid: 500
--
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.
13 years, 5 months
[Fedora-i18n-bugs] [Bug 636216] New: Switching korean layout in IBusHangul Setup > ibus-hangul crashes
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: Switching korean layout in IBusHangul Setup > ibus-hangul crashes
https://bugzilla.redhat.com/show_bug.cgi?id=636216
Summary: Switching korean layout in IBusHangul Setup >
ibus-hangul crashes
Product: Fedora
Version: 14
Platform: All
OS/Version: Linux
Status: NEW
Severity: high
Priority: low
Component: ibus-hangul
AssignedTo: dueno(a)redhat.com
ReportedBy: sangu.fedora(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, dueno(a)redhat.com,
pwu(a)redhat.com, shawn.p.huang(a)gmail.com
Classification: Fedora
Description of problem:
Switching korean layout in IBusHangul Setup > ibus-hangul crashes
$ dmesg
[...]
ibus-engine-han[2277] general protection ip:7f6b43c62aaf sp:7fff278f26d8
error:0 in libhangul.so.0.1.2[7f6b43c5e000+c000]
$ gdb /usr/libexec/ibus-engine-hangul coredump
Core was generated by `/usr/libexec/ibus-engine-hangul --ibus'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f6b43c62aaf in hangul_ic_select_keyboard ()
from /usr/lib64/libhangul.so.0
(gdb) bt
#0 0x00007f6b43c62aaf in hangul_ic_select_keyboard ()
from /usr/lib64/libhangul.so.0
#1 0x00007f6b4458d0ee in g_closure_invoke (closure=0x91d790,
return_value=0x0, n_param_values=4, param_values=0x8eccc0,
invocation_hint=0x7fff278f2820) at gclosure.c:766
#2 0x00007f6b4459eb7a in signal_emit_unlocked_R (node=<value optimized out>,
detail=0, instance=0x8eae00, emission_return=0x0,
instance_and_params=0x8eccc0) at gsignal.c:3252
#3 0x00007f6b445a86ba in g_signal_emit_valist (
instance=<value optimized out>, signal_id=<value optimized out>,
detail=<value optimized out>, var_args=0x7fff278f2a10) at gsignal.c:2983
#4 0x00007f6b445a8863 in g_signal_emit (instance=<value optimized out>,
signal_id=<value optimized out>, detail=<value optimized out>)
at gsignal.c:3040
#5 0x00007f6b447eea54 in ibus_config_ibus_signal (
proxy=<value optimized out>, message=0x9081a0) at ibusconfig.c:200
#6 0x00007f6b447f9f98 in ibus_marshal_BOOLEAN__POINTER (closure=0x8f5570,
return_value=0x7fff278f2e70, n_param_values=<value optimized out>,
param_values=0x9228f0, invocation_hint=<value optimized out>,
marshal_data=<value optimized out>) at ibusmarshalers.c:167
#7 0x00007f6b4458d0ee in g_closure_invoke (closure=0x8f5570,
return_value=0x7fff278f2e70, n_param_values=2, param_values=0x9228f0,
invocation_hint=0x7fff278f2ce0) at gclosure.c:766
---Type <return> to continue, or q <return> to quit---
#8 0x00007f6b4459e97b in signal_emit_unlocked_R (node=<value optimized out>,
detail=0, instance=0x8eae00, emission_return=0x7fff278f2e70,
instance_and_params=0x9228f0) at gsignal.c:3290
#9 0x00007f6b445a850e in g_signal_emit_valist (
instance=<value optimized out>, signal_id=<value optimized out>,
detail=<value optimized out>, var_args=0x7fff278f2ed0) at gsignal.c:2993
#10 0x00007f6b445a8863 in g_signal_emit (instance=<value optimized out>,
signal_id=<value optimized out>, detail=<value optimized out>)
at gsignal.c:3040
#11 0x00007f6b447e3d90 in ibus_proxy_handle_signal (proxy=0x8eae00,
message=0x9081a0) at ibusproxy.c:490
#12 0x00007f6b447e3e9b in _connection_ibus_signal_cb (connection=0x8ef400,
message=0x9081a0, proxy=0x8eae00) at ibusproxy.c:202
#13 0x00007f6b447f9f98 in ibus_marshal_BOOLEAN__POINTER (closure=0x8f9670,
return_value=0x7fff278f3350, n_param_values=<value optimized out>,
param_values=0x922cc0, invocation_hint=<value optimized out>,
marshal_data=<value optimized out>) at ibusmarshalers.c:167
#14 0x00007f6b4458d0ee in g_closure_invoke (closure=0x8f9670,
return_value=0x7fff278f3350, n_param_values=2, param_values=0x922cc0,
invocation_hint=0x7fff278f31c0) at gclosure.c:766
#15 0x00007f6b4459eb7a in signal_emit_unlocked_R (node=<value optimized out>,
detail=0, instance=0x8ef400, emission_return=0x7fff278f3350,
instance_and_params=0x922cc0) at gsignal.c:3252
---Type <return> to continue, or q <return> to quit---
#16 0x00007f6b445a850e in g_signal_emit_valist (
instance=<value optimized out>, signal_id=<value optimized out>,
detail=<value optimized out>, var_args=0x7fff278f33b0) at gsignal.c:2993
#17 0x00007f6b445a8863 in g_signal_emit (instance=<value optimized out>,
signal_id=<value optimized out>, detail=<value optimized out>)
at gsignal.c:3040
#18 0x00007f6b447e122a in ibus_connection_ibus_message (connection=0x8ef400,
message=0x9081a0) at ibusconnection.c:258
#19 0x00007f6b447f9f98 in ibus_marshal_BOOLEAN__POINTER (closure=0x8e73c0,
return_value=0x7fff278f37c0, n_param_values=<value optimized out>,
param_values=0x922c90, invocation_hint=<value optimized out>,
marshal_data=<value optimized out>) at ibusmarshalers.c:167
#20 0x00007f6b4458d0ee in g_closure_invoke (closure=0x8e73c0,
return_value=0x7fff278f37c0, n_param_values=2, param_values=0x922c90,
invocation_hint=0x7fff278f3630) at gclosure.c:766
#21 0x00007f6b4459e97b in signal_emit_unlocked_R (node=<value optimized out>,
detail=0, instance=0x8ef400, emission_return=0x7fff278f37c0,
instance_and_params=0x922c90) at gsignal.c:3290
#22 0x00007f6b445a850e in g_signal_emit_valist (
instance=<value optimized out>, signal_id=<value optimized out>,
detail=<value optimized out>, var_args=0x7fff278f3820) at gsignal.c:2993
#23 0x00007f6b445a8863 in g_signal_emit (instance=<value optimized out>,
signal_id=<value optimized out>, detail=<value optimized out>)
---Type <return> to continue, or q <return> to quit---
at gsignal.c:3040
#24 0x00007f6b447e0ec6 in _connection_handle_message_cb (
dbus_connection=<value optimized out>, message=<value optimized out>,
connection=<value optimized out>) at ibusconnection.c:304
#25 0x00007f6b42c19b8c in dbus_connection_dispatch ()
from /lib64/libdbus-1.so.3
#26 0x00007f6b447df215 in message_queue_dispatch (
source=<value optimized out>, callback=<value optimized out>,
user_data=<value optimized out>) at ibusinternal.c:80
#27 0x00007f6b43eae233 in g_main_dispatch (context=0x8ef010) at gmain.c:2119
#28 g_main_context_dispatch (context=0x8ef010) at gmain.c:2672
#29 0x00007f6b43eaea10 in g_main_context_iterate (context=0x8ef010, block=1,
dispatch=1, self=<value optimized out>) at gmain.c:2750
#30 0x00007f6b43eaf082 in g_main_loop_run (loop=0x8fa420) at gmain.c:2958
#31 0x00007f6b447dea9c in ibus_main () at ibusshare.c:297
#32 0x0000000000402b75 in start_component (argc=1, argv=0x7fff278f3c18)
at main.c:82
#33 main (argc=1, argv=0x7fff278f3c18) at main.c:108
Version-Release number of selected component (if applicable):
1.3.0.20100329-3.fc14.x86_64
How reproducible:
always
Steps to Reproduce:
1. Switch Korean layout ( 2bul -> 3bul )
2.
3.
Actual results:
Expected results:
Additional info:
ibus-1.3.7-5.fc14.x86_64
glib2-2.25.15-1.fc14.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.
13 years, 5 months
[Fedora-i18n-bugs] [Bug 545349] New: [ml_IN] Wrong rendering when യ്യ and വ്വ used with chillu conjuncts
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: [ml_IN] Wrong rendering when യ്യ and വ്വ used with chillu conjuncts
https://bugzilla.redhat.com/show_bug.cgi?id=545349
Summary: [ml_IN] Wrong rendering when യ്യ and വ്വ used with
chillu conjuncts
Product: Fedora
Version: 12
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: qt
AssignedTo: than(a)redhat.com
ReportedBy: apeter(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: rdieter(a)math.unl.edu, than(a)redhat.com,
kevin(a)tigcc.ticalc.org, ltinkl(a)redhat.com,
smc-discuss(a)googlegroups.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Created an attachment (id=376865)
--> (https://bugzilla.redhat.com/attachment.cgi?id=376865)
Screenshot for kwrite showing wrong rendering
Description of problem:
Conjunct "യ്യ" and "വ്വ" when used after chillu conjuncts, it gets combined
with the chillu resulting in wrong rendering. ie,
Conjunct യ്യ = യ + ് + യ [ 0D2F + 0D4D + 0D2F ] and
Conjunct വ്വ = വ + ് + വ [ 0D35 + 0D4D + 0D35 ]
Also,
When any consonant is combined with 0D2F or 0D35 using 0D4D, gives the
following result (Here, consonant ക [0D15] is used) :
ക + ് + യ = ക്യ [ 0D15 + 0D4D + 0D2F ]
ക + ് + വ = ക്വ [ 0D15 + 0D4D + 0D35 ]
Thus, when conjunct യ്യ or വ്വ is used after any chillu conjuncts, say ന്, the
first 0D2F/0D35 is getting combined with ന് and giving out wrong results.
Version-Release number of selected component (if applicable):
qt-4.5.3-9.fc12
kdebase-4.3.3-3.fc12
How reproducible:
Always
Steps to Reproduce:
(i) For Conjunct "യ്യ"
1. Open kwrite
2. Type 0D28, 0D4D, 200D, 0D2F, 0D4D, 0D2F
(ii) For Conjunct "വ്വ"
1. Open kwrite
2. Type 0D28, 0D4D, 200D, 0D35, 0D4D, 0D35
Observe the wrong rendering for above combination.
Actual results:
When conjunct "യ്യ" and "വ്വ" is used after chillu, they get combined with the
chillu and is thus wrong rendering. Attached screenshot with kwrite showing
this wrong rendering.
Expected results:
When conjunct "യ്യ" and "വ്വ" is used after chillu, they must not get combined
with the chillu. Attached screenshot with gedit showing correct rendering.
Additional info:
5 Chillu conjuncts are:
ന് = ന + ് + ZWJ [ 0D28 + 0D4D + 200D ]
ര് = ര + ് + ZWJ [ 0D30 + 0D4D + 200D ]
ണ് = ണ + ് + ZWJ [ 0D23 + 0D4D + 200D ]
ള് = ള + ് + ZWJ [ 0D33 + 0D4D + 200D ]
ല് = ല + ് + ZWJ [ 0D32 + 0D4D + 200D ]
--
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.
13 years, 5 months