351 lines
12 KiB
HTML
351 lines
12 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<html>
|
|
|
|
<!-- @author David Chandler -->
|
|
<!-- @date-created May 18, 2003 -->
|
|
<!-- @editor Emacs, baby! -->
|
|
|
|
<!--
|
|
==============
|
|
INSERT KEYWORDS AND DESCRIPTION HERE
|
|
==============
|
|
-->
|
|
|
|
|
|
<meta name="keywords" content="tibetan fonts, tibetan software, digital ethnography">
|
|
|
|
<meta name="description" content="This presents intellectual and electronic tools for using Tibetan language in a digital medium and for viewing the THDL site.">
|
|
|
|
<!--
|
|
==============
|
|
INSERT PAGE TITLE HERE
|
|
==============
|
|
In order to facilitate the use of the unicode character set the charset declaration will be set equal to utf-8
|
|
Always incorporate Tibetan and Himalayan
|
|
-->
|
|
|
|
<title>Tibetan Machine Web Converter</title>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=iso-utf-8">
|
|
|
|
<!--
|
|
==============
|
|
THIS IS THE STYLE FOR THE BODY; IT'S WHAT CALLS ON THE BANNER AS A BACKGROUND IMAGE AND SETS UP THE BACKGROUND COLOR. MAKE SURE TO LINK TO THE BANNER HERE.
|
|
==============
|
|
-->
|
|
|
|
<style type="text/css">
|
|
<!--
|
|
body {background-attachment: scroll; background-image: url(http://iris.lib.virginia.edu/tibet/images/bannerTools.gif); background-repeat: no-repeat; background-position: left top; backgroud-color: white}
|
|
-->
|
|
</style>
|
|
|
|
<!--
|
|
==============
|
|
THE STYLE FOR THE TEXT, ETC. IT GOES TO THE TOP-LEVEL STYLE PAGE. IS THERE A NEED FOR EACH COLLECTION TO HAVE INDIVIDUAL STYLE PAGES?
|
|
==============
|
|
-->
|
|
|
|
<link rel="stylesheet" href="http://iris.lib.virginia.edu/tibet/style/tools.css">
|
|
|
|
<!--
|
|
==============
|
|
MAKES NETSCAPE RELOAD IF THE WINDOW IS RESIZED
|
|
==============
|
|
-->
|
|
|
|
<script language="JavaScript">
|
|
<!--
|
|
function MM_reloadPage(init) { //reloads the window if Nav4 resized
|
|
if (init==true) with (navigator) {if ((appName=="Netscape")&&(parseInt(appVersion)==4)) {
|
|
document.MM_pgW=innerWidth; document.MM_pgH=innerHeight; onresize=MM_reloadPage; }}
|
|
else if (innerWidth!=document.MM_pgW || innerHeight!=document.MM_pgH) location.reload();
|
|
}
|
|
MM_reloadPage(true);
|
|
// -->
|
|
</script>
|
|
</head>
|
|
|
|
<!--
|
|
==============
|
|
SETS THE PAGE MARGINS TO "0" SO THE MENU DOESN'T GET SCREWED UP
|
|
==============
|
|
-->
|
|
|
|
<body topmargin="0" leftmargin="0" marginwidth="0" marginheight="0">
|
|
|
|
|
|
<!--
|
|
==============
|
|
THE JAVASCRIPT MENUS
|
|
==============
|
|
-->
|
|
|
|
<script type='text/javascript'>
|
|
//HV Menu v5- by Ger Versluis (http://www.burmees.nl/)
|
|
//Submitted to Dynamic Drive (http://www.dynamicdrive.com)
|
|
//Visit http://www.dynamicdrive.com for this script and more
|
|
|
|
function Go(){return}
|
|
|
|
//==============
|
|
// --CALL UP THE MENU. THE 1ST OF THE CHOICES HAS THE VARIABLES
|
|
// AND NEEDS TO BE UPDATED FOR EACH SECTION.
|
|
// MENU_LOADER.JS WILL ALWAYS BE THE SAME.
|
|
//==============
|
|
|
|
|
|
</script>
|
|
<script type='text/javascript' src='http://iris.lib.virginia.edu/tibet/scripts/menu_tools.js'></script>
|
|
<script type='text/javascript' src='http://iris.lib.virginia.edu//tibet/scripts/menu_loader.js'></script>
|
|
<script type="text/javascript" src="http://iris.lib.virginia.edu//tibet/scripts/thdl_scripts.js"></script>
|
|
<noscript> Your browser does not support Javascript menus. Please utilize the
|
|
Site Map for navigation.</noscript>
|
|
|
|
|
|
<div align="left" style="position:absolute; left:0px; top:0px; width:100px; height:50px; z-index:7">
|
|
<a href="http://iris.lib.virginia.edu/tibet/index.html">
|
|
<img src="http://iris.lib.virginia.edu/tibet/images/spacer.gif" style="border-width:0" width="100" height="50">
|
|
</a>
|
|
</div>
|
|
<div id="Layer1" style="position:absolute; left:100px; top:28px; width:708px; height:20px; z-index:1">
|
|
|
|
<!--
|
|
==============
|
|
INSERT THE BREADCRUMBS
|
|
==============
|
|
A HREF tags should not be applied to current page, e.g. THDL and Collections get link, Literature and Home do not. If you were on a subpage of Literature, then Literature would link to the Literature home page.
|
|
-->
|
|
|
|
<div align="right"><font color="#000000"><A HREF="http://iris.lib.virginia.edu/tibet/index.html">THDL</A> : <A HREF="http://iris.lib.virginia.edu/tibet/tools/index.html">Tools</A> : <a href="http://iris.lib.virginia.edu/tibet/tools/software.html">Software</a> : Tibetan Machine Web Converter</a></font>
|
|
</div>
|
|
</div>
|
|
|
|
<!--
|
|
==============
|
|
INSERT THE MENU
|
|
==============
|
|
-->
|
|
|
|
<div id='MenuPos' style="text-size:9px; layer-background-color:#CCCCCC; background-color: #CCCCCC; position:absolute; left:0px; top:50px; width:808px"><table width="808" cellpadding="0" cellspacing="0" height="19"><tr><td><p style="font-size:9px">Menu loading...</p></td></tr></table></div>
|
|
|
|
|
|
<!--
|
|
==============
|
|
MAKE THE LAYER THAT WILL HOLD THE CONTENT OF THE PAGE - THE TEXT, IMAGES, WHATEVER. THIS LAYER WILL BE CLOSED AT THE END OF THIS HTML DOCUMENT
|
|
==============
|
|
Maximum table width not to exceed 750
|
|
All images must have borders of 1 pixel
|
|
No image will exceed 325 X 325 height and width measurements
|
|
Position attribute on layer3 may need to be changed to absolute to accomodate Netscape
|
|
-->
|
|
|
|
<div id="Layer3" style="position:relative; left:7px; top:80px; width:801px; height:396px; z-index:1; overflow: visible; background-color: #FFFFFF; layer-background-color: #FFFFFF; border: 1px none #000000" >
|
|
|
|
<table width="750" border="0" cellspacing="0" cellpadding="10">
|
|
<tr>
|
|
<td valign="top" align="left">
|
|
|
|
<!--
|
|
=============
|
|
FOR EVERY "ADMINISTRATIVELY DISTINCT" PROJECT, THERE SHOULD BE A CREDIT FOR THE PROVIDER OF THE INFO
|
|
=============
|
|
-->
|
|
|
|
<script langauge="JavaScript">
|
|
function openWin(url, name) { popupWin = window.open(url, name,"resizable=1,scrollbars=1,toolbar=0,width=400 ,height=450")
|
|
}
|
|
</script>
|
|
|
|
|
|
<!--
|
|
============
|
|
THIS LINK WILL OPEN A SEPARATE WINDOW THAT WILL PROVIDE INFORMATION REGARDING THE ADVISORY BOARD MEMBERS. ALSO PROVIDED IN THE PAGE WILL BE PARTICIPATION AND DONATION INFORMATION.
|
|
============
|
|
-->
|
|
|
|
|
|
<!--
|
|
==============
|
|
SETS THE BODY TEXT TO JUSTIFIED
|
|
==============
|
|
-->
|
|
|
|
<div align=justify>
|
|
|
|
|
|
<!--
|
|
=============
|
|
INSERT LINK TO GUIDED TOUR HERE -uncomment when ready.
|
|
=============
|
|
-->
|
|
|
|
|
|
<!--
|
|
==============
|
|
INSERT BODY TEXT HERE
|
|
|
|
The first section of text is the short "introduction" about the Theme and the various discplines that have a vested interest in them.
|
|
Design principle: Bold the first few words of this text section.
|
|
==============
|
|
-->
|
|
<h2>Tibetan Machine Web Converter</h2>
|
|
|
|
<p>
|
|
In the same JAR file as Jskad, power users will find a command-line
|
|
utility that converts a Tibetan Machine Web-encoded (TMW-encoded) Rich
|
|
Text Format (RTF) file to either of these two output formats:
|
|
</p>
|
|
<ul>
|
|
<li>RTF files with the appropriate THDL Extended Wylie (Wylie) used
|
|
instead of TMW</li>
|
|
<li>RTF files in Tibetan Machine (used in legacy systems)</li>
|
|
</ul>
|
|
|
|
<p>
|
|
In addition, this converter can convert Tibetan Machine RTF files to
|
|
Tibetan Machine RTF files, and takes precautions to ensure that only
|
|
a 100% perfect conversion is done.<!-- FIXME: talk about the
|
|
my-own-tibwn.ini validation exercise and the oddballs and their
|
|
handling -->
|
|
</p>
|
|
|
|
<p>
|
|
This converter is smart enough to solve the "curly-brace
|
|
problem". This problem originates with certain versions
|
|
of Microsoft Word's Rich Text Format writing capabilities.
|
|
</p>
|
|
|
|
<p>
|
|
Further, this converter gives a polite error message when a given
|
|
.rtf file simply cannot be read by the version of Java used.
|
|
</p>
|
|
|
|
<p>
|
|
Perhaps most importantly, the converter has a
|
|
<tt>--find-some-non-tmw</tt> mode of operation that gives you, the
|
|
user, confidence that RTF reading and writing idiosyncrasies are not
|
|
going to interfere with a flawless conversion. It does so by
|
|
printing out the first occurrence of a given character in a non-TMW
|
|
font. Here is some example output:
|
|
</p>
|
|
<pre>
|
|
java -cp Jskad.jar \
|
|
org.thdl.tib.input.TMW_RTF_TO_THDL_WYLIE \
|
|
--find-some-non-tmw \
|
|
"Dalai Lama Fifth History 01.rtf"
|
|
non-TMW character newline in the font Tahoma appears first at location 39
|
|
non-TMW character ' ' in the font TimesNewRoman appears first at location 45
|
|
non-TMW character '}' in the font Tahoma appears first at location 66
|
|
non-TMW character '{' in the font Tahoma appears first at location 219
|
|
non-TMW character '\' in the font Tahoma appears first at location 1237
|
|
non-TMW character newline in the font Times New Roman appears first at location 9754
|
|
</pre>
|
|
|
|
<p>
|
|
Given the above output, you can be sure that a flawless conversion
|
|
(barring the appearance of <a href="#knownbugs">known bugs</a>) will
|
|
result when you run <tt>java -cp Jskad.jar
|
|
org.thdl.tib.input.TMW_RTF_TO_THDL_WYLIE --to-wylie "Dalai Lama
|
|
Fifth History 01.rtf" > "Dalai Lama Fifth History 01 in THDL
|
|
Extended Wylie.rtf"</tt>. This is because the only text in the
|
|
input file besides Tibetan is whitespace and the Tahoma characters
|
|
<tt>'{'</tt>, <tt>'}'</tt>, and <tt>'\'</tt>. These Tahoma
|
|
characters are understood by the tool; they are symptoms of the
|
|
"curly-brace problem".
|
|
</p>
|
|
|
|
<p>
|
|
Note that some TMW glyphs have no transliteration in Exteded
|
|
Wylie. When you encounter such a glyph, you'll find a message
|
|
like the following in your RTF output:
|
|
</p>
|
|
|
|
<p>
|
|
<tt><<[[JSKAD_TMW_TO_WYLIE_ERROR_NO_SUCH_WYLIE: Cannot convert
|
|
DuffCode <duffcode font=TibetanMachineWeb8 charNum=101
|
|
character=e/> to THDL Extended Wylie. Please see the <a
|
|
href="http://iris.lib.virginia.edu/tibet/tools/tmw.html#doc">
|
|
documentation for the TMW font</a> and transcribe this
|
|
yourself.]]>></tt>
|
|
</p>
|
|
|
|
<p>
|
|
Upon seeing this, you should consult the <a
|
|
href="http://iris.lib.virginia.edu/tibet/tools/tmw.html#doc">
|
|
documentation</a> for the specific TMW font named. Find the
|
|
glyph (by its charNum) and decide how to proceed. If you find
|
|
a glyph that you believe should have been converted into Extended
|
|
Wylie by the tool, please report this as a bug.
|
|
</p>
|
|
|
|
<p>
|
|
Note also that there is one TMW glyph (TibetanMachineWeb7, glyph 91)
|
|
that has no Tibetan Machine equivalent. A 72-point copy of the
|
|
Tibetan alphabet will be inserted (in TMW) before this glyph.
|
|
Some common-but-illegal TibetanMachine input will also cause the
|
|
alphabet to appear before the offending glyph. Please use
|
|
Jskad to convert such documents, as it has better error checking and
|
|
can tell you just what's wrong. If you ever encounter these
|
|
problems, please send us mail with the error report (and the problem
|
|
input document) so that we can improve our tools.
|
|
</p>
|
|
|
|
<h3>Invoking the Converter</h3>
|
|
|
|
<p>
|
|
First add Jskad.jar to your CLASSPATH. Now run the command
|
|
<tt>java org.thdl.tib.input.TMW_RTF_TO_THDL_WYLIE</tt> from a
|
|
command prompt. You will see usage information appear.
|
|
Forgive the name; this converter's scope widened after its creation.
|
|
</p>
|
|
|
|
<h3><a name="knownbugs"></a>Known Bugs</h3>
|
|
|
|
<p>
|
|
If the TMW given is not syntactically legal, then the Wylie that
|
|
results will not necessarily yield, if imported into Jskad, the same
|
|
Tibetan with which the converter started.
|
|
</p>
|
|
|
|
<p>
|
|
Please
|
|
|
|
<a href="mailto:thdltools-devel@lists.sourceforge.net">
|
|
e-mail us</a>
|
|
|
|
your comments about this page.
|
|
</p>
|
|
|
|
<p>
|
|
The
|
|
<a target="_blank" 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 target="_blank" href="http://sourceforge.net/">
|
|
<img src="http://sourceforge.net/sflogo.php?group_id=61934&type=1"
|
|
width="88" height="31" border="0" alt="SourceForge Logo">
|
|
</a>
|
|
<!-- AGAIN, DO NOT DELETE THE SF.NET LOGO. -->
|
|
</p>
|
|
</div>
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
</div>
|
|
|
|
|
|
</body>
|
|
</html>
|