<>
That was the first thing we tried. Sorry I didn't mention it.
The next step was getting a string, turning it into bytes, and
translating the bytes. The third step was getting bytes. Nothing worked
in our Java GUI, the console, or the web page returned.
Maybe it was just something we
J. Michael Crawford wrote:
Encoding translations that didn't work:
a) Getting encoded bytes from the result set. We tried the following
block five times, once for each different encoding we were trying to
test with the database:
b) Getting a string, turning it bytes, and then translating. Sam
<>
Well then, perhaps we shouldn't share the procedure with other folks. I
apologize if I'm introducing some misinformation.
However, this has been the only way to get our system to work on more
than one JVM. People from this group provided many suggestions, people
from other groups did t
On Mon, 8 Nov 2004, J. Michael Crawford wrote:
>
>Even in Java, where you can do all sorts of character-encoding
> translation, it can be impossible to translate data retrieved from Postgres
> if it's in the wrong encoding. We've tried changing the JVM encoding,
> altering the jdbc drive
