src/usr.bin/tr/tr.1 - diff

Return to tr.1 CVS log

Up to [local] / src / usr.bin / tr

Diff for /src/usr.bin/tr/tr.1 between version 1.3 and 1.4

version 1.3, 1998/10/30 00:24:40

version 1.4, 1999/04/30 06:24:25

Line 69

.Bl -tag -width Ds

.It Fl c

Complements the set of characters in

.Ar string1 ,

.Ar string1 ;

that is ``-c ab'' includes every character except for ``a'' and ``b''.

for instance,

.Dq -c\ ab

includes every character except for

.Dq a

and

.Dq b .

.It Fl d

The

.Fl d

Line 134

Line 139

Any character not described by one of the following conventions

represents itself.

.It \eoctal

A backslash followed by 1, 2 or 3 octal digits represents a character

A backslash followed by 1, 2, or 3 octal digits represents a character

with that encoded value.

To follow an octal sequence with a digit as a character, left zero-pad

the octal sequence to the full 3 octal digits.

Line 189

Line 194

\." and vice-versa) is specified in the same relative position in

\." .Ar string1 .

\." .Pp

With the exception of the ``upper'' and ``lower'' classes, characters

With the exception of the

.Dq upper

and

.Dq lower

classes, characters

in the classes are in unspecified order.

In the ``upper'' and ``lower'' classes, characters are entered in

In the

.Dq upper

and

.Dq lower

classes, characters are entered in

ascending order.

.Pp

For specific information as to which ASCII characters are included

Line 205

Line 218

there is a secondary ordering within the equivalence class, the characters

are ordered in ascending sequence.

Otherwise, they are ordered after their encoded values.

An example of an equivalence class might be ``c'' and ``ch'' in Spanish;

An example of an equivalence class might be

.Dq c

and

.Dq ch

in Spanish;

English has no equivalence classes.

.It [#*n]

Represents

Line 224

Line 241

.Ar string1 .

.Ar n

has a leading zero, it is interpreted as an octal value, otherwise,

has a leading zero, it is interpreted as an octal value; otherwise,

it's interpreted as a decimal value.

.El

.Pp

Line 248

Line 265

.D1 Li "tr -cd \*q[:print:]\*q < file1"

.Sh COMPATIBILITY

System V has historically implemented character ranges using the syntax

``[c-c]'' instead of the ``c-c'' used by historic BSD implementations and

.Dq [c-c]

instead of the

.Dq c-c

used by historic BSD implementations and

standardized by POSIX.

System V shell scripts should work under this implementation as long as

the range is intended to map in another range, i.e. the command

``tr [a-z] [A-Z]'' will work as it will map the ``['' character in

.Dq tr\ [a-z]\ [A-Z]

will work as it will map the

.Dq [

character in

.Ar string1

to the ``['' character in

to the

.Dq [

character in

.Ar string2 .

However, if the shell script is deleting or squeezing characters as in

the command ``tr -d [a-z]'', the characters ``['' and ``]'' will be

the command

included in the deletion or compression list which would not have happened

.Dq tr\ -d\ [a-z] ,

the characters

.Dq [

and

.Dq \]

will be

included in the deletion or compression list, which would not have happened

under an historic System V implementation.

Additionally, any scripts that depended on the sequence ``a-z'' to

Additionally, any scripts that depended on the sequence

represent the three characters ``a'', ``-'' and ``z'' will have to be

.Dq a-z

rewritten as ``a\e-z''.

to represent the three characters

.Dq a ,

.Dq - ,

and

.Dq z

will have to be rewritten as

.Dq a\e-z .

.Pp

The

.Nm tr

utility has historically not permitted the manipulation of NUL bytes in

its input and, additionally, stripped NUL's from its input stream.

its input and, additionally, has stripped NUL's from its input stream.

This implementation has removed this behavior as a bug.

.Pp

The

.Nm tr

utility has historically been extremely forgiving of syntax errors,

utility has historically been extremely forgiving of syntax errors:

for example, the

.Fl c

and

Line 293

Line 330

.Ar string1

is permitted by POSIX but is not required.

Shell scripts attempting to be portable to other POSIX systems should use

the ``[#*]'' convention instead of relying on this behavior.

the

.Dq [#*]

convention instead of relying on this behavior.