| |
| |
tr |
 | | The tr output shall be identical to the input, with the exception of the specified transformations. |
 | | It was pointed out that, while tr does employ some syntactical elements from REs, the aim of tr is quite different; ranges, for example, do not have a similar meaning (``any of the chars in the range matches", versus "translate each character in the range to the output counterpart"). |
 | | This meant that historical practice of being able to specify tr -d\200-\377 (which would delete all bytes with the top bit set) would have no effect because, in the C locale, bytes with the values octal 200 to octal 377 are not characters. |
| www.opengroup.org /onlinepubs/009695399/utilities/tr.html (2365 words) |
|