Bug 520589 - html log has charset=None
Summary: html log has charset=None
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: supybot-meetbot
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-01 10:05 UTC by Jens Petersen
Modified: 2009-09-24 18:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-24 18:14:35 UTC


Attachments (Terms of Use)

Description Jens Petersen 2009-09-01 10:05:10 UTC
Description of problem:
I peeked a little around at meetbot and pygments
and got to the conclusion that meetbot is not setting
the default output encoding correctly for pygments
resulting in html with charset=None apparently.

Steps to Reproduce:
1. type/paste あ into an irc meeting
2. look at log.html
  
Actual results:
縺

Expected results:
あ

Additional info:
This was actually tested in #fedora-meeting:

http://meetbot.fedoraproject.org/fedora-meeting/2009-09-01/fedora-meeting.2009-09-01-05.00.log.html

Comment 1 Jens Petersen 2009-09-01 10:07:40 UTC
> meetbot is not setting
> the default output encoding correctly for pygments
> resulting in html with charset=None apparently.

Well actually correctly, it does:

meeting.py:98:    output_codec = 'utf-8'

But somehow it is not reaching the pygment html formatter?

Comment 2 Richard Darst 2009-09-01 18:05:16 UTC
(In reply to comment #0)
> Description of problem:
> I peeked a little around at meetbot and pygments
> and got to the conclusion that meetbot is not setting
> the default output encoding correctly for pygments
> resulting in html with charset=None apparently.

Thanks for reporting this.  I just fixed it.

I had fixed up charsets for the (no longer used) ReStructured Text writer and the pygments log writer at the same time, and got the options "outencoding" and "output_encoding" mixed up.

Anyway, it is fixed now, and will be in the next released version sometime soon now.

Comment 3 Kevin Fenzi 2009-09-24 18:14:35 UTC
This should be fixed in the 0.1.4 release thats in updates-testing. 

Feel free to reopen or file a new bug if you spot any further issues here.


Note You need to log in before you can comment on or make changes to this bug.