There are two terminal capabilities that exist just to explain the proper
way to obey the padding specifications in all the command string
capabilities. One, `pc', must be obeyed by all termcap-using
programs.

`pb'

Numeric value, the lowest baud rate at which padding is actually
needed. Programs may check this and refrain from doing any padding at
lower speeds.

`pc'

String of commands for padding. The first character of this string is
to be used as the pad character, instead of using null characters for
padding. If `pc' is not provided, use null characters. Every
program that uses termcap must look up this capability and use it to
set the variable PC that is used by tputs.
See section Padding.

Some termcap capabilities exist just to specify the amount of padding that
the kernel should give to cursor motion commands used in ordinary
sequential output.

`dC'

Numeric value, the number of msec of padding needed for the
carriage-return character.

`dN'

Numeric value, the number of msec of padding needed for the newline
(linefeed) character.

`dB'

Numeric value, the number of msec of padding needed for the backspace
character.

`dF'

Numeric value, the number of msec of padding needed for the formfeed
character.

`dT'

Numeric value, the number of msec of padding needed for the tab
character.

In some systems, the kernel uses the above capabilities; in other systems,
the kernel uses the paddings specified in the string capabilities
`cr', `sf', `le', `ff' and `ta'. Descriptions of
terminals which require such padding should contain the `dC' ...
`dT' capabilities and also specify the appropriate padding in the
corresponding string capabilities. Since no modern terminals require
padding for ordinary sequential output, you probably won't need to do
either of these things.