On 11/16/16 1:38 AM, Magnus Hagander wrote: > AFAICT this is because the output is now UTF8 and it used to be LATIN1. > The current output actually has it in the html tags that it's utf8,but > since the old one had no tags specifying it's encoding we hardcoded it > to LATIN1.
The old output has this: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> This has always been the case, AFAICT. Btw., shouldn't the output web site pages have encoding declarations? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers