Re: Problems with writing EUC-JP/Unicode to console or file

What encoding did you use to put the character into the database? There
are some mapping problems still in postgres for some Japanese
characters. It depends on which version of Java you are using and where
the data is coming from etc. I'm attaching an email I wrote to hackers
about this before. Looks like the same problem. Anyway, nothing to do
with the driver itself.

Cheers,

Tom.

On Mon, 2003-06-23 at 18:55, Jean-Christian Imbeault wrote:
> Csaba Nagy wrote:
> > I suspect that your machine's default encoding and the encoding used by
> > your Java program doesn't match.
>
> [snip]
>
> >i.e. explicitly tell to your Java
> > writer code what encoding to use, and explicitly tell to the editor what
> > encoding to use when opening the file. Otherwise they'll use their
> > default encodings, which might not match.
>
> Very true. I'll look up how to specify the encoding when writing to
> file. I don't know that it is possible when writing to the console though.
>
> *But* I must point out that I am writing quite a bit of data, in
> japanese, to file and the console and *all* of it come out correctly
> *except* for that one character ...
>
> I *will* check into how to specify the encoding but I don't think that
> is the problem as everything but the one character comes out out right.
> And as I had said, if I hard-code the string to be printed it comes out
> right ... only when the string is retrieved from the database does it
> come out wrong ...
>
> Thanks,
>
> Jean-Christian Imbeault
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
--
Thomas O'Dowd - Got a keitai? Get Nooped!
tom(at)nooper(dot)com - http://nooper.com