www/htdocs/THDLTools_Developers.html
dchandler a35c49e20f An attempt at bringing these pages up to date w.r.t. THDL HTML guidelines.
These validated with the validator.w3.org as XHTML 1.0 strict.
2003-10-31 03:57:47 +00:00

327 lines
9.5 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<!-- @author David Chandler -->
<!-- @date September 7, 2002 -->
<!-- @editor Emacs, baby! -->
<head>
<title>THDL Tools Developers' Site</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<script type="text/javascript" src="/tibet/scripts/thdl_scripts.js"></script>
<link rel="stylesheet" type="text/css" href="/tibet/style/thdl-styles.css"/>
</head>
<body>
<div id="banner">
<a id="logo" href="/tibet/index.html"><img id="test" alt="THDL Logo" src="/tibet/images/logo.png"/></a>
<h1>The Tibetan &amp; Himalayan Digital Library</h1>
<div id="menubar">
<script type='text/javascript'>function Go(){return}</script>
<script type='text/javascript' src='/tibet/scripts/new/thdl_menu_config.js'></script>
<script type='text/javascript' src='/tibet/scripts/new/menu_new.js'></script>
<script type='text/javascript' src='/tibet/scripts/new/menu9_com.js'></script>
<noscript><p>Your browser does not support javascript.</p></noscript>
<div id='MenuPos' >Menu Loading... </div>
</div><!--END menubar-->
</div><!--END banner-->
<div id="sub_banner">
<div id="search">
<form method="get" action="http://www.google.com/u/thdl">
<p>
<input type="text" name="q" id="q" size="15" maxlength="255" value="" />
<input type="submit" name="sa" id="sa" value="Search"/>
<input type="hidden" name="hq" id="hq" value="inurl:iris.lib.virginia.edu"/>
</p>
</form>
</div>
<div id="breadcrumbs">
<a href="/tibet/index.html">Home</a> &gt; <a href="index.html">Tools</a> &gt; <a href="/tibet/tools/software.html">Software</a> &gt; Developers' Site
</div>
</div><!--END banner-->
<div id="main">
<h2>THDL Tools Developers' Site</h2>
<p>
This page is a technical page for software developers,
which presents details concerning the internal mechanics
of the THDL tools. This page covers both low-level (e.g., which
API?) and high-level (e.g., which user interface?) issues.
<a href="#related">
Related projects</a>
are also discussed.
</p>
<p>
The only thing we personally have got up on the web that's any use
thus far are
</p>
<ul>
<li>
the <a
href="http://iris.lib.virginia.edu/tibet/tools/nightly/builds/NightlyBuilds.html">
nightly builds</a>.&nbsp; Get the latest, bleeding-edge version
and try it out for yourself.&nbsp; The latest API docs (i.e.,
Javadocs) are also available.
</li>
<li>
the documentation for the <a
href="tibwn_ini_file_format.html"><code>tibwn.ini</code> file
format</a>.
</li>
<li>
<a href="Tibetan51Errata.html">errata</a> for the <i>Tibetan!
5.1 for Word</i> documentation, mainly concerning the Tibetan
Machine and Tibetan Machine Web fonts.
</li>
<li>
a <a href="TMW_RTF_TO_THDL_WYLIE.html"> document</a> describing
a Tibetan Machine Web to {THDL Extended Wylie, Tibetan Machine}
converter that works for Rich Text Format files and solves the
&quot;curly-brace problem&quot;.
</li>
<li>
our Javadoc <a href="pubapi/">API docs</a> [grab the whole <a
href="public-javadocs.zip">zip file</a>] (see also these <a
href="privateapi/">API docs</a> [grab the whole <a
href="private-javadocs.zip">zip file</a>] that contain private
class members).
</li>
<li>
a description of our <a href="BuildSystems.html"> build
systems</a> that tells you how to compile, run, and cut releases
for our tools.
</li>
<li>
a <a href="TibetanFormatConverterDesign.html">design
document</a> concerning the Tibetan Format Converter.
</li>
</ul>
<p>
Here are some links to tools of interest:
</p>
<ul>
<li>
Jskad uses an Ant build system.&nbsp; See
<a href="http://jakarta.apache.org/ant/">
Apache Ant</a>
or jump right to the
<a href="http://jakarta.apache.org/ant/manual/coretasklist.html">
documentation</a>
for the tasks of which we make use.
</li>
<li>
Our unit tests use the
<a href="http://junit.org/">
JUnit</a>
framework.&nbsp; Javadocs are <a
href="http://www.junit.org/junit/javadoc/3.8.1/index.htm">here</a>
(or jump directly <a
href="http://www.junit.org/junit/javadoc/3.8.1/index.htm/allclasses-frame.html/junit/framework/TestCase.html">here</a>
for TestCase's docs).
</li>
<li>
In our Java(TM) code, we load some classes at run-time.&nbsp; To
understand the mechanisms behind
this--<code>Class.forName(String)</code> and thread context
class loaders, etc.--read
<a href="http://www.javageeks.com/Papers/ClassForName/">
this JavaGeeks white paper</a>.
</li>
<li>
Our Java code uses XML. We use
<a href="http://jdom.org/">
JDOM</a>,
<a href="http://xml.apache.org/xalan-j/">
Xalan</a> (XSLT),
and
<a href="http://xml.apache.org/xerces2-j/index.html">
Xerces</a>.
</li>
<li>
We use the Ant Task Suite provided by Venus Application
Publisher (Vamp) to make putting releases up via Java Web Start
less painful. See
<a href="http://www.vamphq.com/ant.html">
VampHQ</a>.
</li>
</ul>
<h3>Related Projects<a name="related"></a></h3>
<p>
Below are links to some (mainly Java) text editors or word
processors that we might learn from or integrate with. This list is
by no means comprehensive. I started my search from
<a href="http://sourceforge.net/softwaremap/trove_list.php?form_cat=63&amp;discrim=198">
SF.net's software map</a>,
by the way (and see
<a href="http://sourceforge.net/softwaremap/trove_list.php?form_cat=70&amp;discrim=198">
this corner of the map</a>,
too), and haven't yet done anything more.
</p>
<ul>
<li>
The non-open-source
<a href="http://uk.geocities.com/babelstone1357/Software/BabelPad.html">
BabelPad</a> allows you to create Unicode documents using a
THDL Extended Wylie keyboard.
</li>
<li>
The GPL'ed
<a href="http://vietpad.sourceforge.net/">
VietPad</a>,
written in Java, (for entering Vietnamese language in Unicode-8
or -16) may teach us something, though integration doesn't seem
useful (because it is primitive) and would require changing our
license to the GPL.
</li>
<li>
The GPL'ed
<a href="http://jedit.sourceforge.net/">
JEdit</a>
bills itself as a "programmer's text editor", but it supports
Unicode, is 100% Java, is very popular, and is extremely
extensible, making integration while keeping our
non-GPL-compatible license a possibility. Definitely worth a
second look.
</li>
<li>
The GPL'ed
<a href="http://yudit.org/">
Yudit</a>
is an X11 application that supports Unicode in a big way. Their
<a href="http://yudit.org/">
website</a>
has many links of interest to us as we ponder Unicode
compatibility.
</li>
<li>
The GPL'ed/LGPL'ed
<a href="http://www.prometheas.com/projects/_syggrafeus/index.html">
Syggrafeus/Rosetta Stone Library</a>
is a Java library for Unicode multi-lingual something-or-other.
</li>
<li>
The GPL'ed
<a href="http://sted.sourceforge.net/">
STED</a>
is a Java transliterator for many languages.
</li>
<li>
The GPL'ed
<a href="http://sourceforge.net/projects/words-of-magic/">
Words of Magic</a>
is a very simple word processor for English and Dutch.
</li>
<li>
The GPL'ed
<a href="http://sourceforge.net/projects/jgloss/">
JGloss</a>
says this about itself: "JGloss lets you import Japanese text
documents and add reading and translation annotations for words,
both automatically during import, and manually. It is written in
Java."
</li>
</ul>
<p>
Finally, the
<a href="http://epidoc.sourceforge.net/">
EpiDoc</a>
project (hosted by SourceForge) does not yet have any tools up, but
the project's goals are similar in many ways to the THDL's, and they
list their programming language as Java. The blurb of interest:
"The EpiDoc Collaborative is developing a software and
hardware-independent digital publication and interchange
specification for scholarly and educational editions of inscribed
and incised texts in Greek, Latin and other ancient languages".
</p>
<p>
Please
<a href="mailto:thdltools-devel@lists.sourceforge.net">
e-mail us</a>
your comments about this page.
</p>
<p>
The
<a href="http://www.sourceforge.net/projects/thdltools">
THDL Tools</a>
project is generously hosted by:
<!--
DO NOT DELETE THE SF.NET LOGO.
We have a choice of colors and sizes for this logo (see
"https://sourceforge.net/docman/display_doc.php?docid=790&group_id=1"),
but we do not have the option of removing it. SourceForge requests
that we put it on each web page for our project, and to give us
incentive to do so, they will not track the number of hits for our
project web pages unless we put this link in. To track hits, see
"http://sourceforge.net/project/stats/index.php?report=months&group_id=61934".
-->
<a href="http://sourceforge.net/">
<img src="http://sourceforge.net/sflogo.php?group_id=61934&amp;type=1"
width="88" height="31" alt="SourceForge Logo" />
</a>
<!-- AGAIN, DO NOT DELETE THE SF.NET LOGO. -->
</p>
</div>
</body>
</html>