Currently, if we encounter an unsupported charset, we silently fall back on
ISO-8859-1. We should validate unsupported charsets and present to the user as
an error on Submit instead.
Original issue reported on code.google.com by stephen....@gmail.com on 18 Nov 2012 at 5:07
Original issue reported on code.google.com by
stephen....@gmail.comon 18 Nov 2012 at 5:07