Dear grep maintainer, the manpage-l10n project maintains a large number of translations of man pages both from a large variety of sources (including grep) as well for a large variety of target languages. During their work translators notice different possible issues in the original (english) man pages. Sometimes this is a straightforward typo, sometimes a hard to read sentence, sometimes this is a convention not held up and sometimes we simply do not understand the original. We use several distributions as sources and update regularly (at least every 2 month). This means we are fairly recent (some distributions like archlinux also update frequently) but might miss the latest upstream version once in a while, so the error might be already fixed. We apologize and ask you to close the issue immediately if this should be the case, but given the huge volume of projects and the very limited number of volunteers we are not able to double check each and every issue. Secondly we translators see the manpages in the neutral po format, i.e. converted and harmonized, but not the original source (be it man, groff, xml or other). So we cannot provide a true patch (where possible), but only an approximation which you need to convert into your source format. Finally the issues I'm reporting have accumulated over time and are not always discovered by me, so sometimes my description of the problem my be a bit limited - do not hesitate to ask so we can clarify them. I'm now reporting the errors for your project. If future reports should use another channel, please let me know. Man page: grep.1 Issue: IEPATTERNSE → I "Interpret IEPATTERNSE as Perl-compatible regular expressions " "(PCREs). This option is experimental when combined with the B<-z> (B<-\\^-" "null-data>) option, and B may warn of unimplemented features." -- Issue: BEpcrepatternE(3) → B(3) "B understands three different versions of regular expression syntax: " "``basic'' (BRE), ``extended'' (ERE) and ``perl'' (PCRE). In GNU B " "there is no difference in available functionality between basic and extended " "syntaxes. In other implementations, basic regular expressions are less " "powerful. The following description applies to extended regular " "expressions; differences for basic regular expressions are summarized " "afterwards. Perl-compatible regular expressions give additional " "functionality, and are documented in BEpcresyntaxE(3) and " "BEpcrepatternE(3), but work only if PCRE support is enabled." -- Issue: Not in "grep --help"; remove? "B<-y>" -- Issue: --invert-match is above, not below. "Suppress normal output; instead print a count of matching lines for each " "input file. With the B<-v>, B<-\\^-invert-match> option (see below), count " "non-matching lines." -- Dr. Helge Kreutzmann debian@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/