[ZCM] [ZC] 1232/ 5 Comment "RAMCache doesn't work with Unicode pages"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1232 Update (Comment) "RAMCache doesn't work with Unicode pages"
 Status Pending, Zope/bug medium
To followup, visit:
  http://collector.zope.org/Zope/1232

==============================================================
= Comment - Entry #5 by limi on May 31, 2004 1:38 pm

Well, not only content carries Unicode characters, and I still think this is a legitimate problem with the RamCacheManager. I don't see why it shouldn't retain the header information?
________________________________________
= Comment - Entry #4 by leper on May 30, 2004 8:43 pm

RAM Cache Manager's aren't intended for caching entire content
pieces destined to be published directly.  This is by design.
If you want to cache published content do so with a caching
gateway server.  This is essentially the same issue as #724.

________________________________________
= Comment - Entry #3 by batlogg on Feb 18, 2004 9:17 am

oops that's too bad. now i know why we had quite some problems on our multilingual site. for us unicode is a key feature.  i'd appreciate to get RAMCache support :)
________________________________________
= Comment - Entry #2 by bartenst on Feb 18, 2004 8:35 am

I totally agree. One of Zope's big advantages are its i18n-capabilities. That RAMCache does not support Unicode pages is a big hassle.
________________________________________
= Request - Entry #1 by limi on Feb 16, 2004 2:34 pm

The RAM Cache part of Zope doesn't keep any header information about charset, making it impossible to use in production on Unicode sites.

All Unicode pages show up with no charset info, and thus the characters are mangled.

Right now, we have to create a separate method that is RAM-cached, and include these in a page that has the correct header, which is less than optimal.
==============================================================