mfabian@ari:/usr/share/locale/sr@Latn/LC_MESSAGES $ rpm -qf libgda-5.0.mo libgda-5.1.2-4.fc20.x86_64 mfabian@ari:/usr/share/locale/sr@Latn/LC_MESSAGES $ Please move the Serbian translations in Latin script from /usr/share/locale/sr@Latn/LC_MESSAGES/ to /usr/share/locale/sr@latin/LC_MESSAGES/ Reasoning: "Latn" is not the way the Latin script is spelled in glibc locales. "Latn" is the script code according to ISO 15924 http://www.unicode.org/iso15924/iso15924-codes.html used by CLDR and libicu. But glibc locales spell it "latin" and "Latn" doesn’t work with gettext: Check contents of the translation files: mfabian@ari:~ $ msgunfmt /usr/share/locale/sr@Latn/LC_MESSAGES/xdg-user-dirs.mo | grep -A1 "Applications" msgunfmt /usr/share/locale/sr@Latn/LC_MESSAGES/xdg-user-dirs.mo | grep -A1 "Applications" msgid "Applications" msgstr "Programi" mfabian@ari:~ $ msgunfmt /usr/share/locale/sr/LC_MESSAGES/xdg-user-dirs.mo | grep -A1 "Applications" msgunfmt /usr/share/locale/sr/LC_MESSAGES/xdg-user-dirs.mo | grep -A1 "Applications" msgid "Applications" msgstr "Програми" mfabian@ari:~ $ msgunfmt /usr/share/locale/sr@latin/LC_MESSAGES/xdg-user-dirs-gtk.mo | grep -A1 "Current folder name" msgunfmt /usr/share/locale/sr@latin/LC_MESSAGES/xdg-user-dirs-gtk.mo | grep -A1 "Current folder name" msgid "Current folder name" msgstr "Trenutno ime" mfabian@ari:~ $ msgunfmt /usr/share/locale/sr/LC_MESSAGES/xdg-user-dirs-gtk.mo | grep -A1 "Current folder name" msgunfmt /usr/share/locale/sr/LC_MESSAGES/xdg-user-dirs-gtk.mo | grep -A1 "Current folder name" msgid "Current folder name" msgstr "Тренутно име" mfabian@ari:~ $ Correct. Check whether the /usr/share/locale/sr@latin/LC_MESSAGES/xdg-user-dirs-gtk.mo translations can be retrieved with gettext using the @latin modifier: mfabian@ari:~ $ LC_ALL=sr_RS@latin gettext -d xdg-user-dirs-gtk "Current folder name" LC_ALL=sr_RS@latin gettext -d xdg-user-dirs-gtk "Current folder name" Trenutno imemfabian@ari:~ $ LC_ALL=sr_RS.UTF-8@latin gettext -d xdg-user-dirs-gtk "Current folder name" LC_ALL=sr_RS.UTF-8@latin gettext -d xdg-user-dirs-gtk "Current folder name" Trenutno imemfabian@ari:~ $ LC_ALL=sr_RS.UTF-8 gettext -d xdg-user-dirs-gtk "Current folder name" LC_ALL=sr_RS.UTF-8 gettext -d xdg-user-dirs-gtk "Current folder name" Тренутно имеmfabian@ari:~ $ Works, with @latin one gets the Serbian translation in latin script, without @latin the Cyrillic ones. Now check whether the /usr/share/locale/sr@Latn/LC_MESSAGES/xdg-user-dirs.mo translations can be retrieved with gettext using the @latin or the @Latn modifier: mfabian@ari:~ $ LC_ALL=sr_RS.UTF-8@latin gettext -d xdg-user-dirs "Applications" LC_ALL=sr_RS.UTF-8@latin gettext -d xdg-user-dirs "Applications" Програмиmfabian@ari:~ $ LC_ALL=sr_RS@latin gettext -d xdg-user-dirs "Applications" LC_ALL=sr_RS@latin gettext -d xdg-user-dirs "Applications" Програмиmfabian@ari:~ $ So it doesn’t work with "@latin" because the "sr@Latn" directory is mistakenly used, we get the fallback to Cyrillic instead. sr_RS@latin and sr_RS.UTF-8@latin are valid locales, so if a suitable folder containing the @latin cannot be found, gettext falls back to the "sr" folder which exists and contains Cyrillic. Now trying with @Latn: mfabian@ari:~ $ LC_ALL=sr_RS.UTF-8@Latn gettext -d xdg-user-dirs "Applications" LC_ALL=sr_RS.UTF-8@Latn gettext -d xdg-user-dirs "Applications" Applicationsmfabian@ari:~ $ LC_ALL=sr_RS@Latn gettext -d xdg-user-dirs "Applications" LC_ALL=sr_RS@Latn gettext -d xdg-user-dirs "Applications" Applicationsmfabian@ari:~ $ We get the fallback to English beause sr_RS.UTF-8@Latn and sr_RS@Latn are not valid glibc locales. sr_RS.UTF-8@latin and sr_RS@latin are OK: mfabian@ari:~ $ LC_ALL=sr_RS.UTF-8@latin locale charmap LC_ALL=sr_RS.UTF-8@latin locale charmap UTF-8 mfabian@ari:~ $ LC_ALL=sr_RS@latin locale charmap LC_ALL=sr_RS@latin locale charmap UTF-8 mfabian@ari:~ But sr_RS.UTF-8@Latn and sr_RS@Latn are not valid: mfabian@ari:~ $ LC_ALL=sr_RS.UTF-8@Latn locale charmap LC_ALL=sr_RS.UTF-8@Latn locale charmap locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968 mfabian@ari:~ $ LC_ALL=sr_RS@Latn locale charmap LC_ALL=sr_RS@Latn locale charmap locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968 mfabian@ari:~ $
There is still a problem in Fedora-Live-Workstation-x86_64-22_Beta-3.iso : [mfabian@Fedora-Live-Workstation-x86_64-2 ~]$ ll /usr/share/locale/sr@Latn/LC_MESSAGES/libgda-5.0.mo /usr/share/locale/sr@latin/LC_MESSAGES/libgda-5.0.mo -rw-r--r--. 1 root root 2385 8月 17 2014 /usr/share/locale/sr@Latn/LC_MESSAGES/libgda-5.0.mo -rw-r--r--. 1 root root 197151 8月 17 2014 /usr/share/locale/sr@latin/LC_MESSAGES/libgda-5.0.mo [mfabian@Fedora-Live-Workstation-x86_64-2 ~]$ rpm -qf /usr/share/locale/sr@Latn/LC_MESSAGES/libgda-5.0.mo /usr/share/locale/sr@latin/LC_MESSAGES/libgda-5.0.mo libgda-5.2.2-7.fc22.x86_64 libgda-5.2.2-7.fc22.x86_64 [mfabian@Fedora-Live-Workstation-x86_64-2 ~]$ I.e. both /usr/share/locale/sr@Latn/LC_MESSAGES/libgda-5.0.mo and /usr/share/locale/sr@latin/LC_MESSAGES/libgda-5.0.mo exist and the files are not identical. Only the sr@latin directory should exist.
I removed po/sr upstream in both master and LIBGDA_5.2 stable branch: https://git.gnome.org/browse/libgda/commit/?id=855f1420bae2c3904308d7d45822499c8610cc85 https://git.gnome.org/browse/libgda/commit/?h=LIBGDA_5.2&id=989d765936ca1f35d9087cd008d6c67ab012d120 Unfortunately, there were no new releases since that. 5.2.5 (or 6.0) will have only sr@latin.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
mfabian@ari:~ $ rpm -qf /usr/share/locale/sr@Latn/LC_MESSAGES/libgda-5.0.mo libgda-5.2.2-11.fc24.x86_64 mfabian@ari:~ $ cat /etc/fedora-release Fedora release 24 (Twenty Four) mfabian@ari:~ $
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora 'version' of '24'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.