Small correction.
This commit is contained in:
parent
146c778348
commit
cd41dffce1
1 changed files with 13 additions and 5 deletions
|
@ -307,6 +307,18 @@ Non-TMW character newline [decimal 10] in the font Times New Roman appears first
|
|||
|
||||
<h4>TMW to Wylie</h4>
|
||||
|
||||
<p>
|
||||
<font color="red">
|
||||
This section is too up-to-date -- this is documenting plans for the
|
||||
future. At present, an error message like
|
||||
<code><<[[JSKAD_TMW_TO_WYLIE_ERROR_NO_SUCH_WYLIE: Cannot
|
||||
convert DuffCode <duffcode font=TibetanMachineWeb7 charNum=72
|
||||
character=H/> to THDL Extended Wylie. Please see the
|
||||
documentation for the TMW font and transcribe this
|
||||
yourself.]]>></code> appears.
|
||||
</font>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Note that some TMW glyphs have no transliteration in Exteded
|
||||
Wylie. When you encounter such a glyph, you'll find
|
||||
|
@ -420,11 +432,7 @@ Non-TMW character newline [decimal 10] in the font Times New Roman appears first
|
|||
</p>
|
||||
|
||||
<p>
|
||||
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.
|
||||
There are no known bugs at present.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
Loading…
Reference in a new issue