Google's library for dealing with phone numbers (Java/JavaScript)
code.google.com
code.google.com
I often avoid posting java links to HN, thinking that the HN community is more focused on Rails / node.js / python. Guess I should reconsider :)
Funny how this intangible karma stuff affects me :)
Of course, it may not have actually been a wasted opportunity as the (google.com) URL part of the title probably accounts for a large percentage of clicks.
P.S. I upvoted your comment to generate a little more karma as compensation.
Thanks for the upvote, that's kind of you!
In retrospect, I shouldn't have "whined" in my previous comment. As the Facebook quote goes ("If you guys were the inventors of Facebook, you'd have invented Facebook"): had I wanted to post this on HN, I would have posted it on HN!
I'll try to post more links in the future (Java or otherwise), and stop trying to anticipate their success according to some pre-conceived notion of what the HN crowd likes: if I think it is interesting, someone else might like it as well ;)
Did you happen to notice where this is?
http://code.google.com/p/libphonenumber/source/browse/#svn%2...
I'm interested in how the completeness is defined, as the standards available are loose at best. I couldn't see by what measure they considered this work 'complete'.
That complaint aside, it's a great effort to see. Now to test it out...
I am planning on just using the Java version with JRuby - it will probably be faster than a pure ruby version anyway.
Given the usefulness of this library, I've been inspired to give it a go: http://github.com/damncabbage/libphonenumber-php
(Java --> PHP is tough going. Come back in a month. ;) )
After all, if you want to test to see if a number is valid, try and call it.
The problem is this. Although there are hundreds of websites with UK area code lists, almost all of them are either incorrect, out of date, full of typos, or are generally unreliable. Even lists from "official" sources cannot be relied on with any degree of certainty. The obvious errors are easy to find and correct. It took a long time to find out there were many non-obvious errors and there are likely more errors still to be uncovered.
<nitpick>456</nitpick>When everyone is in agreement, the internal Google version is updated with the proposed changes.
Once testing is complete, the java code and metadata is pushed to the public version.
The final steps are to produce the javascript port, and on a less regular basis the .jar file in the "downloads" section is also updated.
See http://www.howtocallabroad.com/ for more information.