From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/22517] et_EE LC_COLLATE does not use copy "iso14651_t1"
Date: Thu, 22 Feb 2018 08:08:00 -0000 [thread overview]
Message-ID: <bug-22517-716-GIPFjBrffg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22517-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22517
--- Comment #6 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to Elan Ruusamäe from comment #4)
> de9661d6beb74b177cef07fe44c90c4e48a983a2
>
> broke localedb gen: https://sourceware.org/bugzilla/show_bug.cgi?id=22861
>
> $ localedb-gen --locales et_EE.UTF-8/UTF-8 -d .
> Generating et_EE.UTF-8 using charset UTF-8... failed to set locale!
> [error] LC_COLLATE: missing `reorder-end' keyword
> failed to set locale!
> [error] no output file produced because errors were issued
>
> (localedb-gen invokes `localedef -f UTF-8 -i et_EE et_EE.UTF-8`)
I fixed this now.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-02-22 8:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 12:41 [Bug localedata/22517] New: " maiku.fabian at gmail dot com
2017-11-29 12:41 ` [Bug localedata/22517] " maiku.fabian at gmail dot com
2017-12-05 11:36 ` maiku.fabian at gmail dot com
2017-12-05 16:11 ` cvs-commit at gcc dot gnu.org
2017-12-05 16:55 ` maiku.fabian at gmail dot com
2018-02-19 11:04 ` glen@pld-linux.org
2018-02-21 15:37 ` cvs-commit at gcc dot gnu.org
2018-02-22 8:08 ` maiku.fabian at gmail dot com [this message]
2018-03-13 1:19 ` cvs-commit at gcc dot gnu.org
2018-03-31 12:31 ` jeremip11 at gmail dot com
2018-06-01 16:52 ` cvs-commit at gcc dot gnu.org
2018-08-01 5:58 ` cvs-commit at gcc dot gnu.org
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=bug-22517-716-GIPFjBrffg@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.org \
/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).