Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#356 closed defect (fixed)

utf-8 problem with BlogShow Macro

Reported by: gernot@… Owned by: pacopablo
Priority: normal Component: TracBlogPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.9


I get an trac error "'ascii' codec can't encode character u'\xe4' in position 10172: ordinal not in range(128)" when I write a blog entry with a german umlaut (äöü). The error occurs only in the Wiki Macro BlogShow, not on the blog page

Attachments (0)

Change History (6)

comment:1 Changed 9 years ago by pacopablo

  • Status changed from new to assigned

I can't duplicate this error. I've tried with 0.9.5 and with trunk. Can you please try the latest version of the blog plugin from trunk?

comment:2 Changed 9 years ago by gernot@…

By the way, it's a great plugin ! I'm running trac 0.9.5, TracBlogPlugin 0.10 and python 2.3.3 The funny thing is, when I view the blog entry on the blog page, everything is fine. The error only occurs on my main wiki page which looks like this:


Willkommen auf der Verwaltung des Projekts verpasst

Geplante Meilensteine




comment:3 Changed 9 years ago by pacopablo

hehe, next time, you might want to put any wiki text that you paste in a code block:

wiki text here

As far as tracking down the issue, can you veryify that you are running the latest trunk version of TracBlogPlugin?

Specifically, make sure that line 166 of tracblogplugin/0.10/blog/ looks like:

        return unicode(req.hdf.render('blog.cs'), 'utf-8')

If there isn't that call to unicode() then make sure you update the plugin.

Will you also post the text in question (the text that causes the error) in a code block on this ticket? Thanks.

comment:4 Changed 9 years ago by gontanon@…

Same problem here, I'm running an up to date plugin. The blog entry shows up fine on its own, the problem happens when it goes through the BlogShow() macro. The entry contains just an ñ (spanish n-tilde character).

comment:5 Changed 9 years ago by pacopablo

Give [766] a try.

I think that should fix it. It is really an issue with the lack of unicode support in 0.9.x

If that fixes it for you, please close the ticket.

comment:6 Changed 9 years ago by gernot@…

  • Resolution set to fixed
  • Status changed from assigned to closed

Changeset 766 works for me, thank you very much for your help, pacopablo. I couldn't live without your plugin ;-)

Add Comment

Modify Ticket

as closed The owner will remain pacopablo.
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.