From: Mike Frysinger <vapier@gentoo.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: LC_MONETARY: unknown character in field `currency_symbol’
Date: Sat, 23 Apr 2016 19:45:00 -0000 [thread overview]
Message-ID: <20160423194539.GN5369@vapier.lan> (raw)
In-Reply-To: <CAMKF1srrb0NDPgoswqvELK=ge-0PaZqLm+Ueq7Hic6DxOVx56w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3218 bytes --]
On 23 Apr 2016 02:26, Khem Raj wrote:
> On Thu, Apr 21, 2016 at 7:01 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> > On 21 Apr 2016 16:23, Khem Raj wrote:
> >> On Thu, Apr 21, 2016 at 2:13 PM, Mike Frysinger wrote:
> >> > On 21 Apr 2016 13:56, Khem Raj wrote:
> >> >> I am seeing these errors off late.
> >> >>
> >> >> /a/build/tmp-glibc/work/cortexa7hf-neon-vfpv4-oe-linux-gnueabi/glibc-locale/2.24-r0/locale-tree/usr/share/i18n/locales/tr_TR:4246: LC_MONETARY: unknown character in field `currency_symbol'
> >> >> /a/build/tmp-glibc/work/cortexa7hf-neon-vfpv4-oe-linux-gnueabi/glibc-locale/2.24-r0/locale-tree//usr/share/i18n/locales/tl_PH:87: LC_MONETARY: unknown character in field `currency_symbol’
> >> >>
> >> >> anyone else seeing them ?
> >> >
> >> > both work for me. is the host locale relevant ? are these the only
> >> > two locales complaining ?
> >>
> >> so far I only see these two. I am using cross-localedef to generate them.
> >
> > i'm not familiar with cross-localedef. does it work with localedef in
> > the tree ?
>
> I see issues when running make check building native as well.
>
> Generating locale si_LK.UTF-8: this might take a while...
> Generating locale tr_TR.ISO-8859-9: this might take a while...
> ../localedata/locales/tr_TR:4246: LC_MONETARY: unknown character in
> field `currency_symbol'
ok, so the issue is encoding. the output you posted earlier didn't
include the command line you were using, so i assumed UTF-8. these
are Unicode symbols and aren't in the various old encodings. here's
the full failing list:
$ localedef -f PT154 -i kk_KZ kk_KZ.PT154
kk_KZ:173: LC_MONETARY: unknown character in field `currency_symbol'
currency_symbol "₸"
$ localedef -f ISO-8859-1 -i en_PH en_PH.ISO-8859-1
en_PH:64: LC_MONETARY: unknown character in field `currency_symbol'
currency_symbol "₱"
$ localedef -f ISO-8859-9 -i ku_TR ku_TR.ISO-8859-9
tr_TR:4246: LC_MONETARY: unknown character in field `currency_symbol'
currency_symbol "₺"
$ localedef -f ISO-8859-1 -i tl_PH tl_PH.ISO-8859-1
tl_PH:87: LC_MONETARY: unknown character in field `currency_symbol'
currency_symbol "₱"
$ localedef -f ISO-8859-9 -i tr_TR tr_TR.ISO-8859-9
tr_TR:4246: LC_MONETARY: unknown character in field `currency_symbol'
currency_symbol "₺"
$ localedef -f ARMSCII-8 -i hy_AM hy_AM.ARMSCII-8
hy_AM:85: LC_MONETARY: unknown character in field `currency_symbol'
currency_symbol "֏"
$ localedef -f ISO-8859-9 -i tr_CY tr_CY.ISO-8859-9
tr_TR:4246: LC_MONETARY: unknown character in field `currency_symbol'
currency_symbol "₺"
$ localedef -f ISO-8859-8 -i he_IL he_IL.ISO-8859-8
he_IL:71: LC_MONETARY: unknown character in field `currency_symbol'
currency_symbol "₪"
$ localedef -f GEORGIAN-PS -i ka_GE
ka_GE.GEORGIAN-PS
ka_GE:72: LC_MONETARY: unknown character in field `currency_symbol'
currency_symbol "₾"
$ localedef -f ISO-8859-1 -i uz_UZ uz_UZ.ISO-8859-1
uz_UZ:209: LC_MONETARY: unknown character in field `currency_symbol'
uz_UZ:317: LC_ADDRESS: unknown character in field `country_name'
currency_symbol "soʻm"
country_name "Oʻzbekiston"
i'll follow up in your translit_neutral thread
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-04-23 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 20:56 Khem Raj
2016-04-21 21:13 ` Mike Frysinger
2016-04-21 23:23 ` Khem Raj
2016-04-22 2:01 ` Mike Frysinger
2016-04-23 9:27 ` Khem Raj
2016-04-23 19:45 ` Mike Frysinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160423194539.GN5369@vapier.lan \
--to=vapier@gentoo.org \
--cc=libc-alpha@sourceware.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).