RE: [Zope] Non-ASCII-form-input -> HTML-entities?
Thanks for your answers! I am looking forward for Unicode-Zope, but for now the solution proposed by D. Maurer is sufficient for me. (I suppose it is equally good to insert a Content-Type meta-tag in the standard_html_header?) This one line doesn't hurt, although W. Strobl seems to be right, especially taking into account the following 2 statements in RFC 2616: 'Some HTTP/1.0 software has interpreted a Content-Type header without charset parameter incorrectly to mean "recipient should guess."' but also: 'Unfortunately, some older HTTP/1.0 clients did not deal properly with an explicit charset parameter.' I encountered these problems especially on the Mac (up to Netscape 3, as far as I can remember). But as it seems, the time to care about this misbehaviour is over now. Markus Kemmerling ___ 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] Non-ASCII-form-input -> HTML-entities?
On 3 Jan 2001, at 22:53, Dieter Maurer wrote: > I would instead include a "charset" declaration and > no longer worry about HTML entities for latin 1 characters. > > This is rendundant. ISO-8859-1 is the default encoding for http, anyway, and has ever been. -- Wolfgang Strobl ___ 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] Non-ASCII-form-input -> HTML-entities?
Markus Kemmerling writes: > I would like to have users being able to enter german vowels ä, ö, ü and other >non-ASCII-characters for which HTML-entities exist (ISO 8859-1) into a >form-input-field and have them rendered as HTML-entities by the corresponding var-tag >in the form-handler. > > The 'html_quote'-attribute only seems to convert &, <, and > (and quotes?). Of >course I could write my own python-method with a lot of replaces. But that would >probably mean to reinvent a wheel that already exists (this seems to be a rather >common task to me). Or is there a way to do it in DTML? > > Any help appreciated. I would instead include a "charset" declaration and no longer worry about HTML entities for latin 1 characters. 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] Non-ASCII-form-input -> HTML-entities?
On Wed, 3 Jan 2001 10:33:20 +0100, "Markus Kemmerling" <[EMAIL PROTECTED]> wrote: >I would like to have users being able to enter german vowels Your suggested solution is a good one if you know all your users are german, all using the same browser, all with the correct german configuraton. If not, I strongly recommend using pages encoded in utf-8, and storing your field values as unicode. Everything will then work happily for non-germans too. Standard Zope can't do this yet, you will need the patches at http://www.zope.org/Members/htrd/wstring Toby Dickenson [EMAIL PROTECTED] ___ 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 )
