public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "romke at estrefa dot pl" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug localedata/388] New: localedata/locales/pl_PL has incorrect LC_COLLATE <space> handling
Date: Fri, 17 Sep 2004 12:10:00 -0000 [thread overview]
Message-ID: <20040917121026.388.romke@estrefa.pl> (raw)
In 54th line of localedata/locales/pl_PL is described ordering algorithm as it
shoud be:
% 1. Spaces and hyphen (but not soft
% hyphen) before punctuation
% characters, punctuation characters
... and so on
but in 290th line it's written:
"<U0020> IGNORE;IGNORE;IGNORE;<U0020>"
so <space> (U0020) is changed into IGNORE and ignored in sort order as it should
NOT!
--
Summary: localedata/locales/pl_PL has incorrect LC_COLLATE
<space> handling
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: localedata
AssignedTo: pere at hungry dot com
ReportedBy: romke at estrefa dot pl
CC: glibc-bugs at sources dot redhat dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://sources.redhat.com/bugzilla/show_bug.cgi?id=388
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2004-09-17 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-17 12:10 romke at estrefa dot pl [this message]
2004-09-17 12:12 ` [Bug localedata/388] " romke at estrefa dot pl
2005-01-29 14:20 ` barbier at linuxfr dot org
2005-10-14 23:03 ` drepper at redhat dot com
2005-10-14 23:54 ` romke at estrefa dot pl
2006-04-10 16:59 ` mfabian at suse dot de
2006-05-01 17:26 ` drepper at redhat dot com
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=20040917121026.388.romke@estrefa.pl \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=glibc-bugs@sources.redhat.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).