Automated SGML Markup

Instructions for Download and Use


These instructions are based on the system this was written on, an IBM RS6000 running AIX3.1 and httpd 1.4.

1. Set up a directory structure
Mu uses three directories: muroot, which you must be able to run cgi scripts from, and a raw and a cooking directory. Muroot is the where all the scripts are stored (this may be your cgi-bin directory, or it may be somewhere else). The raw directory contains the sgml template file (more on this in a second). The cooking directory is where the marked up SGML files will be stored. Make these three directories and ensure that they are writeable by your web server.

2. Unpack mu.tar.Z
Download mu.tar.Z if you haven't already and save or move it into the muroot directory from step 1. Now uncompress and untar that file in that directory (use "uncompress mu.tar.Z" and "tar -xvf mu.tar", for example). Depending on your sever, you may need to rename mu.pl to mu.cgi. You may want to move instruc.html and mu.html somewhere else, also. Make sure all the scripts in muconfig are executable by your web server.

3. Tweak muconfig.pl
Now you need to tell muconfig where your directories are. Open muconfig.pl with your favorite editor, and change $MuRoot, $Raw and $Cooking to the positions of the directories you made. Also, change $Template to the name of the file you are using as a template, i.e. header.raw.sgml. You can also customize the header and tail that gets printed out each time in this file. Make sure not to delete the open and first print statement in Header().

4. Tweak mu.html
Change the first line of the form in mu.html to the URL for MuRoot.

5. SGML template
Put your sgml template file in the raw directory.