The http://thdltools.sf.net web pages are now updated every four hours.
Due to sf.net difficulties, they may be 28 hours behind until September 2003, however. Updated the WylieWord/Diacritics info.
This commit is contained in:
parent
7c7d57ecd7
commit
8c2622d5b9
1 changed files with 15 additions and 34 deletions
|
@ -195,11 +195,11 @@ The first section of text is the short "introduction" about the Theme and the va
|
|||
translation tool, Tibbibl, and for the fonts. In the CVS
|
||||
repository, you'll find that the build system once worked for Savant
|
||||
and QuillDriver as well. This document describes them, and
|
||||
should be updated if we put together build systems for the two
|
||||
diacritics packages and for Wylie Word (but see e-mail to
|
||||
should be updated if we put together better 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).
|
||||
continue to require WylieWord and Diacritics 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
|
||||
|
@ -235,8 +235,7 @@ The first section of text is the short "introduction" about the Theme and the va
|
|||
module</a> -- how to publish on this very web site, that is
|
||||
</li>
|
||||
<li>
|
||||
<a href="#diacriticsmodule">Building the <code>Diacritics</code>
|
||||
module</a>
|
||||
<a href="#diacriticsmodule">Building the <code>Diacritics</code> and <code>WylieWord</code> modules</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="#wyliewordmodule">Building the <code>WylieWord</code>
|
||||
|
@ -603,17 +602,14 @@ name="buildingfonts"></a></h3>
|
|||
</li>
|
||||
|
||||
<li>
|
||||
Now you must update the CVS <a href="#sandbox"> sandbox</a> at
|
||||
Now you must wait four hours for the cron job (added via crontab)
|
||||
to update the CVS <a href="#sandbox"> sandbox</a> at
|
||||
<code>thdltools.sourceforge.net:/home/groups/t/th/thdltools/htdocs</code>.
|
||||
To do so, use PuTTY or another <code>ssh</code> to log in to
|
||||
<code>thdltools.sourceforge.net</code>. Now change directory
|
||||
(<code>cd</code>) to
|
||||
<code>/home/groups/t/th/thdltools/htdocs</code> and run <code>'cvs
|
||||
-d :ext:YourSourceForgeUserId@cvs1:/cvsroot/thdltools -f update -d
|
||||
-P'</code>. You'll see your changes being made to the "real"
|
||||
website. Surf to <a
|
||||
After waiting four hours, surf to <a
|
||||
href="http://thdltools.sourceforge.net/"> the website</a> and see
|
||||
for yourself.
|
||||
for yourself. (Note that we use pserver to update the site,
|
||||
so until September 2003, it may be 28 hours until you see your
|
||||
change.)
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
@ -680,13 +676,6 @@ module<a name="updateapidocs"></a></h4>
|
|||
<code>/home/groups/t/th/thdltools/htdocs/</code>.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
While you're here, do a <code>'cvs -d
|
||||
:ext:YourSourceForgeUserId@cvs1:/cvsroot/thdltools -f update -d
|
||||
-P'</code> -- just in case some developer made changes to the
|
||||
web pages but forgot to update.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Anyway, now run <code>'rm -fr pubapi privateapi public-javadocs*
|
||||
private-javadocs*'</code> (from the <code>htdocs/</code>
|
||||
|
@ -750,23 +739,15 @@ module<a name="updateapidocs"></a></h4>
|
|||
|
||||
|
||||
|
||||
<h3>Building the <code>Diacritics</code> module<a
|
||||
<h3>Building the <code>Diacritics</code> and <code>WylieWord</code> modules<a
|
||||
name="diacriticsmodule"></a></h3>
|
||||
|
||||
<p>
|
||||
We don't yet have source code in this module. Check back here
|
||||
once we do.
|
||||
</p>
|
||||
|
||||
|
||||
|
||||
<h3>Building the <code>WylieWord</code> module<a
|
||||
name="wyliewordmodule"></a></h3>
|
||||
|
||||
<p>
|
||||
You'll have to use MS Word to get at the Visual Basic source code in
|
||||
the .dot file. Edit it there, and then commit the revised .dot
|
||||
file. 'cvs diff' won't work, but that's life.
|
||||
file. 'cvs diff' won't work, but that's life unless you want
|
||||
to do a lot of cutting and pasting into the .dot file every time you
|
||||
make an edit.
|
||||
</p>
|
||||
|
||||
|
||||
|
|
Loading…
Reference in a new issue