[openguides-tickets] [OpenGuides] #141: Optionally supply a charset to go with the content type

#141: Optionally supply a charset to go with the content type ------------------------+--------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: new Priority: normal | Milestone: Component: openguides | Version: svn Severity: normal | Keywords: ------------------------+--------------------------------------------------- We should allow guides to set a charset, which gets included with the content type.

Otherwise, a default (normally ISO-8859-1) is often added, which screws things up (eg your data isn't sent as UTF-8, and then postgres gets in a huff)