From caf446544638ca5c46284e96a8e198977f0016e9 Mon Sep 17 00:00:00 2001 From: dchandler Date: Mon, 15 Dec 2003 08:15:39 +0000 Subject: [PATCH] Updated. --- htdocs/ACIP_To_Tibetan_Converter.html | 27 ++++++++++++++++----------- 1 file changed, 16 insertions(+), 11 deletions(-) diff --git a/htdocs/ACIP_To_Tibetan_Converter.html b/htdocs/ACIP_To_Tibetan_Converter.html index c827c21..d0c47f5 100644 --- a/htdocs/ACIP_To_Tibetan_Converter.html +++ b/htdocs/ACIP_To_Tibetan_Converter.html @@ -101,9 +101,9 @@
  • Some transliterations specified by the ACIP standard are not accepted (i.e., they cause errors) - because they are used too often improperly in Release IV texts + because they are used too often improperly in Release V texts (e.g., {\}); some non-standard transliteration is understood - because it is used in ACIP Release IV texts (e.g., {[DD1]}). + because it is used in ACIP Release V texts (e.g., {[DD1]}).
  • Non-standard Unicode character escapes are @@ -126,7 +126,7 @@
  • The "lexical analyzer" and "parser" handle every intricacy of - real ACIP Release IV texts. + real ACIP Release V texts.
  • The knowledge regarding the TMW font has been verified by @@ -636,7 +636,7 @@ Now that the basic operation is clear from the above example, let's cover the fine points of how standard ACIP is handled.  We'll also cover some non-standard constructs that appear commonly in - actual ACIP Release IV texts. + actual ACIP Release V texts.

    @@ -771,7 +771,7 @@ TIBETAN FONT AND NEEDS TO BE REDONE BY DOUBLE INPUT]"

    The converter also supports several non-standard folio - markers.  A review of ACIP Release IV texts determined that the + markers.  A review of ACIP Release V texts determined that the following types of folio markers can appear:

    @@ -789,7 +789,7 @@ TIBETAN FONT AND NEEDS TO BE REDONE BY DOUBLE INPUT]"

    - Similarly, to support real ACIP Release IV texts, the converter + Similarly, to support real ACIP Release V texts, the converter treats {[DD1]}, {[DD2]}, {[ DD ]}, and {[DDD]} just like {[DD]} (which is specified in the ACIP standard).  It treats {[ BP ]} and {[BLANK PAGE]} just like {[BP]}, also. @@ -797,7 +797,7 @@ TIBETAN FONT AND NEEDS TO BE REDONE BY DOUBLE INPUT]"

    The lists above were created by a most fallible process of reviewing - a large number of ACIP Release IV texts.  Your suggestions for + a large number of ACIP Release V texts.  Your suggestions for additions to these lists are highly valued; please contact the developers. @@ -866,7 +866,7 @@ GA

    Though the ACIP standard does not mention it, it appears that some - ACIP Release IV texts use a period (i.e., {.}) to indicate a + ACIP Release V texts use a period (i.e., {.}) to indicate a non-breaking tsheg (i.e., U+0F0C).  Search for {NGO.,}, {....,DAM}, etc.  Unless {,}, {.}, or a letter (i.e., a through z) follows the {.}, it is only grudingly interpreted as a @@ -1472,7 +1472,7 @@ Nativeness href="http://sourceforge.net/tracker/index.php?func=detail&aid=855519&group_id=61934&atid=502515">855519]

  • - A folio marker {@0B1} can appear; it gives an error at present. + A folio marker {@0B1} can appear in ACIP Release V texts; it gives an error at present.
  • The treatment of the very last line in an input text may be buggy @@ -1483,6 +1483,12 @@ Nativeness incorrect; a tsheg is inserted right now after the visarga.
    • +
  • + The ACIP {?} is treated questionably as being equivalent to + {\u003F}.  This may indicated U+0F08; until the confusion is + resolved, this should cause an error.  [860192] +
    • @@ -1574,8 +1580,7 @@ Nativeness
  • Default substitution rules should handle - {KAsh}, which seems to always mean {K+sh} in ACIP Release IV - texts. + {KAsh}, which seems to always mean {K+sh} in ACIP Release V texts.