Bug 176142
Summary: | Please enable Serbian translation in system-config-bind | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Igor Miletic <grejigl-gnomeprevod> |
Component: | libX11 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | jvdias, kmilos |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-08 21:38:15 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 150221 |
Description
Igor Miletic
2005-12-19 18:11:34 UTC
I noticed the updated 'sr.po' file in system-config-bind-4.0.0/po/sr.po - this is now shipped in system-config-bind-4.0.0-33_FC5 - is this what you mean by 'enable Serbian translation' ? The translation has always been enabled, but until now probably has not been correct. Please try out the new version - thanks! Yes, that was what I ment. Thank you. From User-Agent: XML-RPC system-config-bind-4.0.0-33 has been pushed for FC3, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. From User-Agent: XML-RPC system-config-bind-4.0.0-33_FC4 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. I still can't see the translated sr messages in these updated packages. OK, I've had another look at this issue. Running system_config_bind with : # LC_ALL=sr_CS LANG=sr_CS system-config-bind The ONLY translations seen are those done by libglade for the glade generated buttons - no other translations, done by libgdk, are seen, and these messages appear : 'Gdk-WARNING **: locale not supported by Xlib' 'Gdk-WARNING **: cannot set locale modifiers' It appears this may be an Xlib bug. The libX11 package's /usr/share/X11/locale/{locale.alias,locale.dir} contains information for the sr_YU locale (which no longer exists in glibc!) not the sr_CS locale, which is the only sr_* locale listed by 'locale -a' . So once libX11 contains locale information for sr_CS, not sr_YU, the Serbian translations should appear. When I said that I can't see the translation, I guess I meant the problem might be that there are still no /usr/share/locale/sr/LC_MESSAGES/ nor /usr/share/system-config-bind/po/sr/LC_MESSAGES/ in system-config-bind-4.0.0-34_FC5.noarch.rpm Almost like they're not being built and shipped at all... XOrg upstream should be ok AFAIK since other people have been working on our new sr_CS locale support when the country code changed two years ago, other translations show up fine so far... OK, sorry for the confusion - sr_* was missing from LINGUAS in the po/Makefile - it is now added with system-config-bind-4.0.0-36* in FC5, FC4, and FC3 . But I still get the messages from libgdm about Xlib not knowing about the sr_CS* locales: $ LANG=sr_CS LC_ALL=sr_CS system-config-bind (system-config-bind:6517): Gdk-WARNING **: locale not supported by Xlib (system-config-bind:6517): Gdk-WARNING **: cannot set locale modifiers This comes from the XSupportsLocale Xlib function, which cannot find anything about the sr_CS locale (it only has information for the sr_YU locale), so XSetLocaleModifiers cannot be invoked and no Input Method modifiers can be set - I think this should still be rectified in Xlib, since the sr_YU locale is defunct. After checking with local people in the know, it really looks like the sr_CS issue was never brought up upstream in XFree86/XOrg, so thanks Jason for spotting that. The upstream bug report is here: https://bugs.freedesktop.org/show_bug.cgi?id=5575 Thanks, we'll track the issue in the upstream bugzilla. |