Re: Initdb -E LATIN1 fails when no multibyte support compiled in (current CVS)

On Sun, 12 Aug 2001 12:50:57 +0200 (CEST), you wrote:
>1. ability to handle multi-byte characters sets in string mashing
>functions
>
>2. character set conversion between client and server
>
>These things are technically unrelated but the group of users that need
>this seems to have coincided. If you want to propose splitting this up it
>could be discussed.

I have no reason to.

>> If this is the intended behaviour, I think the documentation of
>> --enable-multibyte in the INSTALL file (and perhaps in other
>> places) should be fixed. And if at all possible, it should be
>> renamed too.
>
>I think the INSTALL file refers you to the Admin Guide for more
>information, where this is explained. Maybe that needs to be improved.

The INSTALL file says:
"--enable-multibyte
Allows the use of multibyte character encodings. This is
primarily for languages like Japanese, Korean, and Chinese. Read
the Administrator's Guide for details."

This is misguiding for users with singlebyte (e.g. European)
encodings. Even if the Admin Guide explains it better, I think
the explanation in the INSTALL file should be corrected.

Regards,
René Pijlman