[Bug libc/15736] mismatch between strcasecmp and toupper/tolower in tr_TR.iso88599 locale

public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed

From: "jrnieder at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15736] mismatch between strcasecmp and toupper/tolower in tr_TR.iso88599 locale
Date: Mon, 15 Jul 2013 06:38:00 -0000	[thread overview]
Message-ID: <bug-15736-131-Ir0POgWvch@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15736-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15736

Jonathan Nieder <jrnieder at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jrnieder at gmail dot com

--- Comment #1 from Jonathan Nieder <jrnieder at gmail dot com> ---
All that POSIX says on this subject is

        When the LC_CTYPE category of the current locale is from the
        POSIX locale, strcasecmp() and strncasecmp() shall behave as
        if the strings had been converted to lowercase and then a byte
        comparison performed. Otherwise, the results are unspecified.

I guess that makes it a matter of taste what the results should be. :(

I would have expected the following:

        10 INF
        10 ıNF
        10 ınF
        10 ınf
        01 inf
        01 İnf
        01 İNf
        01 İNF

That's because i and ı are different letters in Turkish, whose
capitalized equivalents are İ and I.

Is there some standard that makes sense of this stuff?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-19134-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jul 15 08:19:33 2013
Return-Path: <glibc-bugs-return-19134-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 30782 invoked by alias); 15 Jul 2013 08:19:33 -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 28452 invoked by uid 48); 15 Jul 2013 08:17:29 -0000
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15736] mismatch between strcasecmp and toupper/tolower in tr_TR.iso88599 locale
Date: Mon, 15 Jul 2013 08:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.17
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vincent-srcware at vinc17 dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-15736-131-87cJSSVa7x@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-15736-131@http.sourceware.org/bugzilla/>
References: <bug-15736-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-07/txt/msg00075.txt.bz2
Content-length: 738

http://sourceware.org/bugzilla/show_bug.cgi?id=15736

--- Comment #2 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> ---
(In reply to Jonathan Nieder from comment #1)
> I would have expected the following:
> 
>         10 INF
>         10 ıNF
>         10 ınF
>         10 ınf
>         01 inf
>         01 İnf
>         01 İNf
>         01 İNF
> 
> That's because i and ı are different letters in Turkish, whose
> capitalized equivalents are İ and I.

Yes, you're right. I got confused by the fact strcasecmp currently regards as
the ASCII letters i and I as being the same, but it shouldn't.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-19135-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jul 15 09:02:14 2013
Return-Path: <glibc-bugs-return-19135-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 398 invoked by alias); 15 Jul 2013 09:02:14 -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 30360 invoked by uid 48); 15 Jul 2013 09:00:11 -0000
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15736] mismatch between strcasecmp and toupper/tolower in tr_TR.iso88599 locale
Date: Mon, 15 Jul 2013 09:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.17
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vincent-srcware at vinc17 dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-15736-131-Nqb1ZoXwuc@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-15736-131@http.sourceware.org/bugzilla/>
References: <bug-15736-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-07/txt/msg00076.txt.bz2
Content-length: 639

http://sourceware.org/bugzilla/show_bug.cgi?id=15736

--- Comment #3 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> ---
(In reply to Jonathan Nieder from comment #1)
> Is there some standard that makes sense of this stuff?

Unicode actually specifies several forms of case-insensitive (caseless)
matching. It is more complex than POSIX minimal requirements as normalization
should be used (but this makes sense and may be preferable IMHO). Otherwise
default caseless matching could be chosen. See:

  http://www.unicode.org/reports/tr21/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-19136-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jul 15 09:18:17 2013
Return-Path: <glibc-bugs-return-19136-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 20038 invoked by alias); 15 Jul 2013 09:18:17 -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 17704 invoked by uid 48); 15 Jul 2013 09:16:14 -0000
From: "taem at linukz dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/15578] The kk_KZ locale update
Date: Mon, 15 Jul 2013 09:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: localedata
X-Bugzilla-Version: 2.18
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: taem at linukz dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-15578-131-TMnlVAxzit@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-15578-131@http.sourceware.org/bugzilla/>
References: <bug-15578-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: 2013-07/txt/msg00077.txt.bz2
Content-length: 218

http://sourceware.org/bugzilla/show_bug.cgi?id\x15578

--- Comment #2 from Timur Birsh <taem at linukz dot org> ---
Hi,

Any news?

Thanks.

--
You are receiving this mail because:
You are on the CC list for the bug.

next prev parent reply	other threads:[~2013-07-15  6:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 17:52 [Bug libc/15736] New: " vincent-srcware at vinc17 dot net
2013-07-15  6:38 ` jrnieder at gmail dot com [this message]
2013-07-15 15:36 ` [Bug libc/15736] " vincent-srcware at vinc17 dot net
2013-07-16 19:16 ` schwab@linux-m68k.org
2013-08-27 10:27 ` schwab@linux-m68k.org
2014-06-13  9:24 ` fweimer at redhat dot com
2021-08-19 15:34 ` fweimer 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=bug-15736-131-Ir0POgWvch@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).