Dieter Maurer wrote:
Tino Wildenhain wrote at 2006-1-13 16:45 +0100:
...
Maybe just have new uZPT with Unicode and leave the "old" ZPT allone?
Maybe with limited ability to "add" old ZPT from ZMI or such.
This would solve the backward-compatibility problems and would be a more
smooth transitio
Dieter Maurer schrieb:
> Tino Wildenhain wrote at 2006-1-13 16:45 +0100:
>
>>...
>>Maybe just have new uZPT with Unicode and leave the "old" ZPT allone?
>>Maybe with limited ability to "add" old ZPT from ZMI or such.
>>
>>This would solve the backward-compatibility problems and would be a more
>>s
Tino Wildenhain wrote at 2006-1-13 16:45 +0100:
> ...
>Maybe just have new uZPT with Unicode and leave the "old" ZPT allone?
>Maybe with limited ability to "add" old ZPT from ZMI or such.
>
>This would solve the backward-compatibility problems and would be a more
>smooth transition w/o the need of
Martijn Faassen wrote at 2006-1-13 13:25 +0100:
> ...
>What about input? If I have an input form, browsers tend to submit in
>the encoding that the form as in, for instance UTF-8. This means I get
>UTF-8 strings into my request.
Of course, (textual) input should be converted to Unicode as well.
Andreas Jung schrieb:
...
>> Now, if I have code that takes something from that request and displays
>> it in a unicode page template, you'd have a problem, as you'd be mixing
>> UTF-8 with unicode there. Again this might result in a lot of broken
>> code.
>>
>
> I share your worries (meanwhile :-
--On 13. Januar 2006 13:25:19 +0100 Martijn Faassen <[EMAIL PROTECTED]>
wrote:
Andreas Jung wrote:
Thoughts?
All these changes seem to be the right thing. This will make unicode life
in Zope a lot easier.
I worry about backward compatibility though.
Some code (such as PlacelessTranslati
Andreas Jung wrote:
--On 5. Januar 2006 12:47:20 +0100 Andreas Jung <[EMAIL PROTECTED]>
wrote:
As you might know I worked on the integration of the Zope 3 ZPT
implementation for Zope 2.10. Before commiting the changes to the trunk I
would like discuss my approach for Zope 2.10
I forgot t
Andreas Jung wrote:
Thoughts?
All these changes seem to be the right thing. This will make unicode
life in Zope a lot easier.
I worry about backward compatibility though.
Some code (such as PlacelessTranslationService) is doing wild things
like monkeypatching the ZPT engine so that incomin
Andreas Jung wrote at 2006-1-6 10:13 +0100:
> ...
>A site encoding as default makes sense however there are situations when
>the encoding of a string from is different. E.g. when you deal with
>XMLHTTPRequest the browser expects an utf8 fragment which might conflict
>with an iso-8859-15 site-enc
--On 6. Januar 2006 19:55:56 +0900 TAHARA Yusei <[EMAIL PROTECTED]>
wrote:
I've tried to the branch and I found a typo in zope.conf.
I think default-zpublisher-encoding is a correct directive name.
This is already fixed.
By the way, I have a request related to this changes.
If the root
Hello.
> - the ZMI screens for ZPTs use a _fixed_ UTF-8 encoding (is this also
> fine
> for asian users?)
This is fine for me, as one of asian user.
> - The ZPublisher will convert a 'unicode' ZPT using
> default_zpublisher_encoding (zope.conf) to a byte stream. The current
> en
--On 5. Januar 2006 21:12:08 +0100 Dieter Maurer <[EMAIL PROTECTED]> >>
- allowing only unicode textual content when calling macros, PyScript
etc.
definitely not.
I know that this is a hard requirement but it is an implicit requirement in
Zope 3.
- converting non-unicode to unicode in
Andreas Jung wrote at 2006-1-5 13:39 +0100:
> ...
>I forgot to mention a major point: compatibility.
>
>When a ZPT is internally stored a unicode string then content returned by
>methods called through the ZPT will be implicitly converted to unicode.
>This will definitely raise UnicodeDecodeError
--On 5. Januar 2006 12:47:20 +0100 Andreas Jung <[EMAIL PROTECTED]>
wrote:
As you might know I worked on the integration of the Zope 3 ZPT
implementation for Zope 2.10. Before commiting the changes to the trunk I
would like discuss my approach for Zope 2.10
I forgot to mention a major poin
As you might know I worked on the integration of the Zope 3 ZPT
implementation for Zope 2.10. Before commiting the changes to the trunk I
would like discuss my approach for Zope 2.10
- the ZopePageTemplate and PageTemplateFile classes will be replaced
with wrapper classes around correspondi
15 matches
Mail list logo
