From 25fb6ba11575515d754477492a5ff83ef0c126c4 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 1 Sep 2018 16:02:47 -0400 Subject: [PATCH] Doc: fix oversights in "Client/Server Character Set Conversions" table. This table claimed that JOHAB could be used as a server encoding, which was true originally but hasn't been true since 8.3. It also lacked entries for EUC_JIS_2004 and SHIFT_JIS_2004. JOHAB problem noted by Lars Kanis, the others by me. Discussion: https://postgr.es/m/c0f514a1-b7a9-b9ea-1c02-c34aead56c06@greiz-reinsdorf.de --- doc/src/sgml/charset.sgml | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index f8c7ac3b16..15d17c4988 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -1135,6 +1135,13 @@ $ psql -l UTF8 + + EUC_JIS_2004 + EUC_JIS_2004, + SHIFT_JIS_2004, + UTF8 + + EUC_KR EUC_KR, @@ -1190,8 +1197,7 @@ $ psql -l JOHAB - JOHAB, - UTF8 + not supported as a server encoding @@ -1297,6 +1303,11 @@ $ psql -l not supported as a server encoding + + SHIFT_JIS_2004 + not supported as a server encoding + + SQL_ASCII any (no conversion will be performed)