when I set default_charset to utf-8 the error vanishes but I'm not sure how good a fix this is. I mean our Subversion repos should almost always contain utf-8 if I correctly understand the way Subversion works but I may also err here. we can only ensure UTF-8 for the commit messages and not the actual change set content IIRC.
as setting default_charset to utf-8 may not be desired for everyone I'm not sure what the correct fix is but installing python-chardet seems to handle the issue transparently without any need to make charset predictions. if I read it correctly default_charset is intended as a fallback charset definition to use if Trac is uncertain so manually configuring all trac.ini files might fix it for the time being with the uncertainty of hitting the problem again with different content in future change sets which are not utf-8. to reproduce you need a Trac which has actual revisions in the db and load that Trac right after restarting Apache as the error only shows up the first time you load that Trac instance and not at all if you load another empty Trac before. moreover the box has only en_US-UTF-8 configured, nothing else. [trac] #default_charset = iso-8859-15 default_charset = utf-8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
