Am Dienstag, 12. April 2005 01:24 schrieb Simon Riggs:
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.
Well, to redeem myself, the whole thing got screwed up by some mindless
editing during the great encoding
Am Dienstag, 12. April 2005 01:24 schrieb Simon Riggs:
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.
Fixed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
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
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]