[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Findutils-patches] [PATCH] Explain that LC_MESSAGES determines the patt

From: James Youngman
Subject: [Findutils-patches] [PATCH] Explain that LC_MESSAGES determines the patterns used to interpret yes/no answers
Date: Sat, 17 May 2008 21:04:11 +0100

Signed-off-by: James Youngman <address@hidden>

Change made in response to Eric's suggestion that I explain LC_MESSAGES.

 doc/find.texi |   19 +++++++++++--------
 1 files changed, 11 insertions(+), 8 deletions(-)

diff --git a/doc/find.texi b/doc/find.texi
index cc6d58d..9b7ee99 100644
--- a/doc/find.texi
+++ b/doc/find.texi
@@ -2527,14 +2527,17 @@ Otherwise, run it, with  standard input redirected from
 The response to the prompt is matched against a pair of regular
-expressions to determine if it is a yes or no response.
-This regular expression is obtained from the system if the
-POSIXLY_CORRECT environment variable is set, or otherwise from
address@hidden's message translations.  If the system has no suitable 
address@hidden's own definition will be used.  In either case, the
-interpretation of the regular expression itself will be affected by
-the environment variables LC_CTYPE (character classes) and LC_COLLATE
-(character ranges and equivalence classes).
+expressions to determine if it is a yes or no response.  These regular
+expressions are obtained from the address@hidden@code{nl_langinfo} items 
YESEXPR and NOEXPR are used}
+if the POSIXLY_CORRECT environment variable is set and the system has
+such patterns available. 
+Otherwise, @code{find}'s message translations are used.  
+In either case, the LC_MESSAGES environment variable
+will determine the regular expressions used to determine if the answer
+is affirmative or negative.  The interpretation of the regular
+expressions themselves will be affected by the environment variables
+LC_CTYPE (character classes) and LC_COLLATE (character ranges and
+equivalence classes).
 @end deffn
 @deffn Action -ok command ;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]