Comment 1 for bug 244715

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!