Every time I release a version of wp-gopher I assume I'm done with it, since it's a trivial little bit of Python that does one thing and does it well barely adequately. Neverthless, I got annoyed with the lack of character set support in it, so I've quickly hacked up a rudimentary fix — you can now define the character set in the configuration file and wp-gopher will insert an appropriate <meta> Content-Type tag to enforce it within blog posts (supporting non-Latin-1 text in the index would require character set support within the Gopher protocol, which doesn't exist, as far as I know). The default is UTF-8, unsurprisingly.
To prove that it works, you can view this very blog post via Gopher (possibly even IPv6 Gopher, if you have IPv6 connectivity) and marvel at the following string of UTF-8 encoded Arabic, which Wikipedia claims is the Arabic name for Perth: بيرث.
A tarball is available: wp-gopher-0.2.1.tar.gz (SHA-1 sum: b9f9f1ced88464a1ff52cef5d088f2d046d7a20d), or you can git clone http://www.adamharvey.name/git/wp-gopher for the latest trunk.
Copyright © 2006-10 Adam Harvey. Original content is licensed under a Creative Commons Attribution 2.5 Licence.