• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
natural language date parsing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

natural language date parsing


  • Subject: natural language date parsing
  • From: Mike Schrag <email@hidden>
  • Date: Tue, 31 Oct 2006 18:35:15 -0500

Not really WO-specific, but I thought people might find use in this:

Last weekend I ported ruby's natural language date parser "Chronic" to Java. If anyone is interested, it's located at https:// jchronic.dev.java.net/ . It's released under the same license as chronic (MIT) and the source and binary jar are available under the Documents & Files section. The original didn't support anything other than English, so right now the Java one inherits these same limitations. If there is interest, I would need some support on other languages, but it is possible to do. It's also a not-1.0 port of a not-1.0 library :), so it will have some issues, but it's kind of a cool little library the original guy wrote.

Also, it's written with 1.5 as I am now spoiled and can never go back.

If you want to read the original ruby docs on it, you can go to http://chronic.rubyforge.org/ .

For those who are curious, the Java version is about about 12% more code than the Ruby version (when you count "real" code lines -- I count semicolons and open curlies in Java to get that, and I don't recall what I used on Ruby, but I tried to be fair), and the Java version runs between 2 and 3 times faster than the Ruby version.

ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Re: Is it bad to put Objects in EO derived classes
  • Next by Date: OT: database clusering & failover
  • Previous by thread: Re: Is it bad to put Objects in EO derived classes
  • Next by thread: OT: database clusering & failover
  • Index(es):
    • Date
    • Thread