Lists Home |
Date Index |
- From: Istvan Cseri <email@example.com>
- To: firstname.lastname@example.org, 'Tim Bray' <email@example.com>
- Date: Wed, 3 Sep 1997 15:24:48 -0700
For better speed I would suggest an alternative solution: use a quick
array lookup for characters below 256 and go to the more expensive
method above... It will do wonders with your parser.
> From: Tim Bray[SMTP:firstname.lastname@example.org]
> Reply To: Tim Bray
> Sent: Wednesday, September 03, 1997 12:51 PM
> To: email@example.com
> Subject: Character classification
> <<File: CharClasses.java.txt>>
> I've been working on making Lark really do Unicode. JDK 1.1 is
> to have, unlike 1.0, a usable input method; thus the problem is to
> when you're reading a GI or Attribute name, whether the characters are
> legal namestart/name characters.
> It turns out to be quite a lot of work, so this is an offer to share.
> I wrote a program (based on Lark) that pulls the relevant character
> classes out of the XML spec, picks apart the markup, and writes
> Java class that has some static arrays and offers two methods:
> package textuality.lark;
> public class CharClasses
> public static boolean isNameC(char c)
> public static boolean isNameStart(char c)
> It needs about 4k of tables (which it binary-searches); it might be
> with 128k of byte-addressable tables or 16K of bitmaps, neither of
> would be hard to implement.
> (a) is this a waste of time, i.e. are there Unicode library calls that
> do it?
> (b) if not, has everyone else already done this?
> (c) if not, if I'm going to publish this, is the API above OK?
> I've attached the current Java source file for those who find the
> explanation above insufficiently clear.
> Cheers, Tim Bray
> firstname.lastname@example.org http://www.textuality.com/ +1-604-708-9592
xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to email@example.com the following message;
List coordinator, Henry Rzepa (firstname.lastname@example.org)