[zope2-tracker] [Bug 534500] [NEW] Editing ZopePageTemplate through ftp messes up output_encoding

[Ignas Mikalajūnas]

Public bug reported:

When you upload a new version of a zpt "text/html" template using FTP it
sets output_encoding to iso-8859-15 and decodes the content you are
uploading using iso-8859-15...

This means that even after you fix it in the Properties window through
ZMI, the content still is broken.  I think ftp uploads should preserve
output_encoding property and use the same encoding that was used when
serving the template using FTP instead of defaulting to iso-8859-15.

** Affects: zope2
     Importance: Undecided
         Status: New

** Description changed:

- When you upload a zpt "text/html" template using FTP it sets
- output_encoding to iso-8859-15 and decodes the content you are uploading
- using iso-8859-15...
+ When you upload a new version of a zpt "text/html" template using FTP it
+ sets output_encoding to iso-8859-15 and decodes the content you are
+ uploading using iso-8859-15...
  
  This means that even after you fix it in the Properties window through
  ZMI, the content still is broken.  I think ftp uploads should preserve
  output_encoding property and use the same encoding that was used when
  serving the template using FTP instead of defaulting to iso-8859-15.

-- 
Editing ZopePageTemplate through ftp messes up output_encoding
https://bugs.launchpad.net/bugs/534500
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.