This is an instruction sheet with appendices for the program
TYPET. TYPET is a BASIC program written to aid anyone in
processing a file for a typesetter. This documentation contains
the function of the program, a brief explanation of the methods
used, some hints on early preparation, how to process a file,
and a list of a special case. There are several appendices
included to aid in seeing what this program really does.
FUNCTION
The purpose of TYPET is to allow a person who is untrained
in typesetting to accurately prepare a body of text for
typesetting. The concept used is one of substitution, that is,
a complicated typesetting code is substituted for a simple user
installed code. The program also processes each line of the
text to make sure that the text does not contain any undesirable
characteristics such as a double space or leading blanks.
WHAT DOES IT DO AND HOW?
The program processes each line of the text in three ways:
1) the text is pulled over to the left margin; 2) all double
spaces are reduced to a single space; and, 3) each line is
examined for typesetting code flags. Any flag is simply
something designed to get your attention. We use flags to mark
buried cable, road hazards, and special sales on used cars.
In this case, a flag is no different. TYPET searches for a
specific flag and when this flag gets the program's attention,
it is processed. The flag used here is the "close square
bracket" (]). When ever TYPET finds a "]" in the text it
examines the character immediately to the right of the flag.
If the character has a meaning, it is processed. Otherwise,
that flag is ignored,and searching for more flags proceeds. If
the character behind the flag means something, then both the
flag and the character behind it will be substituted with a
typesetting code.
There are some limitations that must be followed while using
this program. First of all, the character following the flag
must be limited to the digits (1 through 9), upper case letters
(A through Z), and lower case letters (a through z). This
allows 64 codes to be entered. Any other character following
the flag will be ignored. Perhaps an example will prove
helpful at this point. Suppose that the following line was
being processed by TYPET:
The quick brown fox [really he was red] bumped the lazy dog.
******
TYPET Documentation - 2 -
User instructions
After processing the line would look like this:
The quick brown fox [really he was red] bumped the lazy dog.
But wait, there was a "]" in that line, it should be processed
with something right? Wrong. Notice that the character
immediately behind the "]" is a space, not a digit or letter.
Therefore, just ignore it and go on. Do notice that the line
was pulled over to the left margin. If the sentence had read:
"]1Now here this]2", [the captain always yelled].
After processing it would read:
"*FT4Now here this*FT3", [the captain always yelled].
Notice that *FT4 and *FT3 were substituted for ]1 and ]2, the
text is on the left margin, and the double space between the
first comma and [ is now a single space. The "]." was ignored.
This assumes that the codes for ]1 and ]2 were previously
defined as *FT4 and *FT3, respectively.
The term "previously defined" implies that some
preparation and forethought have gone into what you want
typeset. First of all, you need to know the typesetting codes,
what they do and where they need to go. This does not mean you
need to know everything about typesetting, just visit your
friendly typesetting institution and they will tell you what
you need to know. Secondly, you need to assign the flags to
various codes so that they will be substituted in the right
fashion. So, now let's go through a typical example of getting
all of the knowledge we need first, then apply it.
EARLY PREPARATION
If you visit your friendly typesetting person, you will learn
some wonderful things. First, some things have to be done on
____
their machine. Things like placing figures, photos, page lay
out, etc., are left for them to do, TYPET will not attempt to do
that. Secondly, you will learn that the typesetting codes can
be kind of complicated and confusing. Listed below are some
codes that have been used:
*SZ12*LS130*FT7*LL4200 -- this means start with size 12 point,
a line size of 130 something-or-others, font 7, and a line
length of 4200 something-elses;
******
TYPET Documentation - 3 -
User instructions
*QR -- move the text to the right margin;
*SZ18*LS200*FT7 -- size 18 point, line size 200, font 7;
*SZ14*LS150*FT7 -- size 14 point, line size 150, font 7.
These codes plus many more can used frequently within a single
document. It would be very tedious to have to type each one of
these codes in the right spot without making an error. But now
that you have them, you can substitute them where necessary.
Next, you must determine the flags that will be translated
into these codes. TYPET will determine this for you. From the
AMOS dot, type RUN TYPET and you will be placed in the
typesetting code input mode. You will be asked to enter these
codes starting with ]1 and going through ]9, followed by ]A
going through ]Z, and ]a going through ]z. You need not enter
all 64 codes, if you only have four, just enter a return at the
prompt for the next code and the entry session will be ended.
Upon completion of the input session, you will be asked if you
want a printout of the codes. If this is the first time these
codes have been entered (and you should only have to enter them
once), answer "y" to this question. TYPET will now do two
things for you. First it will create a file called "CODES.LST"
(see Appendix A.) that you can use for your reference while you
go through the text file adding flags. It is suggested that
you describe what these flags are to do in the white space
following the flag number. Secondly, TYPET creates a file
called "CODES.CMD" that has all of these codes plus the
commands necessary to invoke TYPET from AMOS (See Appendix B.).
In other words, entering the codes is now automated so you
don't have to type them.
After the order of the codes has been assigned, go through
your text file and place the flags in the appropriate locations
to do what is desired.
PROCESSING A FILE
Now that the codes and flags have been assigned, and you
have edited your text file to insert the appropriate flags in
the right spots, you are ready to process your file for
typesetting. Appendix C is an example of a text file before
processing. Before processing this file, the .LST file must be
created. TYPET asks for the name of the file to be processed
and assumes that .LST is the extension. This is critical on
******
TYPET Documentation - 4 -
User instructions
SuperVUE files since the .T file is not a format that can be
processed. To invoke processing, simply type CODES from the
AMOS dot (remember the CODES.CMD file?) and processing will
begin. First all of the codes will be entered, you will be
asked if you want a printout of the codes (you don't need it if
CODES.CMD exists), upon a negative answer, the program changes
modes to the text processing mode. Enter the file name
(excluding the extension) and processing will begin.....if it
finds the file and if it is compatible. The number of lines
processed will be displayed as it zips through your file.
Upon completion, TYPET will produce two more files in your
directory. One is a file called "READY.DAT" which contains the
name of the file processed and the number of lines that have
been processed. The second file is filename.SAV which is the
processed list file. Appendix D contains a listing of a
processed file. By comparing it with Appendix C, you can see
what the program does to the text.
The .SAV file is now ready for typesetting with the
exception of the special codes for figure placement and page lay
out. Those have to be performed by the typesetting operator.
A SPECIAL CASE
There is one special case for the codes. All of the codes
can be entered from the keyboard exactly as they will be
substituted EXCEPT for the leading blanks of a paragraph. In
order to enter those blanks, you must use the following flag:
SP(*) -- where * is the number of spaces to indent
This can be any number you wish but anything greater than 4 is
rejected by some typesetters (check your with your local machine
operator on this one).
A HINT FOR MORE EFFICIENCY
You may have several different types of files to be typeset.
For example, you may have a set of codes for a newsletter,
another set for a quarterly report, and yet another set for a
series of publications. It would become very unhandy to have
each on of these in a separate account all with the same command
file that invokes TYPET, namely CODES.CMD. Therefore, you may
find it beneficial to RENAME the file CODES.CMD to something
that will be associated with the final document. For example,
******
TYPET Documentation - 5 -
User instructions
if the product to be produced was a newsletter, you could use
the following command from AMOS to help you out:
.RENAME NEWLET.CMD=CODES.CMD (return)
This would rename CODES.CMD to NEWLET so when you want to
process a newsletter file you would enter NEWLET from the AMOS
dot to invoke TYPET. This would also save you from the
potential headache of entering a new set of codes and asking for
a printout, only to over-write the existing set of codes that
were designed for a different task.
******
TYPET Documentation - 6 -
User instructions
Appendix A. Codes.LST: an explanitory list of the typesetting
codes. Further explanations may be added by the user for their
own reference.
*SZ12*LS130*FT7*LL4200 ; code flag ]1
*QR ; code flag ]2
*SZ18*LS200*FT7 ; code flag ]3
*QC ; code flag ]4
*SZ14*LS150*FT7 ; code flag ]5
*SZ10*LS120*FT3 ; code flag ]6
SP(4) ; code flag ]7
*FT4 ; code flag ]8
*FT3 ; code flag ]9
*SZ14*LS150*FT3 ; code flag ]A
*QL ; code flag ]B
Appendix B. CODES.CMD: a command file created by TYPET that
invokes the TYPET program and pre-defines some typesetting
codes
Appendix C. An example of a text file before processing by
TYPET. (Note the flags proceded by the "]", doublespacing, and
the left margin).
]1January/February 1985]2
]3DIRECTOR'S REPORT]4
]6]7A National Conference on Water Resources Research
was held February 4-6, 1985 in Chevy Chase, Maryland. The
conference was sponsored by the Universities Council on Water
Resources under a grant from the National Science Foundation.
It was organized by a planning committee composed of a number of
universities and water agencies, with the assistance of the UNL
Water Resources Center.
]7The objectives of the conference were: (1) to seek a
renewed effort to re-establish a national water resources
research agenda; (2) to re-state research priorities; and (3) to
develop alternative working arrangements of the research
community, including federal, state, university and private
sector interests.
]7A conference proceedings is being prepared in which
preconference working papers will be revised as a result of
conference workshop discussions.
]51985 NEBRASKA WATER CONFERENCE]4
]6]7 The 1985 Nebraska Water Conference with the theme "Water
Management Implementation" will be held March 19-20, 1985 at the
Nebraska Center for Continuing Education in Lincoln.
]A]7The conference is divided into three main sessions:
(1) Implementing Legislation and Plans; (2) Economics and
Financing of Water Projects; and (3) Implementing Groundwater
Protection
******
TYPET Documentation - 8 -
User instructions
Appendix D. The processed file (renamed .SAV) ready for being
typeset.
*SZ12*LS130*FT7*LL4200January/February 1985*QR
*SZ18*LS200*FT7DIRECTOR'S REPORT*QC
*SZ10*LS120*FT3 A National Conference on Water Resources Research was held
February 4-6, 1985 in Chevy Chase, Maryland. The conference was
sponsored by the Universities Council on Water Resources under a
grant from the National Science Foundation. It was organized by a
planning committee composed of a number of universities and water
agencies, with the assistance of the UNL Water Resources Center.
The objectives of the conference were: (1) to seek a renewed
effort to re-establish a national water resources research agenda;
(2) to re-state research priorities; and (3) to develop alternative
working arrangements of the research community, including federal,
state, university and private sector interests.
A conference proceedings is being prepared in which pre-
conference working papers will be revised as a result of conference
workshop discussions.
*SZ14*LS150*FT71985 NEBRASKA WATER CONFERENCE*QC
*SZ10*LS120*FT3 The 1985 Nebraska Water Conference with the theme "Water
Management Implementation" will be held March 19-20, 1985 at
the Nebraska Center for Continuing Education in Lincoln.
*SZ10*LS120*FT3 The conference is divided into three main sessions: (1)
Implementing Legislation and Plans; (2) Economics and Financing
of Water Projects; and (3) Implementing Groundwater Protection
