public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pasky at ucw dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/10580] New file for hr_HR localedata Date: Sun, 17 Feb 2013 00:13:00 -0000 [thread overview] Message-ID: <bug-10580-131-lgth76PGpp@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-10580-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=10580 --- Comment #13 from Petr Baudis <pasky at ucw dot cz> 2013-02-17 00:13:28 UTC --- Keld, of course using the newer standard makes sense; however, I'm not sure what do you mean by "further implement" and how that differs from what I wrote. If you are interested in discussing this further, I propose we move the discussion to the mailing list where more people could follow it. (Note that I myself don't have the time to pursue the issue itself, so it makes sense to talk more about it only if someone intends to do anything about it.) Dragan, I'm sorry, I missed the LC_COLLATE syntax error. Any reason why we cannot use the unicode entity there instead? Also, I'm wondering, how was testing of this locale done if it doesn't even compile with glibc's localedef now? And which of the people that provided support for the new locale actually tested it rather than just embraced the idea? -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2013-02-17 0:13 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-10580-131@http.sourceware.org/bugzilla/> 2013-02-16 0:40 ` pasky at ucw dot cz 2013-02-16 18:49 ` keld at keldix dot com 2013-02-16 19:11 ` invisible@hidden-city.net 2013-02-17 0:13 ` pasky at ucw dot cz [this message] 2013-02-17 0:42 ` keld at keldix dot com 2013-02-17 13:56 ` invisible@hidden-city.net 2013-02-17 15:05 ` pasky at ucw dot cz 2013-02-17 18:17 ` invisible@hidden-city.net 2013-02-17 18:23 ` pasky at ucw dot cz 2013-02-19 6:33 ` invisible@hidden-city.net 2013-02-19 6:51 ` invisible@hidden-city.net 2013-02-19 11:17 ` invisible@hidden-city.net 2013-04-07 3:22 ` invisible@hidden-city.net 2013-05-01 17:23 ` invisible@hidden-city.net 2014-06-15 8:03 ` semiRocket at gmail dot com 2014-06-16 16:50 ` fweimer at redhat dot com 2009-08-31 22:54 [Bug localedata/10580] New: " invisible at hidden-city dot net 2009-08-31 22:57 ` [Bug localedata/10580] " invisible at hidden-city dot net 2009-08-31 23:00 ` invisible at hidden-city dot net 2009-09-01 2:46 ` tvujec at redhat dot com 2009-09-01 2:47 ` tvujec at redhat dot com 2009-09-01 12:15 ` invisible at hidden-city dot net 2009-09-03 1:07 ` invisible at hidden-city dot net 2009-09-06 22:11 ` invisible at hidden-city dot net 2009-09-06 22:13 ` invisible at hidden-city dot net 2009-10-29 23:31 ` drepper at redhat dot com 2009-10-30 1:35 ` invisible at hidden-city dot net
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-10580-131-lgth76PGpp@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).