thdltools/Jskad
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
648 commits 1 branch 0 tags 10 MiB
Commit graph

92 commits

Author SHA1 Message Date
eg3p
a39d5c2ba3 changed all occurrences of 'Color.BLACK' to 'Color.black', since the former causes a runtime error on Mac OS X (for Java 1.3.1 at least). not sure why this is, but may be related to the bug mentioned at http://www.oxygenxml.com/forum/viewtopic.php?p=239 2004-08-19 14:59:06 +00:00
dchandler
7acbce3361 Added errors 142 and 143, which are produced when converting yig chung 
to a Unicode text file, which cannot support font size changes.
 2004-06-06 21:59:16 +00:00
dchandler
df262aa148 It is now a compile-time option whether to treat []- and {}-bracketed sequences 
as text to be passed through (without the brackets in the case of {}) literally,
which is the case by default because Robert Chilton requested it, or the old,
ad-hoc mechanism which could be useful for finding some ugly input.

Made a couple of error messages a little more verbose now that we have
short-message mode.
 2004-06-06 21:39:06 +00:00
dchandler
8a9271a3d8 I broke warning 507 into two warnings, one high-priority (512) and one 
low-priority (507).
 2004-05-01 20:49:53 +00:00
dchandler
1a055f3472 I don't think warning level "None" was really doing the trick. Fixed that. 
You can now customize the severities of all warnings, even 504 and 510.

When warning level is "None", scanning, i.e. lexical analysis, is faster.
 2004-04-25 00:37:57 +00:00
dchandler
e2d42f36eb 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.
 2004-04-24 17:49:16 +00:00
dchandler
0ee90a0fb0 Added many ACIP->TMW->ACIP tests. They found no bugs. 2004-04-17 17:28:26 +00:00
dchandler
de3a19761e Fixes for javadoc tool. 2004-04-17 15:48:50 +00:00
dchandler
adcf9de952 Two new tests. 2004-04-17 15:14:46 +00:00
dchandler
1bfd3772e6 TMW->ACIP is much improved. V and W were confused, # and * were 
confused; many glyphs that should have yielded errors were not.

I've added a test case that transforms every TMW glyph save the one with
no TM mapping to ACIP.  I hand-checked that it was correct.

ACIP->TMW is fixed for # and *.  I never noticed it, but each needed an
extra swoosh (U+0F05).

Round-tripping would be good, as would testing real-world use of
TMW->ACIP.
 2004-04-14 05:44:51 +00:00
dchandler
7eca276a62 TMW->Unicode conversions have changed; now using U+0F6A for the stacks 
whose EWTS transliteration begins with "R+".

ACIP->* conversions and test baselines were updated to deal with the
"r+..."=>"R+..."  change.
 2004-04-10 16:03:25 +00:00
dchandler
76356f4009 ACIP->Tibetan now gives an error when {?} is seen alone (not in {[?]} or {[*FOO?]}, but alone). Bug 860192 is fixed. 2004-03-15 00:49:01 +00:00
dchandler
274e1736be Deleted cut-and-paste goof. 2004-01-17 19:45:31 +00:00
dchandler
c69ba26c60 TString now has tracks what Roman transliteration system it is using. Next up is to make ACIPConverter handle EWTS or ACIP TStrings. 2004-01-17 19:28:54 +00:00
dchandler
c1aa81e943 RFE 860190: ACIP->Unicode now gives a warning when it outputs something that can't be represented in TMW. 2003-12-16 07:45:40 +00:00
dchandler
848349fd3a More tests. 2003-12-15 08:16:06 +00:00
dchandler
e7a9e7968f ACIP->Unicode now uses two characters for consonants instead of one. This matches the dislike for characters like U+0F77 etc. 
ACIP->Tibetan was not giving an error for BCWA because it parsed like BCVA.  Fixed.
 2003-12-15 07:32:14 +00:00
dchandler
e9f7b2dfed If you want curly brackets around folio markers, you'll have to set 
the system property
thdl.acip.to.x.output.curly.brackets.around.folio.markers to true.
 2003-12-14 08:47:03 +00:00
dchandler
8664571577 Warnings were not being detected correctly. Fixed. 
ACIP->Unicode uses U+0020, ' ', for whitespace.  ACIP->TMW uses the
TMW whitespace for whitespace.
 2003-12-14 08:38:10 +00:00
dchandler
01e65176d4 Using less memory and time to figure out if warnings occurred. 2003-12-14 07:41:15 +00:00
dchandler
76c2e969ac Fixed ACIP->Unicode bug for YYE etc., things with full-formed 
subjoined consonants and vowels.

Fixed ACIP->TMW for YYA etc., things with full-formed subjoined
consonants.
 2003-12-14 07:36:21 +00:00
dchandler
f625c937ee ACIP {B} was not being treated like {BA}; instead, an error was resulting. All the five prefixes were affected. 2003-12-14 05:54:07 +00:00
dchandler
581643cf59 {DAN,\nLHAG} used to be treated like {DAN, LHAG} but that got broken. Fixed. 
Added tests for lexer's handling of ACIP spaces etc.
 2003-12-10 06:55:16 +00:00
dchandler
8e673bbc2c {NGA,} becomes {NGA\u0f0c,} now instead of {NGA\u0f0b,}. 
Note: ACIP->Unicode for {NGA,} was not giving the Unicode that {NGA\u0f0b,} gives before.
 2003-12-10 06:50:14 +00:00
dchandler
a466bad939 ACIP->TMW now supports EWTS PUA {\uF021}-style escapes. Our extended ACIP is thus TMW-complete and useful for testing. 2003-12-08 07:51:45 +00:00
dchandler
a39c5c12b0 ACIP->TMW now supports EWTS PUA {\uF021}-style escapes. Our extended ACIP is thus TMW-complete and useful for testing. 2003-12-08 07:15:27 +00:00
dchandler
b617f761d5 ACIP->TMW for {^GONG SA } used to fail; fixed. 2003-12-07 20:05:41 +00:00
dchandler
c43e9a446b Revamped some ACIP->Tibetan error messages. 2003-12-06 20:19:40 +00:00
dchandler
c9c771d1ee ACIP {&}, as in {KO&HAm,}, is supported. 2003-11-30 02:18:59 +00:00
dchandler
ac412c994b Now {Pm} is treated like {PAm}; {Pm:} is like {PAm:}; {P:} is like {PA:}. 2003-11-30 02:06:48 +00:00
dchandler
dfaae4be93 ACIP->TMW and ACIP->Unicode now allow for Unicode escapes like K\u0F84. This means that the lack of support for ACIP's backslash, '\\', is mitigated because you can turn ACIP {K\} into ACIP {K\u0F84}. 
Support for U+F021-U+F0FF, the PUA that the latest EWTS uses, is not provided.
 2003-11-29 22:56:18 +00:00
dchandler
4e6a9c299f ACIP % {MTHAR%} and o {Ko} and ^ {^GONG SA} are now supported. A % always causes a warning. 2003-11-11 03:43:11 +00:00
dchandler
2cb90bd231 ACIP->Tibetan converters now warn every time {%} is encountered that U+0F14 might've been intended. 
The Unicode for ACIP {o} is U+0F37.
 2003-11-09 23:15:58 +00:00
dchandler
04816acb74 ACIP->Unicode was broken for KshR, ndRY, ndY, YY, and RY -- those 
stacks that use full-form subjoined RA and YA consonants.

ACIP {RVA} was converting to the wrong things.

The TMW for {RVA} was converting to the wrong ACIP.

Checked all the 'DLC' tags in the ttt (ACIP->Tibetan) package.
 2003-11-09 01:07:45 +00:00
dchandler
e3f1ed5914 Removed a DOS EOF character (^Z). I haven't a clue how it crept in -- the lexer doesn't let that kind of thing get into tsheg bars. 2003-10-27 13:58:45 +00:00
dchandler
94a43d3f39 Now anything not clearly native Tibetan is colored green when coloring is enabled. G'EEm is "native", though -- the only "vowel" that implies non-nativeness is {:}, as in {KA:}. 2003-10-26 18:56:48 +00:00
dchandler
5c36dd81d3 Fixed bug 830332, "Convert selected ACIP=>Tibetan busted". 2003-10-26 18:25:25 +00:00
dchandler
e74547d743 GA-YOGS now parses like G-YOGS and GAYOGS do. 2003-10-26 18:06:38 +00:00
dchandler
61cf19932e ACIP {B5} and {7'} were problematic; that's fixed. 2003-10-26 17:47:35 +00:00
dchandler
ad7b20e485 Added yet more metadata. 2003-10-26 16:05:30 +00:00
dchandler
1550fee41a Removed garbage. 2003-10-26 16:05:07 +00:00
dchandler
fe33d67573 Added more metadata. There are 35 million+ tsheg bars here. 2003-10-26 15:35:08 +00:00
dchandler
050666d735 I'm committing this at 1:55 am EST on Sunday, October 26, 2003. There 
is no compelling technical reason, but this way I get to have two
commits that are both before and after each other.

Freaky.
 2003-10-26 06:56:12 +00:00
dchandler
31b3020d07 Added a test case that runs almost all the tsheg bars from all 
non-reference, publicly available ACIP files (hundreds of megabytes of
them) through the converter.  The frequencies of these tsheg bars in
in the file, too.
 2003-10-26 06:02:48 +00:00
dchandler
7ba1ad0735 Added a mechanism for end users to have the ACIP/EWTS=>Tibetan converters print all tsheg bars or all unique tsheg bars to standard output. This will be useful for getting a list of all the tsheg bars in ACIP texts, e.g., which can then go into PackageTest.java. A lot of postprocessing would be required to get frequency counts, but you could do it with a perl script, awk, etc. 2003-10-26 02:42:06 +00:00
dchandler
ef24c608bf Added a mechanism for end users to customize ACIP/EWTS=>Tibetan conversions by giving a list of substitutions to be performed. E.g., when I invoke Jskad via 'java -Dorg.thdl.tib.text.ttt.VerboseReplacementMap=false -Dorg.thdl.tib.text.ttt.ReplacementMap="KAsh=>K+sh" -jar Jskad.jar', then the ACIP KAsh becomes K+sh automatically. 
This mechanism is for Andres (who noticed KAsh=>K+sh in practice) and power users only, and not power users until I document the thing outside of the source code.
 2003-10-26 02:17:19 +00:00
dchandler
6bda550157 The ACIP "BNA" was converting to B-NA instead of B+NA, even though NA cannot take a BA prefix. This was because BNA was interpreted as root-suffix. In ACIP, BN is surely B+N unless N takes a B prefix, so root-suffix is out of the question. 
Now Jskad has two "Convert selected ACIP to Tibetan" conversions, one with and one without warnings, built in to Jskad proper (not the converter, that is).
 2003-10-26 00:32:55 +00:00
dchandler
306cf2817c Private correspondence with Robert Chilton led to me to add and remove a few prefix rules. BLC and BGL are here, BLK, BLG, BLNG, BLJ, BNG, BJ, BNY, BN, and BDZ are gone. 
Added a few new tests.
 2003-10-25 21:47:34 +00:00
dchandler
7d24ab393f Code cleanup. 2003-10-21 03:44:02 +00:00
dchandler
c764eee8d0 Added a new warning for DMAR and others affected similarly affected by prefix rules, where seeing D+MAR, not D-MAR, could have caused an input operator to type in DMAR. This is a "Most" warning, but DMA causes a higher-priority "Some" warning. 2003-10-21 03:36:57 +00:00