Your message dated Mon, 27 Sep 2010 11:26:58 +0200 (CEST)
with message-id <alpine.deb.2.00.1009271124230.23...@cantor.unex.es>
has caused the   report #598168,
regarding tre-agrep fails to match strings in ISO-8859 files containing 
accented characters
to be marked as having been forwarded to the upstream software
author(s) Ville Laurikari <v...@iki.fi>

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
598168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Hello.

I received this from the Debian bug system:

---------- Forwarded message ----------
From: Douglas A. Augusto <daaugu...@gmail.com>
To: sub...@bugs.debian.org
Date: Mon, 27 Sep 2010 03:07:52 -0300
Subject: Bug#598168: tre-agrep fails to match strings in ISO-8859 files
    containing accented characters

Package: tre-agrep
Version: 0.8.0-2

Suppose we have an ISO-8859 file, lets call it iso-8859.txt, containing those
three lines below:

first line
something here á something else
last line

Notice that there is an accented letter (á, "a acute") in the second line. The
command

   % tre-agrep first iso-8859.txt

returns 'first line' (exit code = 0), which is correct. But both of the
following commands

   % tre-agrep something iso-8859.txt
   % tre-agrep last iso-8859.txt

return nothing (exit code = 1). For the sake of comparison, the standard
'grep' matches correctly all of those three commands above.

The file iso-8859.txt is just a minimal working example to demonstrate this
wrong behaviour of tre-agrep. The reported issue was found when I was running
something like 'find . | tre-agrep "string"' on a directory (ext4 filesystem)
containing file names with accented characters and I realized that something
was wrong, i.e, some files having "string" in their names were never shown
through tre-agrep.

---------------------------------------------------------------------------
Later, the submitter adds:
---------------------------------------------------------------------------
I forgot to say that tre-agrep works as expected if the presented 3-line
example file is encoded in utf-8.
---------------------------------------------------------------------------

So: Is this a bug, or is the file supposed to be always in UTF-8?
(Is this documented?)

Thanks.


--- End Message ---

Reply via email to