From 69769a3a6e7c09270aba3094d3ff6df771adf977 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 28 Jun 2016 14:21:43 -0400
Subject: [PATCH] doc: in binary mode mention, say "encoding conversion"
Used to say "character set conversion"
Reported-by: Tatsuo Ishii
Discussion: 20160618.210417.343199294611427151.t-ishii@sraoss.co.jp
---
doc/src/sgml/datatype.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 11e246fa351..9643746ca4a 100644
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -4219,7 +4219,7 @@ SET xmloption TO { DOCUMENT | CONTENT };
<para>
When using binary mode to pass query parameters to the server
- and query results back to the client, no character set conversion
+ and query results back to the client, no encoding conversion
is performed, so the situation is different. In this case, an
encoding declaration in the XML data will be observed, and if it
is absent, the data will be assumed to be in UTF-8 (as required by
--
GitLab