installed in non-standard locations.

Example: --with-libraries=/opt/gnu/lib:/usr/sup/lib.

--enable-recode

Enables single-byte character set recode support. See the

Administrator's Guide about this feature. Note that a more general

form of character set conversion is supported in the default

configuration; this feature is obsolete.

--enable-nls[=LANGUAGES]

Enables Native Language Support (NLS), that is, the ability to

--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)

--enable-FEATURE[=ARG] include FEATURE [ARG=yes]

--enable-integer-datetimes enable 64-bit integer date/time support

--enable-recode enable single-byte recode support

--enable-nls[=LANGUAGES] enable Native Language Support

--disable-shared do not build shared libraries

--disable-rpath do not embed shared library search path in executables

echo "${ECHO_T}$enable_integer_datetimes" >&6

# Character set recode (--enable-recode)

#

echo "$as_me:$LINENO: checking whether to build with recode support" >&5

echo $ECHO_N "checking whether to build with recode support... $ECHO_C" >&6

# Check whether --enable-recode or --disable-recode was given.

if test "${enable_recode+set}" = set; then

enableval="$enable_recode"

case $enableval in

yes)

cat >>confdefs.h <<\_ACEOF

#define CYR_RECODE 1

_ACEOF

;;

no)

:

;;

*)

{ { echo "$as_me:$LINENO: error: no argument expected for --enable-recode option" >&5

echo "$as_me: error: no argument expected for --enable-recode option" >&2;}

{ (exit 1); exit 1; }; }

;;

esac

else

enable_recode=no

fi;

echo "$as_me:$LINENO: result: $enable_recode" >&5

echo "${ECHO_T}$enable_recode" >&6

#

# NLS

#

dnl Process this file with autoconf to produce a configure script.

dnl $Header: /cvsroot/pgsql/configure.in,v 1.273 2003/08/03 20:23:14 tgl Exp $

dnl $Header: /cvsroot/pgsql/configure.in,v 1.274 2003/08/04 04:03:03 tgl Exp $

dnl

dnl Developers, please strive to achieve this order:

dnl

AC_MSG_RESULT([$enable_integer_datetimes])

# Character set recode (--enable-recode)

#

AC_MSG_CHECKING([whether to build with recode support])

PGAC_ARG_BOOL(enable, recode, no, [ --enable-recode enable single-byte recode support],

[AC_DEFINE([CYR_RECODE], 1,

[Define to 1 if you want single-byte recode support. (--enable-recode)])])

AC_MSG_RESULT([$enable_recode])

#

# NLS

#

<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.36 2003/05/15 15:50:18 petere Exp $ -->

<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.37 2003/08/04 04:03:03 tgl Exp $ -->

<chapter id="charset">

<title>Localization</>

This chapter describes the available localization features from the

point of view of the administrator.

<productname>PostgreSQL</productname> supports localization with

three approaches:

two approaches:

<itemizedlist>

<listitem>

Providing a number of different character sets defined in the

<productname>PostgreSQL</productname> server, including

multiple-byte character sets, to support storing text in all

kinds of languages, and providing character setrecoding between

kinds of languages, and providing character settranslation between

client and server.

</para>

</listitem>

<listitem>

<para>

Single-byte character recoding provides a more light-weight

solution for users of multiple, yet single-byte character sets.

</para>

</listitem>

</itemizedlist>

</para>

</sect1>

<sect1 id="recode">

<title>Single-Byte Character Set Recoding</>

<para>

You can set up this feature with the <option>--enable-recode</> option

to <filename>configure</>. This option was formerly described as

<quote>Cyrillic recode support</> which doesn't express all its

power. It can be used for <emphasis>any</> single-byte character

set recoding.

</para>

<para>

This method uses a file <filename>charset.conf</> file located in

the data directory for configuration. It's a typical

configuration text file where spaces and newlines separate fields

and records and <literal>#</> starts a comment. Three key words with the

following syntax are recognized here:

<synopsis>

BaseCharset <replaceable>server_charset</>

RecodeTable <replaceable>from_charset</> <replaceable>to_charset</> <replaceable>file_name</>

HostCharset <replaceable>host_spec</> <replaceable>host_charset</>

</synopsis>

</para>

<para>

<token>BaseCharset</> defines the character set of the database server.

All character set names are only used for mapping inside of

<filename>charset.conf</> so you can freely use typing-friendly

names.

</para>

<para>

<token>RecodeTable</> records specify conversion tables between

server and client. The file name is relative to the

data directory. The table file format is very

simple. There are no key words, and character mappings are represented by a

pair of decimal or hexadecimal (prefixed by <literal>0x</>) values on single

lines:

<synopsis>

<replaceable>char_value</> <replaceable>converted_char_value</>

</synopsis>

In the <filename>src/data/</> directory in the source distribution you can find an

example <filename>charset.conf</> and a few recoding tables.

</para>

<para>

<token>HostCharset</> records define the client character set by IP

address. You can use a single IP address, an IP mask range starting

from the given address or an IP interval (e.g., <literal>127.0.0.1</>,

<literal>192.168.1.100/24</>, <literal>192.168.1.20-192.168.1.40</>).

</para>

<para>

The <filename>charset.conf</> file is always processed to the

end, so you can easily specify exceptions from preceding rules.

</para>

<para>

As this solution is based on the client's IP address there are

obviously some restrictions as well. You cannot use different

character sets on the same host at the same time. It is also

inconvenient when you boot your client hosts into multiple

operating systems. Nevertheless, when these restrictions are not

limiting and you do not need multibyte characters then it is a

simple and effective solution.

</para>

</sect1>

</chapter>

<!-- Keep this comment at the end of the file

<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.137 2003/08/0103:10:04 momjian Exp $ -->

<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.138 2003/08/04 04:03:03 tgl Exp $ -->

<chapter id="installation">

<title><![%standalone-include[<productname>PostgreSQL</>]]>

</listitem>

</varlistentry>

<varlistentry>

<term><option>--enable-recode</option></term>

<listitem>

<para>

Enables single-byte character set recode support. See

<![%standalone-include[the documentation]]> <![%standalone-ignore[<xref

linkend="recode">]]> about this feature. Note that a more

general form of character set conversion is supported in the

default configuration; this feature is obsolete.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><option>--enable-nls<optional>=<replaceable>LANGUAGES</replaceable></optional></option></term>

<listitem>

on_shmem_exit(DumpFreeSpaceMap,0);

}

SetCharSet();

if (!IsUnderPostmaster)

{

puts("\nPOSTGRES backend interactive interface ");

puts("$Revision: 1.355 $ $Date: 2003/08/0402:40:04 $\n");

puts("$Revision: 1.356 $ $Date: 2003/08/0404:03:06 $\n");

}

for (;i<maxlen;i++)

*r++=' ';

convertstr(VARDATA(result),len,0);

PG_RETURN_BPCHAR_P(result);

}

memcpy(result,VARDATA(s),len);

result[len]='\0';

convertstr(result,len,1);

PG_RETURN_CSTRING(result);

}

VARATT_SIZEP(result)=len+VARHDRSZ;

memcpy(VARDATA(result),s,len);

convertstr(VARDATA(result),len,0);

PG_RETURN_VARCHAR_P(result);

}

memcpy(result,VARDATA(s),len);

result[len]='\0';

convertstr(result,len,1);

PG_RETURN_CSTRING(result);

}

memcpy(VARDATA(result),inputText,len);

convertstr(VARDATA(result),len,0);

PG_RETURN_TEXT_P(result);

}

memcpy(result,VARDATA(t),len);

result[len]='\0';

convertstr(result,len,1);

PG_RETURN_CSTRING(result);

}