On Thu, Aug 26, 2010 at 9:27 AM, C. Michael Pilato <cmpil...@collab.net> wrote:
> [And just wrap this up from the ViewVC side of things] > > As I saw this thread returning the old endorsement of tossing encoding > information into the svn:mime-type property, I went ahead and taught ViewVC > to look there for that information. So, Ivan, if you missed my commit to > ViewVC yesterday, the trunk and 1.1.x branch tip code will parse > svn:mime-type, extract the charset= bit, and pass it's value off to Pygments > when doing syntax highlighting for the markup and annotate views. Will this fix the problem? Isn't there still the problem that the page advertises its encoding to the browser as UTF-8? Does ViewVC convert from the encoding in the mime-type to UTF-8 before sending the content to the browser? Or is that what Pygments is doing for you? -- Thanks Mark Phippard http://markphip.blogspot.com/
