7198f23361
table exactly and I fear that it makes the ACIP->Tibetan converter code a lot uglier. The TODO(DLC)[EWTS->Tibetan] comments littered throughout are part of the ugliness; they point to the ugliness. If each were addressed, cleanliness could perhaps be achieved. I've largely forgotten exactly what this change does, but it attempts to improve EWTS->Tibetan conversion. The lexer is probably really, really primitive. I concentrate here on converting a single tsheg bar rather than a whole document. Eclipse was used during part of my journey here and some imports were reorganized merely because I could. :) (Eclipse was needed when the usual ant build failed to run a new test EWTSTest. And I wanted its debugger.) Next steps: end-to-end EWTS tests should bring many problems to light. Fix those. Triage all the TODO comments. I don't know that I'll ever really trust the implementation. The tests are valuable, though. A clean implementation of EWTS->Tibetan in Jython might hold enough interest for me; I'd like to learn Python. |
||
---|---|---|
.. | ||
LegalTshegBar.java | ||
LegalTshegBarTest.java | ||
package.html | ||
TibetanSyntaxException.java | ||
TransitionInstruction.java | ||
TshegBar.java | ||
UnicodeCodepointToThdlWylie.java | ||
UnicodeCodepointToThdlWylieTest.java | ||
UnicodeConstants.java | ||
UnicodeGraphemeCluster.java | ||
UnicodeGraphemeClusterTest.java | ||
UnicodeReader.java | ||
UnicodeReadingStateMachineConstants.java | ||
UnicodeReadyThunk.java | ||
UnicodeUtils.java | ||
UnicodeUtilsTest.java | ||
ValidatingUnicodeReader.java | ||
ValidatingUnicodeReaderTest.java |