88 * formatting/conversion routines that are needed to produce valid messages.
99 * Note in particular the distinction between "raw data" and "text"; raw data
1010 * is message protocol characters and binary values that are not subject to
11- *MULTIBYTE conversion, while text is converted byMULTIBYTE rules.
11+ *character set conversion, while text is converted bycharacter encoding rules.
1212 *
1313 * Incoming messages are read directly off the wire, as it were, but there
1414 * are still data-conversion tasks to be performed.
1515 *
1616 * Portions Copyright (c) 1996-2002, PostgreSQL Global Development Group
1717 * Portions Copyright (c) 1994, Regents of the University of California
1818 *
19- *$Id: pqformat.c,v 1.23 2002/08/29 03:22:01 tgl Exp $
19+ *$Id: pqformat.c,v 1.24 2002/09/03 21:45:42 petere Exp $
2020 *
2121 *-------------------------------------------------------------------------
2222 */
2727 *pq_sendbyte- append a raw byte to a StringInfo buffer
2828 *pq_sendint- append a binary integer to a StringInfo buffer
2929 *pq_sendbytes- append raw data to a StringInfo buffer
30- *pq_sendcountedtext - append a text string (withMULTIBYTE conversion)
31- *pq_sendstring- append a null-terminated text string (withMULTIBYTE )
30+ *pq_sendcountedtext - append a text string (withcharacter set conversion)
31+ *pq_sendstring- append a null-terminated text string (withconversion )
3232 *pq_endmessage- send the completed message to the frontend
3333 * Note: it is also possible to append data to the StringInfo buffer using
3434 * the regular StringInfo routines, but this is discouraged since required
35- *MULTIBYTE conversion may not occur.
35+ *character set conversion may not occur.
3636 *
3737 * Special-case message output:
38- *pq_puttextmessage - generate aMULTIBYTE -converted message in one step
38+ *pq_puttextmessage - generate acharacter set -converted message in one step
3939 *
4040 * Message input:
4141 *pq_getint- get an integer from connection
4242 *pq_getstr- get a null terminated string from connection
43- * pq_getstr performsMULTIBYTE conversion on the collected string.
43+ * pq_getstr performscharacter set conversion on the collected string.
4444 * Use the raw pqcomm.c routines pq_getstring or pq_getbytes
4545 * to fetch data without conversion.
4646 */
@@ -79,7 +79,7 @@ pq_sendbytes(StringInfo buf, const char *data, int datalen)
7979}
8080
8181/* --------------------------------
82- *pq_sendcountedtext - append a text string (withMULTIBYTE conversion)
82+ *pq_sendcountedtext - append a text string (withcharacter set conversion)
8383 *
8484 * The data sent to the frontend by this routine is a 4-byte count field
8585 * (the count includes itself, by convention) followed by the string.
@@ -106,7 +106,7 @@ pq_sendcountedtext(StringInfo buf, const char *str, int slen)
106106}
107107
108108/* --------------------------------
109- *pq_sendstring- append a null-terminated text string (withMULTIBYTE )
109+ *pq_sendstring- append a null-terminated text string (withconversion )
110110 *
111111 * NB: passed text string must be null-terminated, and so is the data
112112 * sent to the frontend.
@@ -178,10 +178,10 @@ pq_endmessage(StringInfo buf)
178178}
179179
180180/* --------------------------------
181- *pq_puttextmessage - generate aMULTIBYTE -converted message in one step
181+ *pq_puttextmessage - generate acharacter set -converted message in one step
182182 *
183183 *This is the same as the pqcomm.c routine pq_putmessage, except that
184- *the message body is a null-terminated string to whichMULTIBYTE
184+ *the message body is a null-terminated string to whichencoding
185185 *conversion applies.
186186 *
187187 *returns 0 if OK, EOF if trouble