03-15-2012
I was thinking this might be a locale issue, therefore I suggested trying [[:lower:]] instead in post #4:
Quote:
[a-z] is case insensitive
You are encountering problems with locales. POSIX mandates that [a-z] uses the current locale's collation order - in C parlance, that means using strcoll(3) instead of strcmp(3). Some locales have a case-insensitive collation order, others don't.
Another problem is that [a-z] tries to use collation symbols. This only happens if you are on the GNU system, using GNU libc's regular expression matcher instead of compiling the one supplied with GNU sed. In a Danish locale, for example, the regular expression ^[a-z]$ matches the string ‘aa', because this is a single collating symbol that comes after ‘a' and before ‘b'; ‘ll' behaves similarly in Spanish locales, or ‘ij' in Dutch locales.
To work around these problems, which may cause bugs in shell scripts, set the LC_COLLATE and LC_CTYPE environment variables to ‘C'.
sed, a stream editor, 7 Reporting Bugs
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
i've reworked some code from an earlier post, and it isn't working as expected
i've simplified it to try and find the problem. i spent hours trying to figure out what is wrong, eventually thinking there was a bug in perl or a problem with my computer. but, i've tried it on 3 machines with the... (5 Replies)
Discussion started by: quantumechanix
5 Replies
2. UNIX for Dummies Questions & Answers
Hello,
When I run this script, here's what I get:
Searching ...
found 1111
2222
3333
.....
7777
.....
8888
9999 in 95_test
Search completed.
I expected only to see what number was found in the file, not including the ones not found.
Thanks for your help!
#!/bin/sh (1 Reply)
Discussion started by: SSims
1 Replies
3. Shell Programming and Scripting
I have two sripts running in bash. The first one uncompresses log files and moves them to a working directory using uncompress -c and > output to new directory. It then creates one control record to assure our search returns a record. It then calls or executes the second script, which is a grep for... (6 Replies)
Discussion started by: altamaha
6 Replies
4. Shell Programming and Scripting
Following script gives different results when triggered from Cron compared to when triggered from command line.
It is not able to assign values to some variables when triggered from cron.
Can any one help? Its a very simple script
Script -
#! /bin/ksh
sFile=$1
sEnv=$2
sWaitFile=$3... (1 Reply)
Discussion started by: sumeet
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I recently executed a find command that caused unexpected permission changes and we had to do a full system restore. Can someone please explain what this command would do?
find /staging/admin/scr * -exec chmod 755 '{}' +
It caused file permissions inside / to be modified strangely.
... (1 Reply)
Discussion started by: poornima
1 Replies
6. Shell Programming and Scripting
I created 3 files with the identical data as follows
dial-peer voice 9999 pots
trunkgroup CO
list outgoing Local
translation-profile outgoing LOCAL-7-DIGITS-NO-PREPEND-97
preference 2
shutdown
destination-pattern 9......$
forward-digits 7
dial-peer voice 10000 pots
... (6 Replies)
Discussion started by: popeye
6 Replies
7. Shell Programming and Scripting
Hi
I am comparing two files with comm -13 < (sort acc11.txt) < (sort acc12.txt) > output.txt
purpose: Get non matching records which are in acc12 but not in acc11...
TI am getting WRONG output.
Is there any constraints with record length with comm? The above files are the two consective ... (2 Replies)
Discussion started by: vedanta
2 Replies
8. Shell Programming and Scripting
Hi
I'm having hard time here with below script. If i run script manually i see expected results but, if i keep this script in cron job i'm getting unexpected results. Unexpected results means even though condition is true,cronjob returning output of else condition.
This script and cronjob... (2 Replies)
Discussion started by: buzzme
2 Replies
LEARN ABOUT CENTOS
setlocale
SETLOCALE(3) Linux Programmer's Manual SETLOCALE(3)
NAME
setlocale - set the current locale
SYNOPSIS
#include <locale.h>
char *setlocale(int category, const char *locale);
DESCRIPTION
The setlocale() function is used to set or query the program's current locale.
If locale is not NULL, the program's current locale is modified according to the arguments. The argument category determines which parts
of the program's current locale should be modified.
LC_ALL for all of the locale.
LC_COLLATE
for regular expression matching (it determines the meaning of range expressions and equivalence classes) and string collation.
LC_CTYPE
for regular expression matching, character classification, conversion, case-sensitive comparison, and wide character functions.
LC_MESSAGES
for localizable natural-language messages.
LC_MONETARY
for monetary formatting.
LC_NUMERIC
for number formatting (such as the decimal point and the thousands separator).
LC_TIME
for time and date formatting.
The argument locale is a pointer to a character string containing the required setting of category. Such a string is either a well-known
constant like "C" or "da_DK" (see below), or an opaque string that was returned by another call of setlocale().
If locale is "", each part of the locale that should be modified is set according to the environment variables. The details are implemen-
tation-dependent. For glibc, first (regardless of category), the environment variable LC_ALL is inspected, next the environment variable
with the same name as the category (LC_COLLATE, LC_CTYPE, LC_MESSAGES, LC_MONETARY, LC_NUMERIC, LC_TIME) and finally the environment vari-
able LANG. The first existing environment variable is used. If its value is not a valid locale specification, the locale is unchanged,
and setlocale() returns NULL.
The locale "C" or "POSIX" is a portable locale; its LC_CTYPE part corresponds to the 7-bit ASCII character set.
A locale name is typically of the form language[_territory][.codeset][@modifier], where language is an ISO 639 language code, territory is
an ISO 3166 country code, and codeset is a character set or encoding identifier like ISO-8859-1 or UTF-8. For a list of all supported
locales, try "locale -a", cf. locale(1).
If locale is NULL, the current locale is only queried, not modified.
On startup of the main program, the portable "C" locale is selected as default. A program may be made portable to all locales by calling:
setlocale(LC_ALL, "");
after program initialization, by using the values returned from a localeconv(3) call for locale-dependent information, by using the multi-
byte and wide character functions for text processing if MB_CUR_MAX > 1, and by using strcoll(3), wcscoll(3) or strxfrm(3), wcsxfrm(3) to
compare strings.
RETURN VALUE
A successful call to setlocale() returns an opaque string that corresponds to the locale set. This string may be allocated in static stor-
age. The string returned is such that a subsequent call with that string and its associated category will restore that part of the
process's locale. The return value is NULL if the request cannot be honored.
CONFORMING TO
C89, C99, POSIX.1-2001.
NOTES
Linux (that is, glibc) supports the portable locales "C" and "POSIX". In the good old days there used to be support for the European
Latin-1 "ISO-8859-1" locale (e.g., in libc-4.5.21 and libc-4.6.27), and the Russian "KOI-8" (more precisely, "koi-8r") locale (e.g., in
libc-4.6.27), so that having an environment variable LC_CTYPE=ISO-8859-1 sufficed to make isprint(3) return the right answer. These days
non-English speaking Europeans have to work a bit harder, and must install actual locale files.
SEE ALSO
locale(1), localedef(1), isalpha(3), localeconv(3), nl_langinfo(3), rpmatch(3), strcoll(3), strftime(3), charsets(7), locale(7)
COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
GNU
2008-12-05 SETLOCALE(3)