I'm almost certain it has to do with zope 2.7. I have the same problems on win32 and it started when I migrated to 2.7. I think someone posted it as a bug in the zope collector. "Gerry Kirk" <gerry@faithonline.com> wrote in message news:6F67E26361CE3A43A364CFE4A8B66BE6483061@server.central.local...

...

upon further inspection, it seems that the problem is related to improperly escaped tab characters (and, I'm guessing, CR/LF, etc). At least in my case, I'm sure it has something to do with the fact that I run Zope on linux, but edit files in a combination of browser textboxes on both Windows and Linux, as well as via external editor (again, on multiple platforms).

I'm not sure that it's anything more than a coincidence that we're seeing this all of a sudden with Zope 2.7. Are you using Plone as well? -- larry j.c. prikockis <larry_prikockis@natureserve.org> NatureServe

All I know is the day I switched to 2.7 from 2.6.2, I *immediately* ran into these problems. The exact same code ran fine in 2.6.2.

However the stuff is being escaped / formatted, it seems to be handled differently in the two. Maybe 2.7 is more strict and correct, I dunno.

Gerry

------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html