Robert Chilton's experience inspired me to make the handling of errors and

warnings in ACIP->Tibetan conversion much more configurable.  You can
now choose from short or long error messages, for one thing.  You can change
the severity of almost all warnings.  Each error and warning has an error code.
Errors and warnings are better tested.

The converter GUI has a new checkbox for short messages; the converter
CLI has a new mandatory option for short messages.

I also fixed a bug whereby certain errors were not being appended to the
'errors' StringBuffer.
This commit is contained in:
dchandler 2004-04-24 17:49:16 +00:00
parent cc5d096918
commit e2d42f36eb
22 changed files with 1106 additions and 506 deletions

View file

@ -14,10 +14,11 @@
// sure to run 'ant clean check' after your change.
//
// Note that some glyphs have EWTS \uF021-\uF0FF inclusive. These do
// not have anything in the Unicode column, though, because this is just
// the EWTS -- if someone wants to convert TMSkt3.183->Unicode and get
// \u0F21, let them do that, but our *->Unicode converters shouldn't
// output codes in the PUA without explicit user authorization.
// not have anything in the Unicode column, though, because this is
// just the EWTS -- if someone wants to convert TMSkt3.183->Unicode
// and get \u0F21, let them do that, but our *->Unicode converters
// shouldn't output codes in the private-use area (PUA) without
// explicit user authorization.
//
// Note that 0F00, 0F02, 0F03, and 0F0E are made by using multiple
// glyphs from TMW. 0F6A is not listed here (DLC FIXME: should it be?