From: Marcelo . <wachaca@yahoo.com>
To: pgsql-sql@postgresql.org
Subject: Re: UTF8 Vs Latin9 and valid encoding.
Date: Wed, 30 Aug 2006 06:52:28 -0700 (PDT)
Message-ID: <20060830135228.16496.qmail@web53009.mail.yahoo.com> (raw)
In-Reply-To: <44F54B9C.4040200@logix-tt.com>
Hello,
Thanks for your reply.
When I execute
show client_encoding;
I get UNICODE.
However, up to know I was using pgAdmin III Query and
EMS... you gave me the idea to use psql, where I
noticed something interesting:
\encoding
UTF8
show client_encoding;
UTF8
So this seems to be OK..
However when I type áéíóúñ on screen I see ßØ«·±
Why would this be?
Thanks again
--- Markus Schaber <schabi@logix-tt.com> wrote:
> Hi, Marcelo,
>
> Marcelo . wrote:
>
> > I receive the error msg:
> > ERROR: invalid UTF-8 byte sequence detected near
> byte
> > 0xf1
> >
> > Isn't UTF-8 the same as UNICODE where it
> encapsulates
> > all other coding schemes including latin9?
>
> Yes, it is.
>
> But it seems that your client and the server
> disagree on the encoding
> they use.
>
> I think the problem is that your client (psql, I
> presume) uses latin9 to
> communicate with the server, but the server assumes
> the client uses utf8.
>
> in psql, you can use \encoding to show the encoding
> psql uses, and "show
> client_encoding;" to show the encoding the server
> thinks the client uses.
>
> Try one of:
>
> SET client_encoding TO LATIN9; -- Tell server:
> client uses latin9
>
> \encoding LATIN9; -- Set clients encoding
>
> You can also set UTF-8 here, the server will convert
> between the client
> and database encoding (but it needs to know).
>
> HTH,
> Markus
>
>
>
> --
> Markus Schaber | Logical Tracking&Tracing
> International AG
> Dipl. Inf. | Software Development GIS
>
> Fight against software patents in EU! www.ffii.org
> www.nosoftwarepatents.org
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please
> send an appropriate
> subscribe-nomail command to
> majordomo@postgresql.org so that your
> message can get through to the mailing list
> cleanly
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: wachaca@yahoo.com
Subject: Re: UTF8 Vs Latin9 and valid encoding.
In-Reply-To: <20060830135228.16496.qmail@web53009.mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox