Comment 2 for bug 244715

I haven't used a development (checkout) of either Zope 2 or 3 for
years. I'm trying to wrap up this legacy project so I can get myself
back to the much happier land of Zope 3 :).

But I'd like to help and keep Zope 2 solid, so I'll try to supply some
tests, patches, or whatever is necessary. Are there up-to-date docs
about how to work with a development checkout, run tests, etc?

On Jul 2, 2008, at 2:24 PM, Philipp von Weitershausen wrote:

> I agree with your conclusion.
>
> The problem stems from Zope 2 using 8bit strings for object ids. So
> while it's certainly possible to use non-ASCII characters in path
> names, they'll always be stored in some encoding. I imagine the
> default encoding would be latin-1 and there would probably be a way to
> change it (frankly I don't know how, but I think Plone somehow manages
> to use UTF8 I think). Anyway, certainly the publisher must be using
> this implicit encoding when mapping unicode URLs to object paths, so
> there must be some way of figuring this out. Whatever it is, I think
> the TALES traversal machinery in Products.PageTemplates should use the
> same logic.
>
> Since I'm the one who ported Zope 2 to use the Zope 3 ZPT
> implementation, I feel responsible for making this legacy use case
> work again. However, it would help me a lot (and probably speed things
> up) if you could perhaps create some tests for this use case. There
> should be some tests that you can extend in Products.PageTemplates.
> Submitting a patch that just adds failing tests would be very helpful
> already.
>
> Thanks!
>
> --
> TALES string expressions cannot co-exist with dynamic path expressions
> https://bugs.launchpad.net/bugs/244715
> You received this bug notification because you are a direct subscriber
> of the bug.

Thanks,
Jeff Shell
<email address hidden>