Re: survey: zope 2.7 syntax errors with TAL statments over multiple lines
I'm experiencing the same sort of problem as you - e.g., these lines (which happen to be from the epoz_toolbox.pt):
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" tal:define="charset here/portal_properties/site_properties/default_charset; dummy python:request.RESPONSE.setHeader('Content-Type', 'text/html;;charset=%s' % charset)" tal:attributes="content string:text/html;;charset=${charset}" />
produced an error before I moved the 2 tal:define clauses up onto one line.
very weird
I was able to fix the problem by creating a new file, copy/pasting the contents of the original file into the new file, and saving it under the same name. I'm running everything in Linux. - Gerry
Gerry Kirk wrote:
I'm experiencing the same sort of problem as you - e.g., these lines (which happen to be from the epoz_toolbox.pt):
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" tal:define="charset here/portal_properties/site_properties/default_charset; dummy python:request.RESPONSE.setHeader('Content-Type', 'text/html;;charset=%s' % charset)" tal:attributes="content string:text/html;;charset=${charset}" />
produced an error before I moved the 2 tal:define clauses up onto one line.
very weird
I was able to fix the problem by creating a new file, copy/pasting the contents of the original file into the new file, and saving it under the same name. I'm running everything in Linux.
That smells like a line-ending problem; could the original epoz_toolbox.pt have ^N characters embedded in it? Tres. -- =============================================================== Tres Seaver tseaver@zope.com Zope Corporation "Zope Dealers" http://www.zope.com
On Fri, 2004-01-09 at 09:21, Gerry Kirk wrote:
I'm experiencing the same sort of problem as you - e.g., these lines (which happen to be from the epoz_toolbox.pt):
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" tal:define="charset here/portal_properties/site_properties/default_charset; dummy python:request.RESPONSE.setHeader('Content-Type', 'text/html;;charset=%s' % charset)" tal:attributes="content string:text/html;;charset=${charset}" />
produced an error before I moved the 2 tal:define clauses up onto one line.
very weird
I was able to fix the problem by creating a new file, copy/pasting the contents of the original file into the new file, and saving it under the same name. I'm running everything in Linux.
- Gerry 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
participants (3)
-
Gerry Kirk -
larry j.c. prikockis -
Tres Seaver