> * In message <[EMAIL PROTECTED]>
> * On the subject of "Re: Postal codes"
> * Sent on 17 Jul 2000 13:16:45 +0200
> * Honorable Alex Schroeder <[EMAIL PROTECTED]> writes:
>
> Sam Steingold <[EMAIL PROTECTED]> writes:
>
> > I think we should keep all phone numbers as strings, and have a user
> > variable bbdb-phone-canonicalize which should be nil for "as is" or a
> > function which is applied to the phone and should return the
> > canonicalized phone string.
> >
> > Same for zip codes (bbdb-zip-canonicalize).
> >
> > Unless someone objects, I will do something like this next week.
>
> Hm, if we have bbdb-zip-canonicalize, then the old problem re-appears:
> whenever a new format of zip codes is "discovered", somebody has to
> update the code.
you missed the whole point!
1. canonicalization can be turned off at any time
2. canonicalization can be user-supplied
3. if canonicalization fails, the string is used as is
--
Sam Steingold (http://www.podval.org/~sds)
Micros**t is not the answer. Micros**t is a question, and the answer is Linux,
(http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation.
Daddy, what does "format disk c: complete" mean?
_______________________________________________
bbdb-info mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/bbdb-info
