You may no longer put xml-apis.jar, xercesImpl.jar, or xalan.jar in

Jskad/extensions.  If you're lazy, you can move them to
extensions/drop-ins, but the correct thing to do is to move x*.jar to
$ANT_HOME/lib [next to vamp.jar, if you're already set up for Java Web
Start builds].  This is a side effect of improving the nightly builds.

Nightly builds now feature an HTML summary of the JUnit test results,
a datestamp, and full API docs in two flavors.

If you use a patched vamp.jar [e-mail me] that can run when an X11
display is not available (there is not an analogous problem for
Windows servers, I suspect), all you have to do to put up a nightly
builds site is to set up CVS access so that no password is requires
using SSH public-key crypto (sf.net documents how to do so well) and
then use the following daily cron job on your Unix box:

#! /bin/sh
renice +19 -p $$ >/dev/null 2>&1
su -l joe-user /bin/sh -c /var/www/thdl/nightly/doTheBuild.sh

where joe-user is an unprivileged user who has installed Ant properly
(see the updated BuildSystems.html on the developer's site off of
thdltools.sf.net) and set himself up a Jskad sandbox with a Fonts
sandbox underneath it in, e.g., /var/www/thdl/nightly/Jskad.  Here's
doTheBuild.sh:

#! /bin/sh
JSKAD=/var/www/thdl/nightly/Jskad
DEST=/var/www/thdl/nightly/builds
HISTORY=/var/www/thdl/nightly/history
DATE=`date`
if test ! -d $DEST; then \
     echo "$DEST does not exist ($DATE)." >> history; exit 1; fi
(cd $JSKAD && ant dc-nightly-build \
 && rm -fr ${DEST}/* \
 && cp dist/nightlyBuild.zip $DEST \
 && cd $DEST \
     && unzip nightlyBuild.zip)
if test $? != 0; then echo "NIGHTLY BUILDS FAILED on $DATE" >> $HISTORY; exit 2; fi
DDDATE=`date`
echo "Success on start=$DATE end=$DDDATE" >> $HISTORY
exit 0

htdocs/BuildSystems.html

@@ -15,9 +15,13 @@
 
 <p>
   David Chandler has put together a build system for Jskad, Savant,
-  QuillDriver, the translation tool, and for the fonts.  This document
+  QuillDriver, the translation tool, Tibbibl, and for the fonts.  This
-  describes them, and should be updated when we put together build
+  document describes them, and should be updated if we put together
-  systems for the two diacritics packages and for Wylie Word.
+  build systems for the two diacritics packages and for Wylie Word
+  (but see e-mail to thdl-devel@lists.sourceforge.net that tells why
+  we probably will continue to require Wylie Word developers to edit
+  from within MS Word on account of the difficulty of using CVS with
+  VBA).
 </p>
 <p>
   What is a <i>build system</i>, you ask?  A build system is a set of
@@ -636,7 +640,14 @@ module<a name="jskadsetup"></a></h4>
     separately if you need a bug fix from a later release than that
     included in Xalan's.  After downloading, move
     <code>xalan.jar</code>, <code>xercesImpl.jar</code>, and
-    <code>xml-apis.jar</code> to <code>Jskad/extensions/</code>.
+    <code>xml-apis.jar</code> to <code>$ANT_HOME/lib</code>.&nbsp;
+    They need to be there to avoid loader errors when running the
+    <code>check-report</code> target, which is a part of the nightly
+    builds that also requires XSLT (i.e., the presence of those JARs,
+    but in a place that Ant recognizes).&nbsp; A consequence of using
+    this location is that you'll probably find using targets like
+    <code>qd-run</code> much easier than specifying your own
+    CLASSPATH.
   </li>
 
   <li>
@@ -651,7 +662,7 @@ module<a name="jskadsetup"></a></h4>
     Media Framework</a>.  After it is installed, either change your
     CLASSPATH to include its <code>jmf.jar</code>, or avoid the
     classpath hassle by copying <code>jmf.jar</code> to
-    <code>Jskad/extensions/</code>.
+    <code>Jskad/extensions/drop-ins</code>.
   </li>
 
   <li>