next up previous contents index
Next: Via LaTeX Up: Mixed Text and Previous: Via SGML/BookMaster

Via Waterloo/Script SGML

$==>$ KEEP it ???

The original version of the document markup language SGML [] implemented on the central VM/CMS service supports the inclusion of pictures. However, note that this SGML implementation is being replaced by a new one layered on top of the IBM BookMaster product (see above).

For each picture to be included when using the IBM-3812 output devices SGML requires two files; one to define the amount of space to be reserved within the document, and one containing the actual bit-map. These files must be accessible to SGML on one of the users mini-disks. As described in [], the files may originate from several sources. This section will discuss how to use the GRCONV command to produce them from a GKS metafile and store them on the specified mini-disk.

The sequence of operations would be:

  1. Use a graphics application program, including calls to GCNAME, to produce a metafile.
  2. Run GRCONV to produce the set of picture files and store them on a user disk.
  3. Mark-up a document with SGML and associate the picture files with particular figures within the document.
  4. Run SGML on the document.
  5. Edit the document as necessary and repeat previous step until result is satisfactory.
Note that it is not necessary to repeat the first two steps every time SGML is used to re-process the document so long as the picture files are stored on the user's disk.

An example of the SGML syntax necessary to include a figure corresponding to a pair of picture files would be:

<FIG>
<PICTURE NAME=XXXXXXXS>
<FIGCAP>This is the Figure Caption
</FIG>
When SGML encounters the tag 'PICTURE' it reads a file specified by the 'NAME' attribute. The name must consist of 8 characters ending with an 'S'. The file type under VM/CMS is 'SGML'. (The name of the corresponding bit-map file has the same first 7 characters, but the eighth is 'P'.) The GRCONV command can be used to generate these two files. In fact, as it would be cumbersome to require every picture to be stored in its own metafile and processed separately, GRCONV can handle metafiles which contain several pictures (separated by 'CLEAR WORKSTATION' items). It then produces one pair of output files for each picture on the metafile. If the user is not working under VM/CMS, GRCONV first transfers the metafile to the user's VM account, and then interprets it to produce the required set of output files. (Care must be taken to ensure that there is no conflict in having GRCONV write to a VM/CMS mini-disk which is accessed in write mode by another process. The user should have a write password on a mini-disk available for access by GRCONV in write-mode.) Note that GRCONV replaces the command GKSSGML, and has a wider range of features.

next up previous contents index
Next: Via LaTeX Up: Mixed Text and Previous: Via SGML/BookMaster


Janne Saarela
Mon Apr 3 17:00:12 METDST 1995