public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Petter Reinholdtsen <pere@hungry.com>
To: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Test sorting order for tr_TR
Date: Fri, 06 Aug 2004 22:50:00 -0000	[thread overview]
Message-ID: <2flzn57naop.fsf@saruman.uio.no> (raw)
In-Reply-To: <20040804185455.GJ10453@saruman.uio.no> (Petter Reinholdtsen's message of "Wed, 4 Aug 2004 20:54:55 +0200")

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]


[Petter Reinholdtsen]
> Oh.  It worked for me when I sent the patch a long time ago.  I'll
> look into why it fail.  Do you have any more details?

I got the output of the failing test from Ulrich.

> Perhaps I forgot to remove my patch to get the sorting order test to
> check _all_ characters in the file, and not ignore "\s+[:(;].*$"
> when testing the sorting order of locales.  That is the only related
> change I can think of, even though I'm pretty sure I tested the
> patch on a clean CVS tree.

Nope, that is not it.  I tested again on a "clean" CVS tree, and the
test still work for me.

I'm starting to suspect some transfer encoding issue with the UTF-8
file.  Here is the patch again, this time gzipped and included as an
attachment to avoid any mail transfer encoding problems.  I updated
the date of the changelog entry.

2004-08-07  Petter Reinholdtsen  <pere@hungry.com>

	* Makefile (test-input): Add tr_TR.UTF-8 sorting test.  Test case
	for BZ #19.
	* tr_TR.in: New file


[-- Attachment #2: tr_TR UTF-8 sorting test data --]
[-- Type: application/octet-stream, Size: 1060 bytes --]

  reply	other threads:[~2004-08-06 22:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-18  7:47 Petter Reinholdtsen
2004-07-26 22:09 ` Petter Reinholdtsen
2004-07-26 22:43   ` Ulrich Drepper
2004-07-26 22:47     ` Petter Reinholdtsen
2004-08-03  3:16 ` Ulrich Drepper
2004-08-04 18:54   ` Petter Reinholdtsen
2004-08-06 22:50     ` Petter Reinholdtsen [this message]
2004-08-07 23:38       ` Ulrich Drepper

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=2flzn57naop.fsf@saruman.uio.no \
    --to=pere@hungry.com \
    --cc=libc-hacker@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).