Thread
Commits
-
Doc: fix oversights in "Client/Server Character Set Conversions" table.
- d368c6c711d0 9.5.15 landed
- 9b0c58e6d43a 10.6 landed
- 4299c32316ad 12.0 landed
- 3099eec7468f 11.0 landed
- 25fb6ba11575 9.6.11 landed
- 0fef581d61fc 9.4.20 landed
- 0b5054369f30 9.3.25 landed
-
[PATCH] Fix docs to JOHAB encoding on server side
Lars Kanis <lars@greiz-reinsdorf.de> — 2018-09-01T16:17:16Z
The current documentation is inconsistent about the JOHAB character encoding on server side. While the first table says that it is not possible to use JOHAB on server side, it is still listed in table 23.2 as a server character set: https://www.postgresql.org/docs/devel/static/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED -- Kind Regards, Lars
-
Re: [PATCH] Fix docs to JOHAB encoding on server side
Tom Lane <tgl@sss.pgh.pa.us> — 2018-09-01T19:04:21Z
Lars Kanis <lars@greiz-reinsdorf.de> writes: > The current documentation is inconsistent about the JOHAB character encoding on server side. While the first table says that it is not possible to use JOHAB on server side, it is still listed in table 23.2 as a server character set: > https://www.postgresql.org/docs/devel/static/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED Hm, yeah. Probably this is because JOHAB was first installed as being a server-allowed encoding, and it was only later we realized that wasn't OK. This table must've been missed while changing it. Cross-checking the other entries, I notice SHIFT_JIS_2004 is also not listed in that table ... we've been a little sloppy there. Thanks for noticing! regards, tom lane