public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/17998] New: ordinal indicators are lower-case, but islower disagrees
Date: Wed, 18 Feb 2015 22:32:00 -0000 [thread overview]
Message-ID: <bug-17998-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17998
Bug ID: 17998
Summary: ordinal indicators are lower-case, but islower
disagrees
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: aoliva at sourceware dot org
CC: libc-locales at sourceware dot org
As part of the update to Unicode 7, it was noticed that such characters as ª
(U+00AA) and º (U+00BA) were not regarded as lower-case letters by islower.
Unicode says they are, so islower is being fixed to agree.
There are further details about this in bug 14094 comment 34.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-27516-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Feb 19 00:20:39 2015
Return-Path: <glibc-bugs-return-27516-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 2731 invoked by alias); 19 Feb 2015 00:20:39 -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 2684 invoked by uid 48); 19 Feb 2015 00:20:33 -0000
From: "luto at mit dot edu" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/17802] The DNS resolver gets stuck when one nameserver is down
Date: Thu, 19 Feb 2015 00:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: network
X-Bugzilla-Version: 2.19
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: luto at mit dot edu
X-Bugzilla-Status: WAITING
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security?
X-Bugzilla-Changed-Fields:
Message-ID: <bug-17802-131-PrCuQAWbnw@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17802-131@http.sourceware.org/bugzilla/>
References: <bug-17802-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: 2015-02/txt/msg00251.txt.bz2
Content-length: 299
https://sourceware.org/bugzilla/show_bug.cgi?id\x17802
--- Comment #2 from Andy Lutomirski <luto at mit dot edu> ---
Unfortunately, I don't know how to test this, given that I was never able to
trigger it intentionally.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-02-18 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 22:32 aoliva at sourceware dot org [this message]
2015-02-20 22:36 ` [Bug localedata/17998] " 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-17998-131@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: 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).