Updated the list of flaws.
This commit is contained in:
parent
3f775383ec
commit
87e98bf636
2 changed files with 35 additions and 2 deletions
|
@ -1486,6 +1486,12 @@ Nativeness</h2>
|
|||
incorrect; a <i>tsheg</i> is inserted right now after the
|
||||
visarga.<!-- DLC FIXME -->
|
||||
</li>
|
||||
<li>
|
||||
<!--DLC FIXME: --> The number of errors after which processing is
|
||||
aborted (under the assumption that the input is probably not ACIP)
|
||||
is absolute, not a per capita measurement (i.e., one error per 100
|
||||
characters of input) and is not easily configured.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
||||
|
@ -1507,6 +1513,26 @@ Nativeness</h2>
|
|||
</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Some warnings are false alarms (false positives). The only
|
||||
known false positive is the warning <tt>[#WARNING CONVERTING ACIP
|
||||
DOCUMENT: There is a chance that the ACIP KshA was intended to
|
||||
represent more consonants than we parsed it as representing --
|
||||
NNYA, e.g., means N+NYA, but you can imagine seeing N+N+YA and
|
||||
typing NNYA for it too.]</tt> when it is given for ACIP
|
||||
constructions that cannot possibly be interpreted any other
|
||||
way. See issue <a
|
||||
href="http://sourceforge.net/tracker/index.php?func=detail&aid=932896&group_id=61934&atid=502515">932896</a>.
|
||||
</li>
|
||||
<li>
|
||||
The only time Unicode output will contain U+0F6A, full-formed RA,
|
||||
instead of U+0F62, RA (possibly superscribed), is when a Unicode
|
||||
escape sequence for U+0F6A is used or when one of the ten stacks
|
||||
RY, RW, RSH, RSHY, Rsh, Rshn, RshnY, RshM, RshY, or RS
|
||||
appears. The Unicode standard is not as clear as it could be
|
||||
on the issue of when to use full-formed code points like U+0F6A,
|
||||
so this treatment might not be the best.
|
||||
</li>
|
||||
<li>
|
||||
The glyph TibetanMachineWeb9.61 -- the {O'I} special combination
|
||||
(i.e., the glyph for the Unicode string U+0F7C,U+0F60,U+0F72) --
|
||||
|
|
|
@ -171,8 +171,8 @@
|
|||
<p>
|
||||
When a TMW->ACIP conversion fails, a message such as
|
||||
<tt>[# JSKAD_TMW_TO_ACIP_ERROR_NO_SUCH_ACIP: Cannot convert
|
||||
<glyph font=TibetanMachineWeb8 charNum=38 character=&/> to
|
||||
ACIP. Please transcribe this yourself.]</tt> will appear in your
|
||||
<glyph font=TibetanMachineWeb8 charNum=39 character='/> to
|
||||
ACIP. Please transcribe this yourself.]</tt> will appear in your
|
||||
output, but it will be amidst the successfully converted text.
|
||||
</p>
|
||||
|
||||
|
@ -315,6 +315,13 @@ Non-TMW character newline [decimal 10] in the font Times New Roman appears first
|
|||
converted: {\u0F3E\u0F28} appears instead. [<a
|
||||
href="http://sourceforge.net/tracker/index.php?func=detail&aid=855480&group_id=61934&atid=502515">855480</a>]
|
||||
</li>
|
||||
<li>
|
||||
TMW->ACIP will sometimes produce spaces (i.e., the ' '
|
||||
character, U+0020) that are supposed to indicate tshegs (i.e., the
|
||||
character U+0F0B) but will instead be interpreted as Tibetan
|
||||
whitespace. [<a
|
||||
href="http://sourceforge.net/tracker/index.php?func=detail&aid=932897&group_id=61934&atid=502515">932897</a>]
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
|
|
Loading…
Reference in a new issue