Looking through the routes code, I have to say I am not impressed. I shall look into getting rid of it when I do my content server refactor. Mapping URLs to functions should not be that hard
It may be that updating to routes 2.0 will fix the unicode issue since it purports to support python 3, but given that it may break other things, it's not something I want to do.