>>>>> "Ronan" == Ronan Waide <[EMAIL PROTECTED]> writes:
Jack> I consider the approach of making multiple records for a single Jack> individual to be worse than a hack job as it totally skews the Jack> meaning of the records and makes incorrect assumptions. Ronan> Actually, given the inexact mapping of the Palm address book to Ronan> the BBDB, I think it's a remarkably good way of handling the Ronan> problem. Any other solution, such as what you propose (putting Ronan> the data into the Notes field) works fine as long as the Notes Ronan> field is used only for extra address data. As soon as you start Ronan> using the notes field for, say, actual notes, you mess things Ronan> up. Actually, it's not so bad. I use the notes field for a whole lot of things (such as driving directions, birthdays, and the like, and it doesn't come out as bad as you think. You get a notes field like this: [Office] 123 Anywhere Road Somewhere, CA 90321 [Birthday] April 25, 1972 [Notes] Drive down Lake Michigan Boulevard and stop. It's a heck of a lot better than multiple records for individual people, in my humble opinion. Jack> (you should also respect X-Attribution settings) Ronan> First I've ever heard of an 'X-Attribution setting'; any header Ronan> beginning with X- is, by definition, non-standard and can be Ronan> treated in any way the MUA sees fit. The X-Attribution header is used by Supercite users to suggest an attribution. My X-Attribution header is set to "Jack". He is using Supercite, and used "J". That annoys me, because it's antisocial. Jack. -- Jack Twilley jmt at twilley dot org http colon slash slash www dot twilley dot org slash tilde jmt slash
msg02811/pgp00000.pgp
Description: PGP signature
