OK, the original bug was about non-ascii characters in a versioned resource, whereas this latest instance is about a non-ascii branch name.
> SetEnv "LANG fr_FR"
Strange quoting. Perhaps you have to remove those quotes, or only quote the value not the name.
Have you read and followed the section "File name encoding" of the current README?
Since http://bazaar.launchpad.net/~trac-bzr-team/trac-bzr/trunk/revision/116.1.3 the system info page of trac should provide sufficiently privileged users with information about the filesystem encoding as trac sees it. Can you provide that information as well? Unless that setting is fr_FR as well, there is a problem with your environment. The output from the "locale" binary might be helpful, too, to check that a locale called fr_FR is actually installed on your system.
I'm not sure whether mod_wsgi passes environment settings from those SetEnv directives to the python process. I found no box to set environment variables in the mod_wsgi daemob process itself. One hackish workaround might be replacing the python binary inside your virtual environment with a shell script that exports the required variables and then executes the real python binary:
OK, the original bug was about non-ascii characters in a versioned resource, whereas this latest instance is about a non-ascii branch name.
> SetEnv "LANG fr_FR"
Strange quoting. Perhaps you have to remove those quotes, or only quote the value not the name.
Have you read and followed the section "File name encoding" of the current README?
Since http:// bazaar. launchpad. net/~trac- bzr-team/ trac-bzr/ trunk/revision/ 116.1.3 the system info page of trac should provide sufficiently privileged users with information about the filesystem encoding as trac sees it. Can you provide that information as well? Unless that setting is fr_FR as well, there is a problem with your environment. The output from the "locale" binary might be helpful, too, to check that a locale called fr_FR is actually installed on your system.
I'm not sure whether mod_wsgi passes environment settings from those SetEnv directives to the python process. I found no box to set environment variables in the mod_wsgi daemob process itself. One hackish workaround might be replacing the python binary inside your virtual environment with a shell script that exports the required variables and then executes the real python binary:
#!/bin/sh
export LANG=fr_FR.utf8
exec path_to/real_python