|
tr (2365 words) |
 | 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. |
| tr MAN Page (1179 words) |
| Although GNU `tr' does not support the System V syntax that uses square brackets to enclose ranges, translations specified in that format will still work as long as the brackets in STRING1 correspond to identical brackets in STRING2. |
| Therefore, they are not fully implemented in GNU `tr'; each character's equivalence class consists only of that character, which is of no particular use. |
| For example, these two commands are equivalent: tr aaa xyz tr a z A common use of `tr' is to convert lowercase characters to uppercase. |
Feeds |
Contact