Re: The plan for UTF-8

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> We have libraries further down the path which bail out when they are
> confronted with UTF-8 strings.  These libraries are not UTF-8 ready
> (they assume that length($string) returns the number of bytes that
> would be written by print etc.), and this is something we'd need to
> fix anyway.

Okay. If you think of any smoother way to do things, or have other 
ideas to make things easier on you other than setting pg_enable_utf=0 
in the connection string, let us know. None of this is carved in 
stone yet. :)

- -- 
Greg Sabino Mullane greg-738XdyZ4GzZWk0Htik3J/[email protected]
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201102101602
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAk1UUn4ACgkQvJuQZxSWSshCLACgwjJIJJRwDgbAvm9Ed7F+8s2l
fKoAoMOq8GgPX9bWlHg9KHkHxCIaU9b6
=G6WD
-----END PGP SIGNATURE-----