* David Haller schrieb am 07.Okt.2002:
$ echo 'Täst' | tr '[:lower:][:upper:]' '[:upper:][:lower:]' tÄST $ echo $LANG en_US.ISO_8859-15
d.h. tr kann sogar bei en_US damit umgehen!
imho ist das ein flsaches Verhalten.
Aus 'tr --help': ==== Usage: tr [OPTION]... SET1 [SET2] [..] SETs are specified as strings of characters. Most represent themselves. Interpreted sequences are: [..] CHAR1-CHAR2 all characters from CHAR1 to CHAR2 in ascending order [CHAR*] in SET2, copies of CHAR until length of SET1 [CHAR*REPEAT] REPEAT copies of CHAR, REPEAT octal if starting with 0 [:alnum:] all letters and digits [:alpha:] all letters [:blank:] all horizontal whitespace [:cntrl:] all control characters [:digit:] all digits [:graph:] all printable characters, not including space [:lower:] all lower case letters [:print:] all printable characters, including space [:punct:] all punctuation characters [:space:] all horizontal or vertical whitespace [:upper:] all upper case letters [:xdigit:] all hexadecimal digits [=CHAR=] all characters which are equivalent to CHAR
Funktioniert aber auch nur bei [:lower:] und [:upper:] Was anderes wäre ja auch merkwürdig, was soll ein tr [:cntr:] [:digit:] auch machen? Bernd -- ACK = ACKnowledge = Zustimmung | NAC = No ACknowledge = keine Zustimmung DAU = Dümmster Anzunehmender User | LOL = Laughing Out Loud = Lautes Lachen IIRC = If I Remember Correctly = Falls ich mich richtig erinnere OT = Off Topic = Am Thema (der Liste) vorbei |Zufallssignatur 11