J_MTEXT.DOC
January 6, 1994

JAWS Macro compiler/decompiler.
-------------------------------

The program determines what action to take, based on the
extension of the first file being processed.  If the extension is JMF, then
the file is decompiled into a .JMT file.  If the extension is .JMT,
then it is compiled into a .JMF  file.  If the file named by the
user has no extension, then the program does its best to figure out
what should be done.  If both a .JMF and a .JMT file exist with the
same base name, then the newer of the two is acted upon.  Otherwise, if
only one file has this base name, then it is processed.

If multiple .JMT files are entered on the command line, the resulting
.jmf file will have the same base name as the first one,  but will
include the contents of all of them. A similar result can be achieved
by only specifying one file name on the command line, and within that
file, using the [include] command to tell the system to process other
files as well.

the syntax
	[include] FILE-NAME
will insert the contents of another JMT file into the .JMF file being compiled.

If the same macro key is defined multiple times, the first definition
will be used, and additional ones will generate warnings. (The /r
option causes the last definition to be used instead.)

Brackets around function names, and braces around key names are now
optional.  If not bracketted, key and function names can not contain any
spaces.  Spaces should be replaced by dashes, plusses, underscores or slashes.

The /n switch when decompiling a macro file will suppress the
printing of brackets and braces.

When decompiling a .JMF file, the program now lists settings for all
flags which are non-zero. If a flag has a value of 255, then it is
said to be ON, otherwise the numeric setting is printed.

If there is a .JFF file with the same name as the macro file being
decompiled,  then frame and place marker definitions are also
included in the .JMT file.

If a .JMT file contains either frame or place marker definitions,
then compiling that file will also generate a .JFF file.

Frame definitions, marker definitions, macro
definitions, flag settings, and [include] directives can be
freely intermingled throught the file.

Here are examples  of the new statements which can appear outside of
a macro:

# Flag settings
Toggle-units 2
Smart-bar-flag 2
Smart-toggle On

# frames defined in file wp.jff
Frame 25 from row 25 column 1 to row 25 column 9
Frame 26 from row 14 column 1 to row 24 column 80
# Place Markers defined in file wp.jff
Marker e at row 17 column 5 JAWS
Marker r at row 18 column 2 JAWS
Marker Space at row 11 column 37 PC

Words like From, Row, Column, At, and To, are optional in the above statements.

				OPTIONS
	/c      Compressed decompiled output, with as much of each macro
		definition on each line as will fit.

	/d DIRECTORY:   Place output files in specified directory.

	/n      No brackets, don't enclose function and key names in
		brackets and braces respectively.

	/o FILENAME:    Use FILENAME as the name for the output file

	/r      redifine: If a macro is defined more than once, use the
		last definition instead of the first.

	/s      Sort macros alphabetically.

