At 02:06 AM 15/11/2006, Jim Ramsay wrote: >Werner Fleck wrote: > > Today I upgraded python from 2.3.5 to 2.4.1 and reinstalled tmda-cgi, > > but without success, the error remains. > >That is good to know. Can you please send me a message that's >causing the problem?
Well I look at it this way. It's really simple. If I can't read it because it's in a character set and language I can't read, then it's pretty useless sending it to me in the first place and I'd delete it regardless. So I've found my shell "for" loop works wonders. A minor inconvenience at this time to run manually, but there seem to only be three or four variations according to my logs and as far as I'm concerned, a cronjob that runs a bash script isn't much effort in the long term :) An array of strings that need to be searched is easy to add to in the future. In fact, why not just build such a feature into tmda-cgi - when you run the pending view, if you have "delete all unicode guff" turned on, voila! Gone! Maybe a "list box" that allows us to enter more unicodes to delete ;) (Oh I'm so evil!) Seriously, no on e on the planet is going to send me unicoded character set rubbish expecting me to read it to decode it. I personally have little respect for someone who sends me rubbish! >I'll still haven't been able to replicate this myself. I sent you a private re my server. _____________________________________________ tmda-users mailing list (tmda-users@tmda.net) http://tmda.net/lists/listinfo/tmda-users
