Some terminals like xterm allow to redefine the colors via resource files or dynamically, and if it's exposed correctly in the terminfo entry for $TERM, you can do it with:
tput initc 4 1000 0 0
Change ANSI color 4 (normally blue) to RGB (1000, 0 0), that is bright red.
If the terminal doesn't support redefining colours (see infocmp -1 | grep initc
), you can also, for applications that use terminfo, trick them into sending different escape sequences to request colour 4 (blue).
infocmp -x > terminal.info
Edit terminal.info
, replace the name of the terminal with something like "myterm", and edit the "setab" property (set ANSI background).
Instead of
setab=\E[4%p1%dm
That is:
tput setab 4
sends ^[[44m, change it to:
setab=\E[4%?%p1%{4}%=%t1%e%p1%d%;m
The %? ....
, is an if-then-else, to say send "1" when asked for "4" and the requested one otherwise.
So
tput setab 4
will send ^[[41m
, (red) and tput setab 5
will send ^[[45m
Then, compile it with:
TERMINFO=$HOME/.terminfo tic -x terminal.info
and use it as:
TERMINFO=$HOME/.terminfo TERM=myterm the-application-to-trick
That only works if the application uses the terminfo database to send sequences to the terminal.
I found this paragraph in a withdrawal letter for FIPS which might be why it was withdrawn:
excerpt from withdrawal letter
It is no longer necessary for the government to mandate standards
that duplicate industry standards. Federal government departments and
agencies are directed by the National Technology Transfer and
Advancement Act of 1995 (P.L. 104-113), to use technical industry
standards that are developed in voluntary consensus standards bodies.
There is also this letter/email:
From: "richard l. hogan"
<Richard=L.=Hogan%dpi%hqnmd@mcmcban6.er.usgs.gov> Date: Tue, 29 Oct
96 9:20:26 CST Subject: Withdrawal of FIPS
Which discusses that the NIST and the Dept. of Commerce were dropping national designations for things such as ANSI 3.64 when they already had a international designation (ISO).
excerpt from that letter/email
One of the pieces of legislation that, according to NIST and the
Department of Commerce, enabled the FIPS program was rescinded this
year. The law - sometimes referred to as the Brooks Act - contained
specific requirements for establishing uniform standards for
information processing in the Federal government and for making those
standards mandatory in Federal procurement actions. OMB Circular A-119
further clarified that mandatory Federal standards took precedence
over voluntary national and international standards. Now, as a result
of treaty negotiations making the Untied States part of the World
Trade Organization, the Books Act has been replaced with new
legislation that requires Federal agencies to consider voluntary
international and national standards FIRST in procurement actions and
to cite Federal standards only when no appropriate international or
national standards exist.
In many cases FIPS have international (ISO) or national (ANSI)
standard equivalents. For example, FIPS 123 (Data Descriptive Format
for Information Interchange) is also ISO-8211. The change in
legislation requires Federal procurements to now cite ISO-8211.
Previously, we were required to cite FIPS- 123. As a result of this
change, NIST has recognized an opportunity to make government "work
better and cost less" by withdrawing any FIPS that already has an
equivalent ANSI or ISO specification or any FIPS that is not
mandatory; i.e., is just a guideline. What remains on the "active"
FIPS list are mandatory Federal standards which currently have no ANSI
or ISO equivalent; for example, the Spatial Data Transfer Standard
(FIPS 173-1) and the Government Information Locator Service (FIPS
192).
NIST is not withdrawing important standards like Pascal, FIPS 109;
SGML, FIPS 152; or Hydrologic Unit Codes, FIPS 103. The proper way to
look at this action is that NIST is withdrawing the Federal
designation of these standards in favor or their national or
international standards designations; ANSI X3.97-1993 for FIPS 103,
ISO 8879 for FIPS 152, and ANSI X3.145-1986 for FIPS 103. From a user
point of view, this action by NIST is nothing more than a way to
assure the designation change required by the new legislation.
I would interpret this as follows: Since ECMA-48 already covered the standard at an international level there was no need to create redundant standards within ANSI.
Best Answer
Not sure if you're asking solely about presentations that were viewed on a terminal or something else controlled by a computer, or were generated via computer, but I'll answer the latter.
Back in the 1970's, most UNIX users created papers and vugraphs and man pages using troff, which was both a markup language and a program to translate that markup language into a format that could be used by printers.
nroff
was a version oftroff
that took the same input language, but its output consisted of fixed-width ASCII characters. In many cases, it was sufficient for someone preparing a presentation to usenroff
, print the resulting document on a lineprinter (with fanfold paper), then use a photocopier to copy it onto ordinary paper or vugraph material.Documents that needed to have multiple fonts were sent to phototypesetters and, later, laser printers. At Bell Labs, for instance,
troff
would send its output, using lpr, to a GCOS system in a large comp center that drove a phototypesetter.lpr
used the GECOS field in/etc/passwd
, which contained one's name and other identifying data (such as department and bin number) so that the job could be billed and routed appropriately.A set of tools grew up around
troff/nroff
, including the tbl preprocessor to format tables and the eqn preprocessor to format mathematical equations. Since the troff language was rather low-level (for instance, to know when to output a footer, you had to set a trap using.wh
("when") that would be activated when the output was, say, 10.5 inches from the top of the current page), macro packages such as ms andmm
were written to make writing the markup easier.ditroff
was a followon totroff
that could handle additional types of printers (such as Postscript laser printers); it separatedtroff
(andnroff
) into a front end and a variety of device-dependent back ends, connected with a pipe.