public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "bensberg at justemail dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/11561] Collation characters represented by internal name instead of character sequence
Date: Sun, 03 Feb 2013 15:38:00 -0000	[thread overview]
Message-ID: <bug-11561-132-EgGNIY0hAM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11561-132@http.sourceware.org/bugzilla/>

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

Benno Schulenberg <bensberg at justemail dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bensberg at justemail dot
                   |                            |net

--- Comment #1 from Benno Schulenberg <bensberg at justemail dot net> 2013-02-03 15:37:37 UTC ---
> POSIX especially mentions [[.ch.]] in the example instead of [[.ch-digraph.]]
> so this is a bug in glibc.  It shouldn't be hard to fix it in regcomp.

The easiest fix would be, in my opnion, to rename all the
collation-element names for digraphs from their hyphenated
form to the non-hyphenated form.  But a few users may have
gotten used to using the hyphented forms, working around
this bug in glibc.  They would be pissed.  So for quite a
while both forms will have to recognized.  Attached patch
is an attempt to do this -- when the user specifies [.xx.],
it will first try to look up "xx" in the table of collation
elements, and when that fails, it will look up "x-x".  Is
this what you had in mind, Paolo?

-- 
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.


  parent reply	other threads:[~2013-02-03 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11561-132@http.sourceware.org/bugzilla/>
2011-07-08 20:19 ` vapier at gentoo dot org
2013-02-03 15:38 ` bensberg at justemail dot net [this message]
2013-02-03 15:42 ` bensberg at justemail dot net
2013-02-12  8:27 ` schwab@linux-m68k.org
2014-02-16 17:44 ` jackie.rosen at hushmail dot com
2014-05-28 19:44 ` schwab at sourceware dot org
2014-06-30 18:14 ` 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-11561-132-EgGNIY0hAM@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs-regex@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).