XOM API for Processing XML with Java

[Thomas Hicks <hickst AT theriver.com>]

At 03:39 AM 10/18/2007, you wrote:
> > > In the method nu.xom.UnicodeUtil.decompose(..) (Xom 1.2b)
> > there is a
> > > 1900ish-levels nested if-else statement that causes my Eclipse java
> > > editor to crash when opening the file. Yes, I know it's not a
> > > XOM-fault, but I thought I'd throw it on the list anyway...
>
> I had a few problems with compiler limits in this area in Saxon too, though
> my approach is a bit different. I ended up creating a source module
> containing the raw data in which the lists of integers are represented as
> strings containing comma-separated base-32 values; I then parse the strings
> out into the run-time tables needed to drive the algorithm. Don't ask me why
> it wasn't base-64, I'm sure it made sense at the time.

Could this have been because the Character.MAX_RADIX constant,
used by the String.toString(int i, int radix) method, has a value of 36?
        cheers,
        -tom