On Wed, 18 Apr 2007, Earle Martin wrote:
Unfortunately I lost it in a browser crash, but the only possible culprit I could think of would be the £ symbol, which seems unlikely. I replaced it with £ to no effect. I'll try and recreate the case again when I have some time, probably tomorrow.
Try with a pound sign, before and after setting the dbencoding flag (you might need to reload the edit page after setting it). I think setting dbencoding to utf8 should fix it for you, as that's what I had to do for the cotswolds openguide
Nick