No commit message

in order to make the sniffing a bit configurable for instances
working with encodings other than iso-8859-15 or utf-8

- the ZMI edit view now *always* uses 'utf-8' and no longer uses self.output_encoding (which is only relevant for FTP/WebDAV)
- 'output_encoding' is now a property

/Zope/branches/ajung-zpt-encoding-fixes

This branch fixes several encoding issues with the ZopePageTemplate
implementation, some webdav issues and now uses unicode internally
for ZPT instances (but not for the PageTemplate(File) classes)
                         

from a <meta http-equiv..> tag

necessary for pt_edit() calls where the encoding should not be changed
by sniffing inside the content (used by pt_editAction(), ZMI and by
the constructor)

- moved the encoding detection into pt_edit() to make it available in a single place

as encoding if the encoding could not be determined from the body text

(should be fixed in Zope 3)

the PUT factory now tries to detect the encoding of uploaded contenthe PUT factory now tries to detect the encoding of uploaded contentt

- PUT() now uses pt_edit() in order to play nicely
  with encoded text. We *except* the the encoding of the uploaded
  text is the same as the original encoding (self.output_encoding)

- add pt_render() in order to convert result of PageTemplate.pt_render()  - returned as unicode - 
  to the output_encoding
- __call__() sets the charset property of the conent-type header according to the output encoding

Collector #2187: PUT_factory broken.

- test.py lives in ZOPE_HOME for checkouts and ZOPE_HOME/bin for
  installations.
- Comparing abspaths does not fly when symlinks are involved; use
  realpaths instead.