On August 11, [EMAIL PROTECTED] said: > > For what reason? They were wrong anyway, as I said:
I'd have to go digging in the archives to find out. Since you say it's broken, though, I'll happily remove it. > Yes. The check which would prevent that on saving the file (if I > remember correctly) isn't in the released version. Sorry to hear that. I really try to avoid doing things that corrupt peoples' data. > I fixed it some time ago (although I really shouldn't have listened to > people wanting to share .bbdb with XEmacs, which is fundamentally > losing, and just used emacs-mule encoding). It's just been broken. There's a similar problem here in making BBDB behave itself with XEmacs when it's been compiled with Emacs and vice versa. I really should just put in a run-time check in the compiled version that stops you from swapping the two back and forth, as it'd simplify the code in quite a few places. > Coding conversion is actually quite simple -- you just have to > remember it when converting between internal and external data, > (whether or not the internal form is Unicode based). Noted. Since you seem to be familiar with it, can you comment on the sense or otherwise of the change I made to update the encoding cookie? It feels wrong to be doing it manually; it seems like something Emacs should do for me. Cheers, Waider -- [EMAIL PROTECTED] / Yes, it /is/ very personal of me. "We're having a party in Ronan's tonight, go and buy alcohol." - Gemma ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/