[Fedora-i18n-bugs] [Bug 638650] New: better localized name for zh_TW in locale-list
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: better localized name for zh_TW in locale-list
https://bugzilla.redhat.com/show_bug.cgi?id=638650
Summary: better localized name for zh_TW in locale-list
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: system-config-language
AssignedTo: psatpute(a)redhat.com
ReportedBy: chaoweilun(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: psatpute(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org, nkumar(a)redhat.com
Classification: Fedora
Description of problem:
The localized name for the locale zh_TW is inadequate.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1.running system-config-language or
2.viewing /usr/share/system-config-language/locale-list
3.
Actual results:
正體中文
Expected results:
傳統漢語
Additional info:
--
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.
10 years, 11 months
[Fedora-i18n-bugs] [Bug 545701] New: [kn_IN] Pango doesn't render 0c95+0ccd+0c95+0c97 combination properly
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: [kn_IN] Pango doesn't render 0c95+0ccd+0c95+0c97 combination properly
https://bugzilla.redhat.com/show_bug.cgi?id=545701
Summary: [kn_IN] Pango doesn't render 0c95+0ccd+0c95+0c97
combination properly
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: pango
AssignedTo: besfahbo(a)redhat.com
ReportedBy: svenkate(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: besfahbo(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=377107)
--> (https://bugzilla.redhat.com/attachment.cgi?id=377107)
shows the actual and correct rendering
Description of problem:
Pango doesn't render a particular character combination properly.
Version-Release number of selected component (if applicable):
1.26.0-1.fc12
How reproducible:
Always
Steps to Reproduce:
1.Enable the Kannada support
2. Select the "inscript" layout from ibus menu, and type the following key
combination: j+d+j+>
OR
Select "other-rawcode" from ibus menu and type the following key combination
0c95+0ccd+0c95+0c97
Actual results:
ಕ್ಕಷ
Expected results:
As shown in the attached image
Additional info:
Reported upstream at https://bugzilla.gnome.org/show_bug.cgi?id=604060
--
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
[Fedora-i18n-bugs] [Bug 632965] New: Country Name list is untranslated while configure Mobile Broadband
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: Country Name list is untranslated while configure Mobile Broadband
https://bugzilla.redhat.com/show_bug.cgi?id=632965
Summary: Country Name list is untranslated while configure
Mobile Broadband
Product: Fedora
Version: 14
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: NetworkManager
AssignedTo: dcbw(a)redhat.com
ReportedBy: aalam(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: dcbw(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Target Release: ---
Description of problem:
Country Name list is untranslated while configure Mobile Broadband with NM.
/usr/share/mobile-broadband-provider-info/serviceproviders.xml
Version-Release number of selected component (if applicable):
mobile-broadband-provider-info-1.20100122-1.fc13.noarch.rpm
NetworkManager-0.8.1-5.git20100818.fc14.x86_64.rpm
How reproducible:
100%
Steps to Reproduce:
1. Right Click on NM applet
2. Edit Connection
3. Mobile Broadband->Add->Next
4. Check Country List
Actual results:
it is Untranslated
Expected results:
it need to be translated.
Additional info:
--
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, 2 months
[Fedora-i18n-bugs] [Bug 692358] New: Periodic error message: Unknown format at
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: Periodic error message: Unknown format at
https://bugzilla.redhat.com/show_bug.cgi?id=692358
Summary: Periodic error message: Unknown format at
Product: Red Hat Enterprise Linux 6
Version: 6.0
Platform: i686
OS/Version: Linux
Status: NEW
Severity: medium
Priority: unspecified
Component: eclipse-nls
AssignedTo: sflaniga(a)redhat.com
ReportedBy: frederik.vogelsang(a)gmail.com
QAContact: qe-i18n-bugs(a)redhat.com
CC: petersen(a)redhat.com, overholt(a)redhat.com,
eng-i18n-bugs(a)redhat.com, oliver(a)linux-kernel.at,
choeger(a)cs.tu-berlin.de, sflaniga(a)redhat.com,
ebaron(a)fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
akurtako(a)redhat.com, sgehwolf(a)redhat.com,
greubel(a)nkey.de
Classification: Red Hat
Story Points: ---
Clone Of: 653344
The periodic error message is produced by this package:
eclipse-nls-de-3.5.0.v20090620043401-4.el6.i686
It only appears when working with projects which contain error messages.
$> rpm -qa | grep eclipse
eclipse-cdt-6.0.2-3.el6.i686
eclipse-mylyn-java-3.3.2-4.5.el6.i686
eclipse-swt-3.5.2-5.el6.i686
eclipse-gef-3.5.2-1.el6.i686
eclipse-subclipse-1.6.5-6.el6.i686
eclipse-mylyn-3.3.2-4.5.el6.i686
eclipse-nls-de-3.5.0.v20090620043401-4.el6.i686
eclipse-birt-2.5.2-1.el6.i686
jetty-eclipse-6.1.21-1.el6.noarch
eclipse-linuxprofilingframework-0.3.0-5.el6.i686
eclipse-valgrind-0.5.0-1.el6.i686
icu4j-eclipse-4.0.1-3.3.el6.i686
eclipse-dtp-1.7.2-1.el6.i686
eclipse-svnkit-1.3.0-3.el6.i686
eclipse-callgraph-0.5.0-1.el6.i686
eclipse-rse-3.1.2-1.el6.i686
eclipse-changelog-2.6.7-5.el6.i686
eclipse-rpm-editor-0.5.0-2.el6.i686
eclipse-nls-3.5.0.v20090620043401-4.el6.i686
eclipse-nls-de-3.5.0.v20090620043401-4.el6.i686
eclipse-platform-3.5.2-5.el6.i686
eclipse-jdt-3.5.2-5.el6.i686
eclipse-oprofile-0.5.0-1.el6.i686
eclipse-rcp-3.5.2-5.el6.i686
eclipse-emf-2.5.0-4.4.el6.i686
+++ This bug was initially created as a clone of Bug #653344 +++
Description of problem:
Periodically my eclipse shows me an error about a malformatted message. This is
a german locale. Not sure what plugin causes this.
Version-Release number of selected component (if applicable):
[choeger@elrond page-runtime]$ rpm -qa | grep eclipse
tomcat5-jasper-eclipse-5.5.27-7.4.fc12.noarch
eclipse-mylyn-java-3.4.0-4.fc14.noarch
eclipse-gef-3.6.0-1.fc14.noarch
eclipse-nls-de-3.5.0.v20090620043401-2.fc12.noarch
eclipse-dtp-1.8.0-1.fc14.noarch
eclipse-jgit-0.9.3-1.fc14.noarch
eclipse-nls-3.5.0.v20090620043401-2.fc12.noarch
eclipse-oprofile-0.6.1-1.fc14.x86_64
eclipse-pydev-1.6.1-1.fc14.x86_64
eclipse-birt-2.5.2-1.fc14.noarch
eclipse-subclipse-1.6.12-1.fc14.noarch
eclipse-rpm-editor-0.6.0-1.fc14.x86_64
eclipse-jdt-3.6.1-2.fc14.x86_64
eclipse-linuxprofilingframework-0.6.1-1.fc14.x86_64
eclipse-collabnet-merge-2.0.0-1.fc13.noarch
eclipse-cdt-7.0.1-2.fc14.x86_64
eclipse-valgrind-0.6.1-1.fc14.x86_64
eclipse-platform-3.6.1-2.fc14.x86_64
eclipse-emf-2.6.0-2.fc14.noarch
eclipse-mylyn-3.4.0-4.fc14.noarch
eclipse-rcp-3.6.1-2.fc14.x86_64
eclipse-changelog-2.6.7-5.fc14.x86_64
eclipse-pde-3.6.1-2.fc14.x86_64
eclipse-svnkit-1.3.3-5.fc14.noarch
eclipse-callgraph-0.6.1-1.fc14.x86_64
eclipse-egit-0.9.3-1.fc14.noarch
icu4j-eclipse-4.2.1-1.fc14.x86_64
eclipse-swt-3.6.1-2.fc14.x86_64
eclipse-rse-3.2-1.fc14.noarch
How reproducible:
always
Steps to Reproduce:
1. Start eclipse
2. Save some java file
Actual results:
error message pops up
Additional info:
Stack trace from log:
java.lang.IllegalArgumentException: unknown format type at
at com.ibm.icu.text.MessageFormat.makeFormat(MessageFormat.java:2069)
at com.ibm.icu.text.MessageFormat.applyPattern(MessageFormat.java:571)
at com.ibm.icu.text.MessageFormat.<init>(MessageFormat.java:420)
at com.ibm.icu.text.MessageFormat.format(MessageFormat.java:1109)
at
org.eclipse.ui.internal.views.markers.ExtendedMarkersView.getStatusMessage(ExtendedMarkersView.java:890)
at
org.eclipse.ui.internal.views.markers.ExtendedMarkersView.updateTitle(ExtendedMarkersView.java:1395)
at
org.eclipse.ui.internal.views.markers.UIUpdateJob.runInUIThread(UIUpdateJob.java:117)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
--- Additional comment from greubel(a)nkey.de on 2010-11-21 06:43:14 EST ---
Workaround: Remove the nls package for eclipse. In my case this was
Nov 21 12:39:20 Erased: eclipse-nls-de
Then the problem seems to be gone.
--- Additional comment from akurtako(a)redhat.com on 2010-11-22 02:49:21 EST ---
So this is a problem with eclipse-nls. Changing component.
--- Additional comment from choeger(a)cs.tu-berlin.de on 2010-11-23 17:04:05 EST
---
Yeah, seems to be a bad formatted translation string. I hoped someone with a
little more spare time then me currently could figure out what string that was
from the backtrace and fix it. Maybe I could do it next week if noone steps in.
--- Additional comment from greubel(a)nkey.de on 2010-11-24 01:30:54 EST ---
If it helps: it occurs any time, when some entry in the error log appear (or
maybe also disappear - not tested). For example, if you compile a C Makefile
project which has some warnings (unused variables, etc.)
--- Additional comment from sflaniga(a)redhat.com on 2010-11-29 00:06:25 EST ---
I haven't had a chance to reproduce the problem yet, but does anyone want to
try the updated lang packs to see if they fix the problem?
http://koji.fedoraproject.org/koji/taskinfo?taskID=2631446
You'll need to grab the base rpm:
eclipse-nls-3.6.0.v20100814043401-1.fc15.noarch.rpm
plus the 'de' rpm:
eclipse-nls-de-3.6.0.v20100814043401-1.fc15.noarch.rpm
--- Additional comment from sflaniga(a)redhat.com on 2010-11-29 02:26:52 EST ---
Another build, basically the same as the last one:
http://koji.fedoraproject.org/koji/buildinfo?buildID=206810
Again, you'll need to grab the base eclipse-nls rpm:
http://kojipkgs.fedoraproject.org/packages/eclipse-nls/3.6.0.v20100814043...
plus the eclipse-nls-de rpm:
http://kojipkgs.fedoraproject.org/packages/eclipse-nls/3.6.0.v20100814043...
--- Additional comment from updates(a)fedoraproject.org on 2010-12-09 20:08:13
EST ---
eclipse-nls-3.6.0.v20100814043401-2.fc14 has been submitted as an update for
Fedora 14.
https://admin.fedoraproject.org/updates/eclipse-nls-3.6.0.v20100814043401...
--- Additional comment from updates(a)fedoraproject.org on 2010-12-10 15:25:50
EST ---
eclipse-nls-3.6.0.v20100814043401-2.fc14 has been pushed to the Fedora 14
testing repository. If problems still persist, please make note of it in this
bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update eclipse-nls'. You can provide
feedback for this update here:
https://admin.fedoraproject.org/updates/eclipse-nls-3.6.0.v20100814043401...
--- Additional comment from greubel(a)nkey.de on 2010-12-28 07:37:29 EST ---
Installed using the recommended command, started eclipse, rebuild a project
which contains warnings (CDT).
eclipse-nls-de-3.6.0.v20100814043401-2.fc14.noarch solves the problem for me.
Thank you.
--- Additional comment from updates(a)fedoraproject.org on 2011-01-04 15:59:46
EST ---
eclipse-nls-3.6.0.v20100814043401-2.fc14 has been pushed to the Fedora 14
stable repository. If problems still persist, please make note of it in this
bug report.
--
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, 2 months
[Fedora-i18n-bugs] [Bug 504757] New: Bad translation in German language pack
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: Bad translation in German language pack
https://bugzilla.redhat.com/show_bug.cgi?id=504757
Summary: Bad translation in German language pack
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: eclipse-nls
AssignedTo: sflaniga(a)redhat.com
ReportedBy: kenda(a)fedoraproject.org
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, overholt(a)redhat.com,
sflaniga(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
When creating a new java class, the checkbox for adding the 'public static
void' method is translated literally. That doesn't make sense in German.
Version-Release number of selected component (if applicable):
Eclipse-nls-de-3.4.0.v20090423085802
How reproducible:
Starting Eclipse
"Datei - Neu - Klasse"
Actual results:
"öffentlich statisch ungültig Haupt(String[] Argumente)"
Expected results:
"public static void main(String[] args)"
--
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, 2 months
[Fedora-i18n-bugs] [Bug 513901] New: ibus-table setup does not store config settings
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-table setup does not store config settings
https://bugzilla.redhat.com/show_bug.cgi?id=513901
Summary: ibus-table setup does not store config settings
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ibus-table
AssignedTo: cchance(a)redhat.com
ReportedBy: petersen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: cchance(a)redhat.com, phuang(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
ibus-table config is not using gconf to store configuration settings.
Steps to Reproduce:
1. change ibus-table config
2. restart desktop
3. use ibus-table
Actual results:
configuration lost
Expected results:
configuration to persist
--
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, 3 months
[Fedora-i18n-bugs] [Bug 572611] New: ibus should ensure that ~/.config/ibus/bus exists
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 should ensure that ~/.config/ibus/bus exists
https://bugzilla.redhat.com/show_bug.cgi?id=572611
Summary: ibus should ensure that ~/.config/ibus/bus exists
Product: Fedora
Version: 12
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ibus
AssignedTo: phuang(a)redhat.com
ReportedBy: mjg(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: ---
If the ~/.config/ibus/bus directory doesn't exist, any gtk app will wake up
once per second in an attempt to add a notify on it. The directory should be
automatically created to work around this.
--
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, 3 months
[Fedora-i18n-bugs] [Bug 648358] New: Devanagari Northern Variant 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: Devanagari Northern Variant for Lohit Devanagari
https://bugzilla.redhat.com/show_bug.cgi?id=648358
Summary: Devanagari Northern Variant for Lohit Devanagari
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Unspecified
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 456793
--> https://bugzilla.redhat.com/attachment.cgi?id=456793
Chandas Uttara Sahadeva and Lohit Devangari
Description of problem:
The Lohit Devanagari currently uses the most popular variant - the southern
variant of devanagari. But being the default font of fedora a popular os, it
should also support the northern variant of devangari. This requires additions
of newer glyph for:
अ आ ओ औ ऋ ॠ ण झ क्ष
My goal by asking this feature is to make Lohit Devanagari a full featured
Devanagari font.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
I have attached the screenshot showing it in Chandas/Uttara - a GPL'ed font
containing Northern Variant, and a free font Sahadeva containing Northern
variant along with Lohit Hindi. Hope this will help.
--
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, 4 months
[Fedora-i18n-bugs] [Bug 603958] New: gdm kbd layout setting should add US layout by default for layouts without Latin characters
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: gdm kbd layout setting should add US layout by default for layouts without Latin characters
https://bugzilla.redhat.com/show_bug.cgi?id=603958
Summary: gdm kbd layout setting should add US layout by default
for layouts without Latin characters
Product: Red Hat Enterprise Linux 6
Version: 6.1
Platform: All
URL: https://www.redhat.com/archives/fedora-devel-list/2008
-December/msg00047.html
OS/Version: Linux
Status: NEW
Severity: high
Priority: high
Component: gdm
AssignedTo: jmccann(a)redhat.com
ReportedBy: rstrode(a)redhat.com
QAContact: desktop-bugs(a)redhat.com
CC: petersen(a)redhat.com, jmccann(a)redhat.com,
rstrode(a)redhat.com, atigro(a)ya.ru, tfujiwar(a)redhat.com,
pnemade(a)redhat.com, shamardin(a)gmail.com,
atorkhov(a)gmail.com, peter.hutterer(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org,
TBomBM3879(a)gmail.com, sergey.rudchenko(a)gmail.com,
tim623(a)gmail.com
Depends on: 474010
Blocks: 474014
Classification: Red Hat
Target Release: ---
Clone Of: 474010
+++ This bug was initially created as a clone of Bug #474010 +++
Description of problem:
If you select "Russian" keyboard during system installation then gdm is
configured to use Russian input for user names and passwords by default. Any
language different from english does not make sense for user name, and probably
english should be default for passwords.
Version-Release number of selected component (if applicable):
gdm-2.24.0-12.fc10.i386
How reproducible:
always?
Steps to Reproduce:
1. install a fresh fedora system using "Russian" keyboard. Don't be afraid, it
won't affect the installation since during installation you will have US
english layout with this selection anyway.
2. try to enter a login name when you get that far.
Actual results:
You are entering funny cyrillic characters.
Expected results:
English, at least for user name and hopefully for password.
Additional info:
https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00047....
--- Additional comment from TBomBM3879(a)gmail.com on 2009-03-02 18:41:01 EST ---
I don't get this bug?
If you select the Russian keyboard layout, then that's exactly what you'll get;
the Russian layout for the keys on your keyboard.
If you are using a US keyboard, then use the US keyboard layout.
--- Additional comment from TBomBM3879(a)gmail.com on 2009-03-02 19:54:01 EST ---
*** Bug 474011 has been marked as a duplicate of this bug. ***
--- Additional comment from shamardin(a)gmail.com on 2009-03-03 00:35:56 EST ---
(In reply to comment #1)
> I don't get this bug?
In case you don't know, Russian layout does not have any of the the latin
characters.
Unix account names always use English low-case alphabet. Therefore in order to
be able to enter a unix account name (this is an expected thing at a login
screen, right?) you would like to be able to enter English letters, and you
can't if the only keyboard layout available is Russian. Even more, the most
common practice, at least in Russia, is not to use Russian layout when entering
passwords, but use the English layout; otherwise you often can encounter
"there-are-many-encodings" problems.
To have a Russian keyboard layout as the only choice at the login prompt as an
insane default. Nobody even in Russia would be able to use this default
setting. This must be changed.
This is an insane and unsuable default.
And even if you ignore the login problem, almost every Russian user will
install the English keyboard as one of the first actions on a new system,
because there are lots of other places where latin letters are used. Some
examples are unix command line and web URLs.
>
> If you select the Russian keyboard layout, then that's exactly what you'll get;
> the Russian layout for the keys on your keyboard.
>
> If you are using a US keyboard, then use the US keyboard layout.
And I can tell you even more, Russian keyboard layout is not the only layout
with this peculiarity. At least a Greek layout has the same problems. I believe
there are other layouts as well.
For all these layouts you would like to have:
1. English layout selected as default on the login screen.
2. English layout installed as an alternate layout after logging in.
No exceptions.
--- Additional comment from shamardin(a)gmail.com on 2009-03-03 00:38:02 EST ---
This is not the duplicate of 474011. This bug is about insane default, bug
474011 is about broken layout switching at login.
--- Additional comment from tim623(a)gmail.com on 2009-08-04 22:10:41 EDT ---
Solving this bug would solve bug 474014 by eliminating the need to
"double-switch" (see Description of bug 474014.)
--
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
--- Additional comment from fedora-triage-list(a)redhat.com on 2009-11-18
02:47:49 EST ---
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 WONTFIX if it remains open with a Fedora
'version' of '10'.
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 prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
--- Additional comment from petersen(a)redhat.com on 2009-11-24 03:24:00 EST ---
I think I can reproduce this with F12 Live:
1. boot F12 Live
2. switch layout to Russia
3. autologin as liveuser
4. observe only "ru" layout installed not "us" as well
I think we need to install both for Russian: "us,ru"
would probably be better for technical users anyway.
Then Shift+Caps_Lock should allow switching "ru" <-> "us".
--- Additional comment from petersen(a)redhat.com on 2009-11-24 03:45:11 EST ---
Ah I see: if I then logout and change to US kbd layout
and login again then the gnome kbd applet shows "us,ru".
(Though no xkb toggle for changing layout,
eg Shift+Caps_Lock, defined.)
I think we need "XX,us" for all layouts that don't
provide Latin input, or maybe better checkboxes
in the gdm options layout widget to select multiple
layouts?
--- Additional comment from atigro(a)ya.ru on 2009-11-24 04:26:06 EST ---
(In reply to comment #8)
> Ah I see: if I then logout and change to US kbd layout
> and login again then the gnome kbd applet shows "us,ru".
> (Though no xkb toggle for changing layout,
> eg Shift+Caps_Lock, defined.)
>
> I think we need "XX,us" for all layouts that don't
> provide Latin input, or maybe better checkboxes
> in the gdm options layout widget to select multiple
> layouts?
Yes, checkboxes (and pre checkboxed items for different languages) is a very,
very good idea. But "us" must be the primary layout for non latin. For some
other (as cz,us) let it be cz,us.
--- Additional comment from tfujiwar(a)redhat.com on 2009-11-25 23:21:48 EST ---
Probably I could understand this issue.
In the most cases, I would think users could define their keyboard layouts with
gnome-keyboard-properties after they log into the session.
However it seems this request is to the special keyboard layouts which don't
have ASCII chars. They need to type both ASCII and the language chars.
Yes, sending multiple layouts could be a solution. However I'd think that
selecting one layout on GDM is simple.
Probably I think one solution is to configure input method.
E.g. A user chooses "ru" on GDM and log into the GNOME session, ibus checks the
user's layout, if the layout is found in the predefined list in ibus, ibus
provides the "us" layout with Ctrl + Space.
If the users could switch "ru" and "us" with the trigger key, probably I think
this problem could be resolved and if they want other language layouts, they
could use gnome-keyboard-properties.
--- Additional comment from shamardin(a)gmail.com on 2009-11-26 02:53:28 EST ---
No, you don't get it at all.
There is no need to tweak ANYTHING after the log in.
And there is no need to provide switching in GDM.
It is very simple: after user is logged in any kind of defaults, setups etc. is
fine and must be left for the user.
But not at the GDM. At the GDM you ALWAYS need to type latin characters. So, if
you have selected US keyboard you do not need to change anything for GDM
defaults. If you have selected French keyboard you do not need to change
anything for GDM defaults. If you have selected Greek keyboard you MUST change
default layout in GDM to US. If you have selected Russian keyboard you MUST
change default layout in GDM to US. And so on. Not AFTER logging in to GNOME
session. Not allowing to switch with more comfort in GDM. Just set the
appropriate for the keyboard latin layout in GDM as default, and thats it!
--- Additional comment from shamardin(a)gmail.com on 2009-11-26 03:03:56 EST ---
And yes, there is another place in the system which needs the same amount of
sane defaults, but I'm too lazy right now to open a separate bug. It's
gnome-screensaver. If you happen to lock your screen with NO latin layout
available to switch to, you will never be able to unlock it.
The perfect solution would be something like this: at all places which prompt
for system password or login, default selected layout must be appropriate latin
layout (US for US keyboard, French for French keyboard, US for Russian
keyboard, US for greek keyboard, etc.)
--- Additional comment from petersen(a)redhat.com on 2009-11-26 03:47:03 EST ---
Ok so there are two issues
(1) make sure user can input Latin characters in gdm
(2) config good default layouts for desktop
Lev is talking about (1).
So probably (2) might be moved to another bug
even though they might be solvable together.
(Using input-methods or ibus for xkb switching might
help but Latin layout needs to be base layout for
gdm, screensaver, etc.)
--- Additional comment from petersen(a)redhat.com on 2009-11-26 03:48:49 EST ---
However I think the easiest way to solve (1) is by (2).
--- Additional comment from shamardin(a)gmail.com on 2009-11-26 03:52:13 EST ---
You cannot solve (2) because what is a 'good default' for the user is up to the
user to decide. There will always be dissatisfied with your 'good defaults'.
But for the GDM and other login/password prompts there can be only one 'good
default': latin layout.
--- Additional comment from petersen(a)redhat.com on 2009-11-26 03:54:22 EST ---
Taking ru as the example: /usr/share/X11/xkb/symbols/ru
doesn't provide Latin input so when using it the layout
should be set to "us,ru" and xkb can do layout switching
(per window) between us and ru as needed. We are also
thinking how ibus can help with this eventually.
--- Additional comment from tfujiwar(a)redhat.com on 2009-11-26 04:10:13 EST ---
(In reply to comment #11)
> default layout in GDM to US. If you have selected Russian keyboard you MUST
> change default layout in GDM to US. And so on. Not AFTER logging in to GNOME
>From this mention, the Russian users normally select "us" layout in GDM with
the physical Russian keyboard but don't select "ru" layout for the user/passwd
prompt and they like to switch ru and us layout after log into the session?
If we fix this in either GDM or IBus side, probably I think the hard-coded list
is needed and it could be done in ibus.
--- Additional comment from shamardin(a)gmail.com on 2009-11-26 04:24:49 EST ---
(In reply to comment #17)
> From this mention, the Russian users normally select "us" layout in GDM with
> the physical Russian keyboard but don't select "ru" layout for the user/passwd
> prompt and they like to switch ru and us layout after log into the session?
Yes, normally Russian users have "us" layout in GDM with a physical Russian
keyboard, and after logging into the session they usually have two layouts with
switching between them, "us" and "ru" (typically a layout variant which was
named "ru-winkeys" some time ago). Which one is the default depends on the
user's main activity. Those who often type commands usually prefer "us" layout
as the default, while those who use generally mail-browser-office applications
often prefer "ru" layout as the default, but usually all Russian users have two
layouts configured with switching.
For those of you who have no idea what does 'physical Russian keyboard' look
like, I will attach a picture to this bug. Please notice that the keys have two
layouts printed on them: US (upper characters on letter keys, left column of
characters on symbols and numbers) and Russian (lower characters on letter
keys, right column of characters on symbols and numbers).
--- Additional comment from shamardin(a)gmail.com on 2009-11-26 04:25:34 EST ---
Created an attachment (id=373944)
--> (https://bugzilla.redhat.com/attachment.cgi?id=373944)
Photo of a physical russian keyboard, showing two layouts printed on keys.
--- Additional comment from shamardin(a)gmail.com on 2009-11-26 04:29:32 EST ---
Created an attachment (id=373945)
--> (https://bugzilla.redhat.com/attachment.cgi?id=373945)
Photo of a physical greek keyboard, showing two layouts printed on keys.
--- Additional comment from petersen(a)redhat.com on 2009-11-26 20:36:39 EST ---
http://wikipedia.org/wiki/Keyboard_layout
What is the default layout on Windows? Probably Russian?
We have to have default... :)
And what should it be on a Linux desktop?
For all Asian languages we currently default to Latin input
and users have to turn on the input-method for native input.
So to me it seems natural to do the same for xkb layouts.
I think this is might be ok for Fedora's current user audience,
but with long term proliferation we may need to rethink.
--- Additional comment from petersen(a)redhat.com on 2009-11-26 20:43:38 EST ---
Or how would you decide when to switch layout immediately in gdm and when not?
Eg AZERTY (French) or Dvorak users would not want gdm to delay changing layout
until after login.
--- Additional comment from shamardin(a)gmail.com on 2009-11-27 00:22:00 EST ---
On windows if you select Russian keyboard, the system is configured to have two
layouts, US and Russian with layout switching and Russian as default, even at
login prompt.
Windows allows unicode login names (and russian login names become more and
more common for home users). POSIX does not. There is absolutely no point to
have a non-latin layout as default when you need to enter a POSIX login!
--- Additional comment from peter.hutterer(a)redhat.com on 2009-11-27 00:51:55
EST ---
how about the following idea:
gdm provides an on-screen keyboard. this keyboard provides the layout selected
by the user (russian in this case) but also "Switch to US layout" button.
Hitting this button changes _both_ the virtual keyboard and the physical
keyboard to a us layout. Hitting the "back" button (or whatever) changes back
to the previous method.
This is an idea only, with no code to back it up but it solves a few issues:
- users without a keyboard can log in using the virtual keyboard
- users with a non-ascii layout can switch to an ascii-layout if needed
- no "magic" layout switching using possibly unknown keyboard shortcuts
- if the layout is changed to US, the visual representation shows what the
physical keyboard now does. for those not used to the US layout, this provides
an overview of what the keyboard does now.
--- Additional comment from shamardin(a)gmail.com on 2009-11-27 01:37:45 EST ---
(In reply to comment #24)
> how about the following idea:
>
> gdm provides an on-screen keyboard. this keyboard provides the layout selected
> by the user (russian in this case) but also "Switch to US layout" button.
> Hitting this button changes _both_ the virtual keyboard and the physical
> keyboard to a us layout. Hitting the "back" button (or whatever) changes back
> to the previous method.
I have a better idea. Let's make Russian layout with big convinient button to
switch to US as default for US Keyboard.
The whole point is THERE ARE ABSOLUTELY NO CASES WHEN YOU NEED A RUSSIAN LAYOUT
AT LOGIN PROMPT!!!
You do not need switching, you do not need more convinient switching, all you
need is a f-----g latin layout as default!
> This is an idea only, with no code to back it up but it solves a few issues:
> - users without a keyboard can log in using the virtual keyboard
Users without a keyboard must hit "change layout" button first. Great.
> - users with a non-ascii layout can switch to an ascii-layout if needed
And users with non-latin layout must hit "change layout" button first.
> - no "magic" layout switching using possibly unknown keyboard shortcuts
But they can see that big button clearly.
> - if the layout is changed to US, the visual representation shows what the
> physical keyboard now does. for those not used to the US layout, this provides
> an overview of what the keyboard does now.
And we will have a shiny virtual keyboard, great!
--- Additional comment from sergey.rudchenko(a)gmail.com on 2009-12-05 00:32:12
EST ---
My 2 cents.
GDM should know whether it works on a POSIX system and enable ONLY latin
keyboard layout for it's login input field.
>From the other hand, passwords CAN contain non-latin characters so it's worth
to have an ability to type them.
I propose to add a layout indicator (pretty like gnome-panel applet, but
cutted) in right of the password input box. For those who have a non-latin
password. The layout list for the switcher should be filled with the us+system
default keyboard (e.g. us,ru). Notice, the latin layout should go first,
because most of users are careful enough to use a latin password.
And finally, I think the proposed switcher should be hidden if the alternative
layout contains all the latin characters (GDM would need some library to
determine that?).
The switcher widget itself must solve the problem for users unfamiliar with the
default layout toggle shortcuts.
--- Additional comment from tfujiwar(a)redhat.com on 2010-02-19 05:06:11 EST ---
Created an attachment (id=395063)
--> (https://bugzilla.redhat.com/attachment.cgi?id=395063)
Patch for gdm-common.h, gdm-session-direct.c, gdm-layouts.c
Sorry for dispatching the issue.
I thought to fix this in IM side but there are several problems; one is a
design issue in either ibus Linpus version or ibus-xkbc and another is IM
should be disabled in password dialog for lookup table.
Now I'm back to GDM for this issue.
When I see system-config-keyboard, it has the hard-coded table in
/usr/lib/python2.6/site-packages/system_config_keyboard/keyboard_models.py.
Probably it would be a good idea to have the static data instead of parsing xkb
directory.
I picked up "ara", "bg", "cz", "dev", "gr", "gur", "in", "mkd", "ru", "ua" from
the keyboard_models.py.
This patch assigns Ctrl+Shift to switch the layouts of "us" and the original on
both GDM login and logged session.
system-config-keyboard assigns Shift_L+Shift_R but I guess some keyboards might
not have two shifts.
It still needs to change gnome-settings-daemon but almost works fine in my
test.
--- Additional comment from tfujiwar(a)redhat.com on 2010-02-23 04:09:24 EST ---
Created an attachment (id=395671)
--> (https://bugzilla.redhat.com/attachment.cgi?id=395671)
Patch for gdm-common.h, gdm-session-direct.c, gdm-layouts.c
Revised the patch to use gconf and put a label "Ctrl + Shift toggles layouts"
in prompt when you select the non-ASCII layout.
--- Additional comment from tfujiwar(a)redhat.com on 2010-02-23 21:58:03 EST ---
Created an attachment (id=395876)
--> (https://bugzilla.redhat.com/attachment.cgi?id=395876)
Patch for gdm page.ui
The patch is applied over the internal patch gdm-multistack.patch .
--- Additional comment from tfujiwar(a)redhat.com on 2010-02-23 21:59:54 EST ---
Created an attachment (id=395877)
--> (https://bugzilla.redhat.com/attachment.cgi?id=395877)
Patch for gnome-settings-daemon gsd-keyboard-xkb.c
gnome-settings-daemon can load the group layouts with this patch.
--- Additional comment from tfujiwar(a)redhat.com on 2010-02-23 22:39:17 EST ---
Working on the upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=610903
--- Additional comment from fedora-triage-list(a)redhat.com on 2010-03-15
08:11:32 EDT ---
This bug appears to have been reported against 'rawhide' during the Fedora 13
development cycle.
Changing version to '13'.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
--
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, 4 months
[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, 6 months