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 three output formats: + utility that converts Tibetan documents from one digital + representation to another. The converter embodies the same + technology as Jskad itself, but often works even when Jskad fails + due to Java's presently poor support for viewing RTF + documents. This command-line utility converts a Tibetan + Machine Web-encoded (TMW-encoded) Rich Text Format (RTF) file to + either of these three output formats:
-java -cp Jskad.jar \
+java -cp "c:\my thdl tools\Jskad.jar" \
org.thdl.tib.input.TibetanConverter \
--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
@@ -260,14 +266,15 @@ non-TMW character newline in the font Times New Roman appears first at location
Given the above output, you can be sure that a flawless conversion
(barring the appearance of known bugs) will
- result when you run java -cp Jskad.jar
- org.thdl.tib.input.TibetanConverter --to-wylie "Dalai Lama
- Fifth History 01.rtf" > "Dalai Lama Fifth History 01 in THDL
- Extended Wylie.rtf". This is because the only text in the
- input file besides Tibetan is whitespace and the Tahoma characters
- '{', '}', and '\'. These Tahoma
- characters are understood by the tool; they are symptoms of the
- "curly-brace problem".
+ result when you run java -cp "c:\my thdl tools\Jskad.jar"
+ org.thdl.tib.input.TibetanConverter --to-wylie "Dalai Lama Fifth
+ History 01.rtf" > "Dalai Lama Fifth History 01 in THDL Extended
+ Wylie.rtf". (Note that the '>' causes the output to be
+ directed to the file named thereafter; this is quite handy.)
+ This is because the only text in the input file besides Tibetan is
+ whitespace and the Tahoma characters '{', '}', and
+ '\'. These Tahoma characters are understood by the tool;
+ they are symptoms of the "curly-brace problem".
Failed Conversions
@@ -281,26 +288,56 @@ non-TMW character newline in the font Times New Roman appears first at location
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:
+ Wylie. When you encounter such a glyph, you'll find
+ \tmwXYYY in your output, where X tells you which TMW font
+ the troublesome glyph comes from and YYY is the decimal number of
+ the glyph in that font (which is a number between 000 and 255
+ inclusive, usually between 33 and 126). The following are
+ values corresponding to X:
-
- <<[[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
- documentation for the TMW font and transcribe this
- yourself.]]>>
-
+- Upon seeing this, you should consult the \tmwXYYY sequence in your output, you should + consult the documentation 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. + glyph (by its YYY value) 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 through the + SourceForge website or via e-mail.
- There is one TMW glyph (TibetanMachineWeb7, glyph 91) that has no - Tibetan Machine equivalent. This glyph is the only TMW glyph - that can cause a TMW->TM conversion to fail. + There is one TMW glyph (TibetanMachineWeb7, glyph 91 [\tmw7091]) + that has no Tibetan Machine equivalent. This glyph is the only + TMW glyph that can cause a TMW->TM conversion to fail. It + is fairly common, though, especially if you've used Jskad to prepare + your document. It might be appropriate to change the document + to use TibetanMachineWeb7, glyph 90 [\tmw7090], a similar glyph that + does have a TM equivalent.
@@ -326,23 +367,37 @@ non-TMW character newline in the font Times New Roman appears first at location
If you ever encounter problems in a TM->TMW conversion, please send us mail with the error report (and the problem input document's - resulting document) so that we can improve our tools. + resulting document) so that we can improve our tools.
- First add Jskad.jar to your CLASSPATH. Now run the command
- java org.thdl.tib.input.TibetanConverter from a
- command prompt. You will see usage information appear.
+ First add Jskad.jar to your CLASSPATH. You can do this by
+ setting an environment variable CLASSPATH to contain the absolute
+ path of the Jskad.jar file and then running the command java
+ org.thdl.tib.input.TibetanConverter. Alternatively, you
+ can use java -cp "c:\my tibetan documents\Jskad.jar"
+ org.thdl.tib.input.TibetanConverter where you put in the
+ appropriate path to Jskad.jar. You will see usage information
+ appear if you do this correctly; you'll see a message like
+ java.lang.NoClassDefFoundError:
+ org/thdl/tib/input/TibetanConverter; Exception in thread
+ "main" if you've not correctly told Java where to find
+ Jskad.jar.
- 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. The glyphs + All known bugs are listed in this section. They're more likely + to be fixed if users complain, so complain away. +
+ ++ First, 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. The glyphs corresponding to the Wylie 'jaskadaskeda' have this problem, for example.