Paul Ramsey wrote:
Steve,
You're right and I'm wrong, I was confused by the UTF code numbers,
which differ from the actual byte encodings used for UTF8. Indeed, all
the multi-byte higher-order stuff is stuffed into 128-255 in the UTF8
encoding, so a straight byte-swap would work (for UTF8 and the various
one-byte latin code pages, that is).
I've just confirmed on the postgres-hackers list that it should be OK to
replace the '\r' characters:
Tom Lane wrote:
>
> It's safe, because you'll be dealing with prosrc inside the backend,
> therefore using a backend-legal encoding, and those don't have any
> ASCII aliasing problems (all bytes of an MB character must have high
> bit set).
So now it is just a Simple Matter of Programming :-)
Joe
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
