Jim Meyering <[EMAIL PROTECTED]> writes: > Joe Wells <[EMAIL PROTECTED]> wrote: >> Jim Meyering <[EMAIL PROTECTED]> writes: >>> I've Cc'd [email protected], since that's the preferred bug-reporting >>> address. >> >> Then I have another bug to report. The man page for “grep” on my >> system (Ubuntu Dapper Drake) gives [EMAIL PROTECTED] as the only > > That was updated upstream in Nov of 2004. > Of course, it was after the release of grep-2.5.1, > and we're still waiting for 2.5.2.
Thanks for explaining! >> bug reporting address. (And there is no “grep.info” file installed. >> Is there such a file?) Is this a Debian/Ubuntu bug or a problem in >> the original grep source? > > There is most definitely a grep.info file. > If you wonder, check out the upstream site for grep: > http://savannah.gnu.org/projects/grep > > grep.info is generated from grep.texi, here: > http://cvs.savannah.gnu.org/viewvc/grep/doc/grep.texi?root=grep&view=log > > Maybe you haven't installed the documentation. Unfortunately, there appears to be no separate documentation package with the info file. :-( ☹ > In any case, it's a Debian/Ubuntu-specific problem. Indeed! >>>> By the way, I am using Ubuntu 6.06 LTS (“Dapper Drake”) with all >>> >>> I would consider upgrading. >> >> Of course. (But “LTS” is for “long term support”. One of its main >> advantages is not needing to upgrade.) > > You shouldn't expect all of the latest fixes for small things > like this in an older *stable* release. I don't. Are you suggesting I should not have reported the bug? >>> On some systems, the locale name is spelled slightly differently: >>> [get the proper spelling from the output of "locale -a"] >> >> (By the way, this is irrelevant to the bug in grep, but I believe the >> output of “locale -a” does not give the officially correct locale >> names. On my system, it says my locale name is “en_US.utf8”. My >> understanding from reading the standards documents is that the >> officially correct name is “en_US.UTF-8”. The use of “utf8” occurs >> because glibc has an internal compatibility hack where it downcases >> the charset name and removes hyphens from it before looking up the >> locale on disk and in data structures.) > > Maybe you'd prefer s/the proper/a useful/? > I just want to be sure that the locale setting I use will be > recognized by the system at hand, and don't care if it's officially correct. > In pedantic mode, this might be more to your liking: > > if you want to be sure to use a spelling that is recognized on your > system, one way is to choose from the list output by "locale -a". Yes, that makes sense. (Anyway, I would hope any system would always recognize the officially correct version, which is why I prefer to use it.) Thanks for your time in investigating my bug report! -- Joe
