Bob,
Sorry for the delay. I have been pointing in another direction for a while.

The source of scribe is ERCC15.SCRIBE2P9. The bit you will want is external
routine ESCRIBE which is the first 8000 lines or thereabout. The rest is
externalroutine SCRIBE which deals with dispatching scribe jobs to our VAX
and DEC10, and in the case of Emas simply calls ESCRIBE.

You will see that there are drivers for devices LPT,X2700,GP300 and FILE.
For the sake of efficiency, many more of the device characteristics are
built into the code rather than being effected from the device definitions
in the data-base, than is the case in Unilogoc Scribe. Thus much of the
information in the DECLARE directives in the data-base is redundant.
I don't know what devices you have but if there changes to make to the code
they will be in that area. The only other thing that is site dependant is the
conststring ESCRIBE MANAGR which is where the data-base lives.

The data-base itself is ERCC15.ESCRIBE which is a pD file of four members.
They are all character files. The members are
      _DEVICE, device declarations and standard environments,
      _MAKE,   document specific environments, counters, etc
      _TYPECASE, the typecase definitions, ie the mapping of logical facecodes
                 to collections of device characters,
      _WIDTH,  the width of individual device charcters.
The DEVICE and MAKE members are in standard Unilogoc format and you should
not have any trouble with those. The TYPECASE and WIDTH formats are of my own
invention, being much condensed and much less general than theie UNilogoc
equivalents, again for the sake of efficiency. No doubt you will need to change
those for your devices and their specific fonts, so you will need to understand
that format. I suppose the best explanation is the code that reads them -
routine LOAD TYPECASE.

Let me know if you need any more info.

Colin.