Re: [Zope] Character display issues upgrading 2.8.8 to 2.9.8
Aloha, OK, I have now done the upgrade the "right" way, by copying add-in products and data.fs from zope 2.8.8 instance to 2.9.8 instance (on debian 4.0). I still have the same problem occurring. StructuredDocument content that contains curly quotes, curly apostrophes, and some accented (French) chars (and maybe others I haven't spotted yet) is not displaying those chars correctly (they show up as hollow block, black diamond "?", etc. depending on browser). My assumption is that something has changed in character set handling/publishing between 2.8.8 and 2.9.8. I know nothing about zope char set handling (if that's even the right term) - it's never been an issue before. As mentioned the zope.conf settings for default-zpublisher-encoding are left at the default (iso-8859-15) in both instances. 2.8.8 was installed from source. 2.9.8 was installed by the plone 2.5.5 unified installer. I would appreciate any leads on where/how to start fixing this. thanks, John S. John Schinnerer wrote: Aloha, I am in the process of moving from zope 2.8.8 to zope 2.9.8 (running on debian 4.0). I am transferring individual zope sites from 2.8.8 instance to 2.9.8 instance via export/import. So far everything is fine except... I have some content in StructuredDocument objects that includes text with some accented French characters, and some of the curly quotes (the 6--9 quotes) and "real" apostrophes and that sort of thing. They are not displaying correctly in the 2.9.8 zope - they show up as whatever symbol the browser uses to say "oops, can't display this correctly." Both zopes are running on my dev system and I'm looking with all the same browsers so it seems it must be something to do with zope handling the characters (or not). The zope.conf settings for default-zpublisher-encoding are left at the default (iso-8859-15) in both instances, if that is relevant. I've never had any problem like this before, such as in previous upgrades of 2.7.x to 2.8.x. I don't even know where to look, aside from the zope.conf setting above which is the same in both cases. Any ideas why this is happening? Any help appreciated! thanks, John S. -- John Schinnerer, MA WSD -- - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration [EMAIL PROTECTED] http://eco-living.net ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Character display issues upgrading 2.8.8 to 2.9.8
- Original Message - From: "John Schinnerer" <[EMAIL PROTECTED]> Well, it worked last time from 2.7.x to 2.8.x. Not so lucky time I guess. Anyone else have pointers to what I need to know? You need to have right codepage in your system and defined management page charset property too. But these prerequisities does not able to make STX absolutelly sucessfull. I was generate CP1250 locales (I use mandriva), but with Zope 294 they does not run 100% correctly with STX (for example bold text with nationalities is displayed with ** quotation). But STX at Zope 251 (with own very old python) is OK with the same machine. Other thing that does not work with new zope is names of days or months which have national characters. It is question if new zope code or new python is broken, or something else. Does somebody know, which highest Zope version is OK? JL. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Character display issues upgrading 2.8.8 to 2.9.8
Aloha, Andreas Jung wrote: --On 6. Februar 2008 21:21:42 -1000 John Schinnerer <[EMAIL PROTECTED]> wrote: Aloha, I am in the process of moving from zope 2.8.8 to zope 2.9.8 (running on debian 4.0). Why not 2.10 or 2.11? The zope instance also supports some plone 2.5.x sites. Complete upgrade needs to be zope 2.8.8 to 2.9.8 and plone 2.5.0 to 2.5.5. I have installed the new versions using the unified installer. Does that make this impossible? Should I just move this whole question to plone list? I started it here because I'm having only this one zope problem so far... I am transferring individual zope sites from 2.8.8 instance to 2.9.8 instance via export/import. So far everything is fine except... ..which is basically unsupported since source and destination system run different Zope versions. Well, it worked last time from 2.7.x to 2.8.x. Not so lucky time I guess. Anyone else have pointers to what I need to know? When I search zope.org for "upgrade zope" the only relevant article on the first three pages of results was last updated in August 2003 and is useless. Google doesn't get me anything much better. There is no upgrade information on or linked from the zope 2.9.8 release pages. I found some generic info on the zope wiki finally, however of course it doesn't cover plone upgrades. thanks, John S. -- John Schinnerer, MA WSD -- - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration [EMAIL PROTECTED] http://eco-living.net ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Character display issues upgrading 2.8.8 to 2.9.8
Aloha, I am in the process of moving from zope 2.8.8 to zope 2.9.8 (running on debian 4.0). I am transferring individual zope sites from 2.8.8 instance to 2.9.8 instance via export/import. So far everything is fine except... I have some content in StructuredDocument objects that includes text with some accented French characters, and some of the curly quotes (the 6--9 quotes) and "real" apostrophes and that sort of thing. They are not displaying correctly in the 2.9.8 zope - they show up as whatever symbol the browser uses to say "oops, can't display this correctly." Both zopes are running on my dev system and I'm looking with all the same browsers so it seems it must be something to do with zope handling the characters (or not). The zope.conf settings for default-zpublisher-encoding are left at the default (iso-8859-15) in both instances, if that is relevant. I've never had any problem like this before, such as in previous upgrades of 2.7.x to 2.8.x. I don't even know where to look, aside from the zope.conf setting above which is the same in both cases. Any ideas why this is happening? Any help appreciated! thanks, John S. -- John Schinnerer, MA WSD -- - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration [EMAIL PROTECTED] http://eco-living.net ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )