[Fedora-i18n-bugs] [Bug 514110] New: [ta_IN] Tamil collation rules are not working in other locales
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: [ta_IN] Tamil collation rules are not working in other locales
https://bugzilla.redhat.com/show_bug.cgi?id=514110
Summary: [ta_IN] Tamil collation rules are not working in other
locales
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: glibc
AssignedTo: schwab(a)redhat.com
ReportedBy: psatpute(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: jakub(a)redhat.com, santhosh.thottingal(a)gmail.com,
fedora-i18n-bugs(a)redhat.com, schwab(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
ta_IN collation rules are not working, when we select other locale say
en_US.UTF-8
Version-Release number of selected component (if applicable):
glibc-common-2.10.90-7.1
How reproducible:
every time
Steps to Reproduce:
1. select en_US locale
2. try to sort Tamil characters
3.
Actual results:
sorting is not working
Expected results:
It should be sorted as per collation rule
Additional info:
This is happening due to ta_IN collation rules written in ta_IN locale file,
and these rules are not available to outside locale.
We should move these collation table to iso14651_t1_common(common to most of
the locale), so it will be available to other locale as well and tamil sorting
will work while selecting any locale
--
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.
11 years, 7 months
[Fedora-i18n-bugs] [Bug 591554] New: Font artifact with number 4
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: Font artifact with number 4
https://bugzilla.redhat.com/show_bug.cgi?id=591554
Summary: Font artifact with number 4
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: liberation-fonts
AssignedTo: cchance(a)redhat.com
ReportedBy: cchance(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, cchance(a)redhat.com,
fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Target Release: ---
Description of problem:
(Quoted from calumlind)
I have this issue with Liberation Sans font when used with Docky:
http://imagebin.org/95732
I have checked that this occurs with Sans, Mono and very slightly with
Serif on two different Ubuntu Lucid computers.
It seems to be related to the inner triangle of the 4 because as you
increase the icon size to 128 in Docky the artefact does not grow but you
can still faintly see it behind the number: http://imagebin.org/95870
I already posted a bug report with Docky but they did not think it is a
problem they can fix: https://bugs.launchpad.net/docky/+bug/575807
--
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.
11 years, 8 months
[Fedora-i18n-bugs] [Bug 486272] New: toolbar focus problems
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: toolbar focus problems
https://bugzilla.redhat.com/show_bug.cgi?id=486272
Summary: toolbar focus problems
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ibus
AssignedTo: phuang(a)redhat.com
ReportedBy: mclasen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
The toolbar seems useless if "focus-follows-mouse" is turned on, since
it becomes inactive on focus out. This also affects the status icon.
By focus-follows-mouse, I mean the "Select windows when the mouse moves
over them" option in the "Windows" capplet. If you turn that on, and
move the move from the window you are working in towards the toolbar or
statusicon, the window looses focus and the status icon/toolbar turn
inactive, so you can't do whatever you wanted to there in the first
place...
--
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.
11 years, 9 months
[Fedora-i18n-bugs] [Bug 486279] New: ibus preferences ui improvements, part 2
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 preferences ui improvements, part 2
https://bugzilla.redhat.com/show_bug.cgi?id=486279
Summary: ibus preferences ui improvements, part 2
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ibus
AssignedTo: phuang(a)redhat.com
ReportedBy: mclasen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Keyboard shortcuts: I would love to see these moved to the keyboard
shortcuts capplet, which has support for handling application-defined
shortcuts. As a bonus, you get automatic conflict handling. The one
restriction is that currently, only one key-combination per action is
possible. If having multiple is essential, you could either split it
into "Trigger", "Alternative Trigger", "Second Alternative Trigger", or
file a bug and I'll look into enabling multiple shortcuts per action in
the keybinding capplet
--
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.
11 years, 9 months
[Fedora-i18n-bugs] [Bug 477690] New: libchewing multilib conflict
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: libchewing multilib conflict
https://bugzilla.redhat.com/show_bug.cgi?id=477690
Summary: libchewing multilib conflict
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: libchewing
AssignedTo: dchen(a)redhat.com
ReportedBy: phil(a)fifi.org
QAContact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
yum install libchewing.i386 libchewing.x86_64
yeilds:
file /usr/share/chewing/fonetree.dat from install of
libchewing-0.3.2-0.fc10.i386 conflicts with file from package
libchewing-0.3.2-0.fc10.x86_64
Version-Release number of selected component (if applicable):
libchewing-0.3.2-0.fc10
--
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.
11 years, 9 months
[Fedora-i18n-bugs] [Bug 517789] New: Droid Sans overrides default Japanese desktop font
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: Droid Sans overrides default Japanese desktop font
https://bugzilla.redhat.com/show_bug.cgi?id=517789
Summary: Droid Sans overrides default Japanese desktop font
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: google-droid-fonts
AssignedTo: nicolas.mailhot(a)laposte.net
ReportedBy: petersen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: nicolas.mailhot(a)laposte.net,
fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
I was just testing a f12alpha spin and discovered that Droid Sans
seems to override the default Japanese desktop font.
How reproducible:
every time
Steps to Reproduce:
1. yum install google-droid-sans-fonts
2. login to gnome desktop
3. run gucharmap
Actual results:
Most kanji glyphs are shown with Droid Sans.
Expected results:
Default Japanese IPA font to be used for Japanese characters.
Additional info:
Not sure why the Droid fonts were pulled into the spin.
This affects whole Japanese desktop and gdm, etc.
--
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.
11 years, 9 months
[Fedora-i18n-bugs] [Bug 528140] New: [hi_IN][ta_IN] TimeZone in Clock is Boston by default
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: [hi_IN][ta_IN] TimeZone in Clock is Boston by default
https://bugzilla.redhat.com/show_bug.cgi?id=528140
Summary: [hi_IN][ta_IN] TimeZone in Clock is Boston by default
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: gnome-panel
AssignedTo: rstrode(a)redhat.com
ReportedBy: aalam(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: rstrode(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Created an attachment (id=364235)
--> (https://bugzilla.redhat.com/attachment.cgi?id=364235)
Screenshot for s-c-date and gnome-clock
Description of problem:
After installation and setting Default Timezone Kolkata, Clock is showing
Default Timezone (added by Default) Boston (after Fresh installation).
Version-Release number of selected component (if applicable):
gnome-panel-2.28.0-2.fc12.x86_64
system-config-date-1.9.52-1.fc12.noarch
libgweather-2.28.0-1.fc12.x86_64
How reproducible:
Everytime
Steps to Reproduce:
1. fresh install with Hindi (hi_IN) locale
2. login with Hindi
3. Click on clock/Task Top-Right Side
Actual results:
Boston is added by Default
Expected results:
Either should be default for locale or s-c-date's Zone
Additional info:
Screenshot
--
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.
11 years, 9 months
[Fedora-i18n-bugs] [Bug 700971] New: [ru_RU] Not displayed Russian symbols in console again
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: [ru_RU] Not displayed Russian symbols in console again
https://bugzilla.redhat.com/show_bug.cgi?id=700971
Summary: [ru_RU] Not displayed Russian symbols in console again
Product: Fedora
Version: 15
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Keywords: i18n
Severity: unspecified
Priority: unspecified
Component: dracut
AssignedTo: harald(a)redhat.com
ReportedBy: lpoetter(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: notting(a)redhat.com, harald(a)redhat.com,
rstrode(a)redhat.com, aalam(a)redhat.com, atigro(a)ya.ru,
mschmidt(a)redhat.com, vcrhonek(a)redhat.com,
jonathan(a)jonmasters.org, lpoetter(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org,
plautrba(a)redhat.com, iarlyy(a)gmail.com,
elemc(a)atisserv.ru, metherid(a)gmail.com,
johannbg(a)gmail.com
Depends on: 699282
Classification: Fedora
Story Points: ---
Clone Of: 699282
+++ This bug was initially created as a clone of Bug #699282 +++
Description of problem:
After system boot up, I've switched to console (Ctrl-Alt-F2), login and run mc
(Midnight Commander) or another application with Russian symbols.
Russian symbols not displayed, again. Like this was in Fedora 12.
Version-Release number of selected component (if applicable):
initscripts-9.29
How reproducible:
always
Steps to Reproduce:
1. Boot system
2. switch to console
3. run application with Russian symbols, as example LANG=ru_RU.UTF-8 mc
Actual results:
White squares instead Russian symbols.
Expected results:
Russian symbols displayed correctly.
Additional info:
I've find workaround or patch.
If I change this line in /lib/udev/rules.d/10-console.rules:
KERNEL=="tty0",><------>RUN+="/lib/udev/console_init %k"
like this:
KERNEL=="tty*",><------>RUN+="/lib/udev/console_init %k"
then Russian symbols displayed correctly.
--- Additional comment from atigro(a)ya.ru on 2011-04-24 23:34:08 CEST ---
In earlier dracut (in F14) initramfs image contained system binary
/lib/udev/console_init from initscripts. Maybe it is the second way to fix this
problem:
https://github.com/RussianFedora/dracut/blob/f15%2Ffixes/dracut-009-conso...
--- Additional comment from lpoetter(a)redhat.com on 2011-04-27 02:30:00 CEST ---
systemd-vconsole should be responsible for setting that up.
Does invoking /lib/systemd/systemd-vconsole-setup manually make things work for
you?
What is the content of /etc/sysconfig/i18n?
--- Additional comment from elemc(a)atisserv.ru on 2011-04-27 19:59:39 CEST ---
Yes, after run /lib/systemd/systemd-vconsole-setup in console Russian symbols
displayed correctly.
cat /etc/sysconfig/i18n
LANG="ru_RU.UTF-8"
--- Additional comment from lpoetter(a)redhat.com on 2011-04-28 00:39:26 CEST ---
Which systemd version is this?
Normally /lib/systemd/systemd-vconsole-setup should run at boot.
Can you do "systemctl --full | grep vconsole" after boot when the problem
happened and paste the output here?
--- Additional comment from elemc(a)atisserv.ru on 2011-04-28 08:31:27 CEST ---
# yum list installed systemd*
systemd.x86_64 25-1.fc15 @updates-testing
systemd-units.x86_64 25-1.fc15 @updates-testing
I've booted and checked what problem still persist.
# systemctl --full | grep vconsole
systemd-vconsole-setup.service loaded active exited Setup Virtual
Console
--- Additional comment from mschmidt(a)redhat.com on 2011-04-28 10:52:30 CEST ---
Can you boot with "rd.plymouth=0"? Do the fonts appear correctly then?
--- Additional comment from elemc(a)atisserv.ru on 2011-04-28 11:05:39 CEST ---
Yes, with rd.plymouth=0 kernel parameter the fonts appear correctly.
--- Additional comment from lpoetter(a)redhat.com on 2011-04-28 16:54:36 CEST ---
Hmm, Ray, have you heard of such a problem with font loading and Plymouth
colliding?
--- Additional comment from lpoetter(a)redhat.com on 2011-04-28 16:59:20 CEST ---
OK, my guess is that this might be related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172/comments/245
i.e. setfont should probably retry opening /dev/tty0 a couple of times.
--- Additional comment from lpoetter(a)redhat.com on 2011-04-28 17:06:38 CEST ---
Tentatively reassigning this to kbd. The EIO loop is definitely necessary in
kbd. It might fix this problem. If it doesn't feel free to reassign back.
kbd maintainers, can you please beef up open_a_console() in src/getf_fd.c to
loop a couple of times if you get EIO when opening the device? Since the BKL
was dropped in the kernel this is unfortunately necessary in userspace to make
things work race-freely, see the linked ubuntu bug.
We do a similar loop in systemd:
http://cgit.freedesktop.org/systemd/tree/src/util.c#n2326
--- Additional comment from notting(a)redhat.com on 2011-04-28 18:38:23 CEST ---
(In reply to comment #8)
> Hmm, Ray, have you heard of such a problem with font loading and Plymouth
> colliding?
vconsole setup needs done before plymouth sets the terminal to graphics
mode/the framebuffer driver is loaded, IIRC.
(font/unicode state is per-VT, but inherited from the prior existing console)
--- Additional comment from lpoetter(a)redhat.com on 2011-04-30 03:45:44 CEST ---
OK, will duplicate against dracut then, which apparently dropped the font
loading.
Harald, please add an invocation of systemd-vconsole-setup to dracut, before
you run plymouth, as discussed on IRC the other day.
--
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.
11 years, 10 months
[Fedora-i18n-bugs] [Bug 696476] New: [bn][bn-IN]Combinations with Consonant+09CB+special characters fail on Openoffice.org writer
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: [bn][bn-IN]Combinations with Consonant+09CB+special characters fail on Openoffice.org writer
https://bugzilla.redhat.com/show_bug.cgi?id=696476
Summary: [bn][bn-IN]Combinations with Consonant+09CB+special
characters fail on Openoffice.org writer
Product: Fedora
Version: 14
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: ibus
AssignedTo: tfujiwar(a)redhat.com
ReportedBy: runab(a)redhat.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
Story Points: ---
Description of problem:
Combinations with various Bengali consonant characters (0995-09B9)+09CB+special
characters (0981-0983) cause Openoffice.org writer to crash unexpectedly, after
ibus, ibus-libs, ibus-gtk2, ibus-gtk3 packages are updated.
Version-Release number of selected component (if applicable):
openoffice.org-writer-3.3.0-9.3.fc14
ibus-libs-1.3.9-3.fc14
ibus-gtk2-1.3.9-3.fc14
ibus-1.3.9-3.fc14
ibus-gtk3-1.3.9-3.fc14
How reproducible:
Steps to Reproduce:
1. Add Bengali=>Probhat and Inscript keyboards from ibus-preferences to enable
them
2. Start openoffice.org writer
3. Enable Probhat keyboard by choosing it from the ibus panel applet
4. Write the following combination:
* 099C + 09CB + 0981
actual key strokes: j]>
to display: জোঁ
* 0995 + 09CB + 0982
actual key strokes: k]L
to display: কোং
* 09B9 + 09CB + 0983
actual key strokes: h]H
to display: হোঃ
Actual results:
Openoffice.org writer crashes
Expected results:
Combinations to be displayed and application should not crash.
Additional info:
1. The bug can be replicated with direct unicode input as well
2. The consonant value can be replaced with any in the range, and same results
are seen. The special character may or may not be different in each case.
3. With no change in the Openoffice.org (and its dependency) packages, these
combinations worked as expected on the ibus GA versions (1.3.9-3.fc14)
--
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.
11 years, 10 months
[Fedora-i18n-bugs] [Bug 498706] New: Key bindings don't work after restart
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: Key bindings don't work after restart
https://bugzilla.redhat.com/show_bug.cgi?id=498706
Summary: Key bindings don't work after restart
Product: Fedora
Version: 9
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: stardict
AssignedTo: cchance(a)redhat.com
ReportedBy: pahan(a)hubbitus.info
QAContact: extras-qa(a)fedoraproject.org
CC: cchance(a)redhat.com, zhu(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
Stardict save keybindings, but its do not work after restart and require reset
it after each boot.
Version-Release number of selected component (if applicable):
# rpm -q stardict
stardict-3.0.1-9.fc9.i386
How reproducible:
Stardict load after boot by any DE (or restored within session). Go to
Preferencies, setup Modifier with wich scan will be doing. Close setting
window.
After that all work fine in this session. After restart computer, scan window
do not appear when defined keys pressed. But, when going into preferencies,
defined keys saved (sic!) and start working just after close window without any
manipulations with it!
--
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.
11 years, 11 months