mod_xslt sets the Content-Encoding http header to the charset in use. The charset should be encoded in the Content-Type (which it does correctly). The Content-Encoding should only be used for wrappers, such as compression methods, not charsets. This both Safari and Lynx don't understand this. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 14909 [details, diff] removes the code that adds the Content-Encoding header.
Created attachment 14916 [details, diff] This one is actualy tested :-)
Sorry, first patch was wrong. Took me some time to get the second patch correct.
why dont you send your patches to the upsteam author instead. ok?
I have, I always send these patches to both ebuild maintainer and the developer.
hmm you sent two patches... you attached each more than once i think... would you perhaps care to create a single patch, with all of your latest fixes? I just want to be sure you're settled on your fixes and make it easier to process. Any news from the author?
Patch has been added.