Attachment 94374 Details for Bug 75220 – 0002-add-be_BY.UTF-8-latin-and-sr_RS.UTF-8-latin-to-local.patch

0002-add-be_BY.UTF-8-latin-and-sr_RS.UTF-8-latin-to-local.patch

0002-add-be_BY.UTF-8-latin-and-sr_RS.UTF-8-latin-to-local.patch (text/plain), 1.42 KB, created by Mike FABIAN on 2014-02-19 17:58:40 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Mike FABIAN

Created: 2014-02-19 17:58:40 UTC

Size: 1.42 KB

patch

obsolete

>From 5657481f070f3a8bd9764610c89594caffb53b77 Mon Sep 17 00:00:00 2001
>From: Mike FABIAN <mfabian@redhat.com>
>Date: Wed, 19 Feb 2014 11:50:55 +0100
>Subject: [PATCH 2/2] add be_BY.UTF-8@latin and sr_RS.UTF-8@latin to locale.dir
>
>See also: https://bugzilla.redhat.com/show_bug.cgi?id=1066910
>
>If these are not in locale.dir,
>
>    $ LANG=sr_RS.UTF-8@latin xterm
>
>and
>
>    $ LANG=sr_RS@latin xterm
>
>give the warning:
>
>    Warning: locale not supported by Xlib, locale set to C
>
>and some programs (like xmms) fail to find translations for Serbian
>in Latin because of this.
>---
> nls/locale.dir.pre | 2 ++
> 1 file changed, 2 insertions(+)
>
>diff --git a/nls/locale.dir.pre b/nls/locale.dir.pre
>index be6f3ba..8570ba3 100644
>--- a/nls/locale.dir.pre
>+++ b/nls/locale.dir.pre
>@@ -292,6 +292,7 @@ en_US.UTF-8/XLC_LOCALE:			ar_YE.UTF-8
> en_US.UTF-8/XLC_LOCALE:			as_IN.UTF-8
> en_US.UTF-8/XLC_LOCALE:			az_AZ.UTF-8
> en_US.UTF-8/XLC_LOCALE:			be_BY.UTF-8
>+en_US.UTF-8/XLC_LOCALE:			be_BY.UTF-8@latin
> en_US.UTF-8/XLC_LOCALE:			bg_BG.UTF-8
> en_US.UTF-8/XLC_LOCALE:			bn_BD.UTF-8
> en_US.UTF-8/XLC_LOCALE:			bn_IN.UTF-8
>@@ -440,6 +441,7 @@ en_US.UTF-8/XLC_LOCALE:			sq_AL.UTF-8
> en_US.UTF-8/XLC_LOCALE:			sr_CS.UTF-8
> en_US.UTF-8/XLC_LOCALE:			sr_ME.UTF-8
> en_US.UTF-8/XLC_LOCALE:			sr_RS.UTF-8
>+en_US.UTF-8/XLC_LOCALE:			sr_RS.UTF-8@latin
> en_US.UTF-8/XLC_LOCALE:			sr_YU.UTF-8
> en_US.UTF-8/XLC_LOCALE:			ss_ZA.UTF-8
> en_US.UTF-8/XLC_LOCALE:			st_ZA.UTF-8
>-- 
>1.8.5.3
>

Actions: View

Attachments on bug 75220: 94374

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.