This would explain the similar failure that I reported and didn't get around to digging into. Excellent.
andrew
Simon Riggs wrote:
I have access to a system with locale of UTF-8. cvstip would no longer initdb on this system, as a result of recent renaming of UTF-8 to UTF8.
i.e. [EMAIL PROTECTED] ~]$ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
OS is Fedore Core 3.
Attached patch adds UTF-8 as a synonym for UTF8, so initdb works again without needing to specify an encoding, just like it used to.
Whatever we call UTF*8, there will always be somebody who says
different.
Best regards, Simon Riggs
------------------------------------------------------------------------
Index: initdb.c
===================================================================
RCS file: /projects/cvsroot/pgsql/src/bin/initdb/initdb.c,v
retrieving revision 1.79
diff -d -c -r1.79 initdb.c
*** initdb.c 14 Mar 2005 18:31:23 -0000 1.79
--- initdb.c 11 Apr 2005 23:12:25 -0000
***************
*** 721,726 ****
--- 721,727 ----
{PG_JOHAB, "???"},
#endif
+ {PG_UTF8, "UTF-8"},
{PG_UTF8, "UTF8"},
{PG_UTF8, "utf8"},
------------------------------------------------------------------------
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
