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:
parent
cc5d096918
commit
e2d42f36eb
22 changed files with 1106 additions and 506 deletions
|
@ -390,5 +390,18 @@ public class UnicodeUtils implements UnicodeConstants {
|
|||
&& '\u0F48' != cp
|
||||
&& '\u0F98' != cp);
|
||||
}
|
||||
|
||||
/** Returns true if a character is in the Tibetan range of Unicode
|
||||
4.0 but is a reserved code in that range, not yet assigned to
|
||||
any character. */
|
||||
public static boolean isReservedTibetanCode(char cp) {
|
||||
return (cp == '\u0F48'
|
||||
|| cp == '\u0F98'
|
||||
|| (cp >= '\u0F6B' && cp <= '\u0F70')
|
||||
|| (cp >= '\u0F8C' && cp <= '\u0F8F')
|
||||
|| cp == '\u0FBD'
|
||||
|| (cp >= '\u0FCD' && cp <= '\u0FCE')
|
||||
|| (cp >= '\u0FD0' && cp <= '\u0FFF'));
|
||||
}
|
||||
}
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue