On 5/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I understand that using sessions to store the locale is not the
> smartest idea but had the impression (looking at _get_locale) that this
> is the way to do it.

To be clear, I wasn't saying that *you* were wrong in doing in that
way, I was just saying that we should probably come up with something
better.

> And given the way cherrypy maps urls to methods
> using something along the line of "/en/foo/bar" seemed pretty contrived
> to implement.

This could be done with a filter or, in TurboGears 1.1, will naturally
fit as a small bit of middleware.

> Anyway. Yes the ... represent the recursion; I omitted a lot of
> tracebacks to the same line 60 in i18n_filter). You can have the whole
> traceback if you want it.

The traceback is interesting, because it's going from a loop over
items in the stream into the filter, which is also looping over the
stream. Something seems wrong about that, but i've never written a Kid
filter before. I can't answer your question offhand, so I can make two
suggestions:

1) open a ticket in our trac (http://trac.turbogears.org) if you haven't already
2) send a message to the Kid mailing list (see
http://kid.lesscode.org) asking if anyone can see a problem with that
filter (just copy the whole i18n_filter code into your message, it's
not too long).

Hopefully, you'll get a response to that.

> Has any of the i18n code changed in the 1.0 branch?

That code should be the same between the trunk and the branch at this
point. I was just making the general suggestion that the trunk may not
be completely stable too much longer.

Kevin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears-trunk
-~----------~----~----~----~------~----~------~--~---

Reply via email to