[Bug localedata/16374] New: Change currency symbol in LC_MONETARY in lv_LV

[Bug localedata/16374] New: Change currency symbol in LC_MONETARY in lv_LV

[lafriks at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

            Bug ID: 16374
           Summary: Change currency symbol in LC_MONETARY in lv_LV
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: localedata
          Assignee: unassigned at sourceware dot org
          Reporter: lafriks at gmail dot com
                CC: libc-locales at sourceware dot org

As of 01.01.2014 official currency in Latvia will be Euro so this should be
changed in LC_MONETARY from LVL/Ls to euro. Order of currency symbol should be
the same as for other EU countries where euro currency are used.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[lafriks at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

Lafriks <lafriks at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lafriks at gmail dot com

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[cjlhomeaddress at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

Chris Leonard <cjlhomeaddress at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cjlhomeaddress at gmail dot com

--- Comment #1 from Chris Leonard <cjlhomeaddress at gmail dot com> ---
Is this best handled by the creation of an @euro locale (like some many others)
or are we beyond that point in time and should be gin jsut making direct
changes to locales?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[lafriks at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

--- Comment #2 from Lafriks <lafriks at gmail dot com> ---
If you asking me I don't see point in keeping locale with Ls/LVL as as of
01.01.2014 it will be just history :) I would vote for making direct changes to
current locale.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[carlos at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com

--- Comment #3 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Chris Leonard from comment #1)
> Is this best handled by the creation of an @euro locale (like some many
> others) or are we beyond that point in time and should be gin jsut making
> direct changes to locales?

If the locales character set already has the euro symbol then I see no reason
not to directly edit the locale itself. If we need a new character set then
that's a different issue and then we should be using @euro to transition from
the old character set to the new one. I don't know if the the BALTIC charset in
use by lv_LV has a euro symbol. If it doesn't then I recommend we create
lv_LV@euro with an alternate charset that supports the euro symbol.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[carlos at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Carlos O'Donell from comment #3)
> (In reply to Chris Leonard from comment #1)
> > Is this best handled by the creation of an @euro locale (like some many
> > others) or are we beyond that point in time and should be gin jsut making
> > direct changes to locales?
> 
> If the locales character set already has the euro symbol then I see no
> reason not to directly edit the locale itself. If we need a new character
> set then that's a different issue and then we should be using @euro to
> transition from the old character set to the new one. I don't know if the
> the BALTIC charset in use by lv_LV has a euro symbol. If it doesn't then I
> recommend we create lv_LV@euro with an alternate charset that supports the
> euro symbol.

Please note that this isn't a make-work project, but rather that there is some
software that doesn't yet work with the euro symbol correctly, therefore we
provide two locales during a transitional period to allow users to run certain
applications using the old locale.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[lafriks at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

--- Comment #5 from Lafriks <lafriks at gmail dot com> ---
In Baltic charset there is no euro sign and there is no other charset that
contains euro sign and characters needed for Latvian language.
Solution would probably be change LVL/Ls to EUR (e.g. EUR 123,56) in lv_LV and
to euro sign (e.g. 123,56 €) in lv_LV.UTF-8.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-20595-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Dec 31 19:38:32 2013
Return-Path: <glibc-bugs-return-20595-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 19882 invoked by alias); 31 Dec 2013 19:38:32 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 19830 invoked by uid 48); 31 Dec 2013 19:38:28 -0000
From: "cjlhomeaddress at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV
Date: Tue, 31 Dec 2013 19:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: localedata
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cjlhomeaddress at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16374-131-bF4ogaAx4B@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16374-131@http.sourceware.org/bugzilla/>
References: <bug-16374-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-12/txt/msg00241.txt.bz2
Content-length: 1095

https://sourceware.org/bugzilla/show_bug.cgi?id\x16374

--- Comment #6 from Chris Leonard <cjlhomeaddress at gmail dot com> ---

This simple patch built fine with make testing.

Does this seem to do the job?



>From 54142df97f52c008a6859c4a0ddecc780f4fd86f Mon Sep 17 00:00:00 2001
From: Chris Leonard <cjlhomeaddress@gmail.com>
Date: Tue, 31 Dec 2013 14:32:06 -0500
Subject: [PATCH] Change currency symbol in LC_MONETARY in lv_LV

---
 localedata/locales/lv_LV | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/localedata/locales/lv_LV b/localedata/locales/lv_LV
index 5fbfa1b..47695f5 100644
--- a/localedata/locales/lv_LV
+++ b/localedata/locales/lv_LV
@@ -2122,8 +2122,8 @@ translit_end
 END LC_CTYPE

 LC_MONETARY
-int_curr_symbol   "<U004C><U0056><U004C><U0020>"
-currency_symbol   "<U004C><U0073>"
+int_curr_symbol           "<U0045><U0055><U0052><U0020>"
+currency_symbol           "<U20AC>"
 mon_decimal_point "<U002C>"
 mon_thousands_sep "<U00A0>"
 mon_grouping      3;3
--
1.7.11.7

--
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[carlos at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

--- Comment #7 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Lafriks from comment #5)
> In Baltic charset there is no euro sign and there is no other charset that
> contains euro sign and characters needed for Latvian language.
> Solution would probably be change LVL/Ls to EUR (e.g. EUR 123,56) in lv_LV
> and to euro sign (e.g. 123,56 €) in lv_LV.UTF-8.

If it is true that there is no character set that contains the euro and the
characters needed for the Latvian language then yes I agree that it would be OK
to switch to using "EUR" for lv_LV and the euro symbol for lv_LV.UTF-8.

Are you certain that say ISO-8859-15 doesn't have the characters required for
Latvian?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-20597-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Dec 31 19:45:14 2013
Return-Path: <glibc-bugs-return-20597-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 23629 invoked by alias); 31 Dec 2013 19:45:13 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 23571 invoked by uid 48); 31 Dec 2013 19:45:10 -0000
From: "cjlhomeaddress at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV
Date: Tue, 31 Dec 2013 19:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: localedata
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cjlhomeaddress at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16374-131-DvuVmywNRX@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16374-131@http.sourceware.org/bugzilla/>
References: <bug-16374-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-12/txt/msg00243.txt.bz2
Content-length: 404

https://sourceware.org/bugzilla/show_bug.cgi?id\x16374

--- Comment #8 from Chris Leonard <cjlhomeaddress at gmail dot com> ---

Here is the relevant section of the locale make


. . .
lt_LT.UTF-8... done
lt_LT.ISO-8859-13... done
lv_LV.UTF-8... done
lv_LV.ISO-8859-13... done
lzh_TW.UTF-8... done
mag_IN.UTF-8... done
. . .

--
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[carlos at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

--- Comment #9 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Chris Leonard from comment #8)
> Here is the relevant section of the locale make
> 
> 
> . . . 
> lt_LT.UTF-8... done
> lt_LT.ISO-8859-13... done
> lv_LV.UTF-8... done
> lv_LV.ISO-8859-13... done
> lzh_TW.UTF-8... done
> mag_IN.UTF-8... done
> . . .

That's right, gconv's internal alias table aliases BALTIC to ISO-8859-13.

The next steps here are:
* Verify that ISO-8859-13 lacks the euro symbol.
  * If it does then consider creating lv_LV@euro using ISO-8859-15, but only if
    that charset has the required Latvian characters.
  * If it has the euro symbol then just switch lv_LV to use the euro symbol
    from the ISO-8859-13 character set. This skips the creation of the
alternate
    @euro locale because the character set hasn't changed.
* Post changes.
* Get review and checkin.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[aj at suse dot de]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

--- Comment #10 from Andreas Jaeger <aj at suse dot de> ---
I think we should go for UTF-8. In general all new locales are UTF-8, thus
switching here should be fine.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[carlos at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

--- Comment #11 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Andreas Jaeger from comment #10)
> I think we should go for UTF-8. In general all new locales are UTF-8, thus
> switching here should be fine.

My worry is that there are programs written that support the BALTIC character
set but don't run correctly in full UTF-8. Offering the alternative lv_LV@euro
(using UTF-8) allows a distribution to default to lv_LV@euro with users using
lv_LV to run older programs that don't fully work with UTF-8?

Does that make sense?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[lafriks at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

--- Comment #12 from Lafriks <lafriks at gmail dot com> ---
Yes, I'm sure ISO-8859-15 does not contain required characters for Latvian
language. Required (0xA1+) characters in Latvian language are: Ā, ā, Č, č, Ē,
ē, Ģ, ģ, Ī, ī, Ķ, ķ, Ļ, ļ, Ņ, ņ Š, š, Ū, ū, Ž, ž. Only way of changing to euro
in ISO-8859-13 is to use EUR.

(In reply to Carlos O'Donell from comment #9)
> 
> That's right, gconv's internal alias table aliases BALTIC to ISO-8859-13.
> 
> The next steps here are:
> * Verify that ISO-8859-13 lacks the euro symbol.
>   * If it does then consider creating lv_LV@euro using ISO-8859-15, but only
> if
>     that charset has the required Latvian characters.
>   * If it has the euro symbol then just switch lv_LV to use the euro symbol
>     from the ISO-8859-13 character set. This skips the creation of the
> alternate
>     @euro locale because the character set hasn't changed.
> * Post changes.
> * Get review and checkin.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-20611-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Jan 02 06:16:22 2014
Return-Path: <glibc-bugs-return-20611-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 20848 invoked by alias); 2 Jan 2014 06:16:21 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 20795 invoked by uid 48); 2 Jan 2014 06:16:16 -0000
From: "lafriks at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV
Date: Thu, 02 Jan 2014 06:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: localedata
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lafriks at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16374-131-ehA6aMUIW7@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16374-131@http.sourceware.org/bugzilla/>
References: <bug-16374-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-01/txt/msg00012.txt.bz2
Content-length: 785

https://sourceware.org/bugzilla/show_bug.cgi?id\x16374

--- Comment #13 from Lafriks <lafriks at gmail dot com> ---
But how would lv_LV@euro differ from already wildly used lv_LV.UTF-8? If it is
just an alias to lv_LV.UTF-8 than ok but otherwise I don't see point in
creating lv_LV@euro as it should be equal to lv_LV.UTF-8.

(In reply to Carlos O'Donell from comment #11)
> My worry is that there are programs written that support the BALTIC
> character set but don't run correctly in full UTF-8. Offering the
> alternative lv_LV@euro (using UTF-8) allows a distribution to default to
> lv_LV@euro with users using lv_LV to run older programs that don't fully
> work with UTF-8?
>
> Does that make sense?

--
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[carlos at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

--- Comment #14 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Lafriks from comment #13)
> But how would lv_LV@euro differ from already wildly used lv_LV.UTF-8? If it
> is just an alias to lv_LV.UTF-8 than ok but otherwise I don't see point in
> creating lv_LV@euro as it should be equal to lv_LV.UTF-8.

That's right, sorry I'd forgotten about that, which is why I initially
suggested that lv_LV@euro use ISO-8859-15 instead of UTF-8.

I don't have any data to confirm that lv_LV.UTF-8 is in common usage, but I
expect it should be. If lv_LV.UTF-8 were already wildly used why do we need to
change lv_LV? The distributions should simply default to the .UTF-8 locale?

Either way this is what needs to be done in my opinion:

Guiding Principles:

(a) The existing lv_LV locale should *not* change it's character set in order
to be backwards compatible with old programs that may not work correctly with
UTF-8.

(b) A new locale should be created with the @euro extension and should use a
character set that is as close to the non-euro extension as possible e.g.
ISO-8859-15, but still has all of the required characters and the euro symbol.
This is for compatibility.

(c) New programs should be written to use and support UTF-8, and the UTF-8
locale should use the euro symbol.

Next steps:

- Verify that ISO-8859-15 contains all of BALTIC and a euro symbol.
- Create the lv_LV@euro locale using ISO-8859-15 and set the monetary value to
the euro symbol.

Distributions should default to lv_LV@euro for maximum compatibility with the
old BALTIC locale and use of the euro, or lv_LV.UTF-8 for full UTF-8 support.
Users should use lv_LV for maximum backwards compatibility with old programs.

Does anyone object to this? Is this too conservative? I'd like to develop some
kind of principle here so we can move forward with consensus from our users.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[carlos at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

--- Comment #15 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Carlos O'Donell from comment #14)
> Next steps:
> 
> - Verify that ISO-8859-15 contains all of BALTIC and a euro symbol.
> - Create the lv_LV@euro locale using ISO-8859-15 and set the monetary value
> to the euro symbol.

Lafriks, My apologies I see that you did verify that ISO-8859-15 does not
contain all of the required Latvian characters. In that case the only solution
here would be:

- Add "EUR" as the euro symbol of lv_LV.
- Verify that lv_LV.UTF-8 displays the euro symbol for monetary.

Users use lv_LV.UTF-8 when they want full UTF-8 support and the euro symbol,
while lv_LV will just print "EUR", all as you  suggested.

I think Chris' patch did all of that so he should post it for review.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[martin.pitt at ubuntu dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

Martin Pitt <martin.pitt at ubuntu dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martin.pitt at ubuntu dot com

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug localedata/16374] Change currency symbol in LC_MONETARY in lv_LV

[gunnarhj at ubuntu dot com]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 4698 bytes --]

https://sourceware.org/bugzilla/show_bug.cgi?id=16374

Gunnar Hjalmarsson <gunnarhj at ubuntu dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gunnarhj at ubuntu dot com

--- Comment #16 from Gunnar Hjalmarsson <gunnarhj at ubuntu dot com> ---
Created attachment 7813
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7813&action=edit
Ubuntu patch of the lv_LV locale definition file

Attached please find a patch which we are about to apply in Ubuntu.

$ LC_MONETARY=lv_LV.UTF-8 locale currency_symbol
€
$ LC_MONETARY=lv_LV locale currency_symbol
EUR

Seems to do its job.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-26355-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Sep 29 01:52:23 2014
Return-Path: <glibc-bugs-return-26355-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 11645 invoked by alias); 29 Sep 2014 01:52:22 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 11621 invoked by uid 89); 29 Sep 2014 01:52:19 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.5 required=5.0 testsºYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO: terra.astr.tohoku.ac.jp
Received: from terra.astr.tohoku.ac.jp (HELO terra.astr.tohoku.ac.jp) (130.34.119.200) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 29 Sep 2014 01:52:17 +0000
Received: from [172.22.11.211] (d22-011-211.astr.tohoku.ac.jp [172.22.11.211])	(authenticated bits=0)	by terra.astr.tohoku.ac.jp (3.14159265/1.41421356) with ESMTP id s8T1qDW4008786	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits\x128 verify=NOT)	for <glibc-bugs@sourceware.org>; Mon, 29 Sep 2014 10:52:13 +0900
Message-ID: <5428BB4E.6010009@astr.tohoku.ac.jp>
Date: Mon, 29 Sep 2014 01:52:00 -0000
From: Mohammad Akhlaghi <akhlaghi@astr.tohoku.ac.jp>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: glibc-bugs@sourceware.org
Subject: argp and parse_opt: question and possible feature request
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2014-09/txt/msg00277.txt.bz2
Content-length: 1750

Hi glibc (argp) maintainers,

This is my first mail to this mailing list, so sorry if this is off
topic or not actually a bug. It is just two questions that might also be
feature requests, if they do not already exist. If they do, I am sorry
for not noticing.

I am using the argp argument parser to parse the arguments to my
program. But there were two things I could not find in the manual which
would make my program much more easier and less buggy:

1. Accessing the long version of the option in pars_opt:
The short version of the option that is passed to pars_opt() is simply
the `key`, but I could not find if there is a way to access the long
format of the option that was called.

2. Checking for wrong usage of the equal sign (`=`).
In my simple tests, when I gave a short option with an equal sign or a
long option with spaces before and after the equal sign, I noticed that
the equal sign is passed in to parse_opt() as part of the argument. So I
added this tiny check at the beginning of parse_opt() to check for this
and warn the user:

if(arg && arg[0]=='=')
   argp_error(state, "Incorrect use of the equal sign (`=`). For short "
              "options, `=` should not be used and for long options,
              "there should be no space between the option, equal sign "
               "and value.");

So I wanted to to see if there is already a built in feature in argp
that can solve these two issues? If there isn't and the maintainers
agree, I think it is very useful to have these two features added.

I have learnt a lot from the glibc manual and made a lot of use of it in
my work. Thank you very much for creating and maintaining such a
fantastic library and its great documentation.

Thanks again,
Mohammad