Re: [Zope] Zope 2.3.0b2 bug #2
Oleg Broytmann wrote: > > On Mon, 22 Jan 2001, Dieter Maurer wrote: > > Oleg Broytmann writes: > > >Hm, will you fix my browser, too? I am using Netscape for Linux, don't > > > know how well it plays with Unicode. I suppose it plays bad :( > > We use Netscape (4.5, 4.7; Linux, Windows) with "charset=utf-8" and > > it handles it well. > >Good news, thanks. Are there (free) Unicode fonts for X? If your X server supports ttf you could use the ones from windows (or microsoft website). You could also use the Bitstream Cyberbit fonts that are available at least from ftp://ftp.funet.fi/pub/mirrors/ftp.netscape.com/pub/communicator/extras/fonts/windows/ I'm not sure about their legal status though ;( > What should I > do if I want to save an HTML to disk? (I want plain text, of course, in my > preferred encoding... probably need to write Unicode-to-koi8 converter) That should be trivial in python 2.0 -- Hannu ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] Zope 2.3.0b2 bug #2
On Mon, 22 Jan 2001, Dieter Maurer wrote: > Oleg Broytmann writes: > >Hm, will you fix my browser, too? I am using Netscape for Linux, don't > > know how well it plays with Unicode. I suppose it plays bad :( > We use Netscape (4.5, 4.7; Linux, Windows) with "charset=utf-8" and > it handles it well. Good news, thanks. Are there (free) Unicode fonts for X? What should I do if I want to save an HTML to disk? (I want plain text, of course, in my preferred encoding... probably need to write Unicode-to-koi8 converter) Oleg. Oleg Broytmann http://www.zope.org/Members/phd/ [EMAIL PROTECTED] Programmers don't die, they just GOSUB without RETURN. ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] Zope 2.3.0b2 bug #2
Oleg Broytmann writes: >Hm, will you fix my browser, too? I am using Netscape for Linux, don't > know how well it plays with Unicode. I suppose it plays bad :( We use Netscape (4.5, 4.7; Linux, Windows) with "charset=utf-8" and it handles it well. Dieter ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.3.0b2 bug #2
On Mon, 22 Jan 2001, Michael Bernstein wrote: > >Sure. Language/encoding issues are hard to implement, though. There are > > servers, proxies, browsers - and almost none of them obey standards > > correctly :( > > The chosen language/encoding solution will likely have to be > implemented along with some sort of language/encoding policy > interface, so that the exact behaviour can be set by the > server administrator, and possibly overridden by managers at > different points in the tree. No, this force to choose one encoding for a subtree. Wrong way - we, poor Russians use different encodings for different OSes. UNIX users use KOI8-R, Windows uses windows-1251, DOS and OS/2 users still use old CP866 encoding. This is browser issue, not server-side, and site admin should NOT force any encoding. Oleg. Oleg Broytmann http://www.zope.org/Members/phd/ [EMAIL PROTECTED] Programmers don't die, they just GOSUB without RETURN. ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.3.0b2 bug #2
Oleg Broytmann wrote: > > On Mon, 22 Jan 2001, Brian Lloyd wrote: > > FYI - I've taken out the charset declaration altogether for beta 3, > >Thanks. > > > since this is obviously an issue that needs more thought. Since > >Sure. Language/encoding issues are hard to implement, though. There are > servers, proxies, browsers - and almost none of them obey standards > correctly :( The chosen language/encoding solution will likely have to be implemented along with some sort of language/encoding policy interface, so that the exact behaviour can be set by the server administrator, and possibly overridden by managers at different points in the tree. I would suggest that the default setting (in the startup script) be fully standards compliant, but a systems administrator should still be able to select another behaviour for Zope if they wish (including disallowing managers to override). Sorry this is a bit vague, need coffee. Michael Bernstein. ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] Zope 2.3.0b2 bug #2
On Mon, 22 Jan 2001, Brian Lloyd wrote: > FYI - I've taken out the charset declaration altogether for beta 3, Thanks. > since this is obviously an issue that needs more thought. Since Sure. Language/encoding issues are hard to implement, though. There are servers, proxies, browsers - and almost none of them obey standards correctly :( > Zope 2.4 will be the Python 2 (unicode) release, we should start > a fishbowl project to work out how / whether Zope should deal with > charset issues for the 2.4 release... Hm, will you fix my browser, too? I am using Netscape for Linux, don't know how well it plays with Unicode. I suppose it plays bad :( My only hope is to have Mozilla at the time of Zope 2.4. Anyone here knows how Mozilla handles Unicode? Oleg. Oleg Broytmann http://www.zope.org/Members/phd/ [EMAIL PROTECTED] Programmers don't die, they just GOSUB without RETURN. ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] Zope 2.3.0b2 bug #2
> > >This is WRONG way of doing! Please stop it and don't do it > :) Meanwhile > > > - where I can turn this off? > > > > It would be very nice, if we could set it somewhere in configuration. > > Till now (Zope 2.2.x) I have to patch Zope (some *.dtml files, and even > > some *.py files) in order to have proper Content-Type headers on my > > management screens (specifically iso-8859-2). > >Oh, NO! This should be handled in HTTP, not HTML! HTTP responce shold > give correct Conten-Type header. >With Apache, it is easy to configure. But I certainly don't want to > force all my editors to use one fixed encoding. This because some > of us use > KOI8-R encoding (UNIX), and other use windows-1251 (gues the OS). This is > at least browser/user preference, not a server-side option. >Russian Apache (specially patched version of Apache) correctly handles > this on HTTP level... FYI - I've taken out the charset declaration altogether for beta 3, since this is obviously an issue that needs more thought. Since Zope 2.4 will be the Python 2 (unicode) release, we should start a fishbowl project to work out how / whether Zope should deal with charset issues for the 2.4 release... Brian Lloyd[EMAIL PROTECTED] Software Engineer 540.371.6909 Digital Creations http://www.digicool.com ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.3.0b2 bug #2
On Sat, 20 Jan 2001, Aleksander Salwa wrote: > > > > > >This is WRONG way of doing! Please stop it and don't do it :) Meanwhile > > - where I can turn this off? > > It would be very nice, if we could set it somewhere in configuration. > Till now (Zope 2.2.x) I have to patch Zope (some *.dtml files, and even > some *.py files) in order to have proper Content-Type headers on my > management screens (specifically iso-8859-2). Oh, NO! This should be handled in HTTP, not HTML! HTTP responce shold give correct Conten-Type header. With Apache, it is easy to configure. But I certainly don't want to force all my editors to use one fixed encoding. This because some of us use KOI8-R encoding (UNIX), and other use windows-1251 (gues the OS). This is at least browser/user preference, not a server-side option. Russian Apache (specially patched version of Apache) correctly handles this on HTTP level... Oleg. Oleg Broytmann http://www.zope.org/Members/phd/ [EMAIL PROTECTED] Programmers don't die, they just GOSUB without RETURN. ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.3.0b2 bug #2
On Sat, 20 Jan 2001, Oleg Broytmann wrote: >Zope now sends all HTML in management screens with > > > >This is WRONG way of doing! Please stop it and don't do it :) Meanwhile > - where I can turn this off? It would be very nice, if we could set it somewhere in configuration. Till now (Zope 2.2.x) I have to patch Zope (some *.dtml files, and even some *.py files) in order to have proper Content-Type headers on my management screens (specifically iso-8859-2). [EMAIL PROTECTED], [EMAIL PROTECTED] /--\ | `long long long' is too long for GCC | \--/ ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )