From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jorge Silva <jorge.silva93@gmail.com>
cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: xPath in a database with LATIN1 encoding
In-reply-to: <E8EDD295-7797-4EC7-9F60-96A9554CDEE6@gmail.com>
References: <E8EDD295-7797-4EC7-9F60-96A9554CDEE6@gmail.com>
Comments: In-reply-to Jorge Silva <jorge.silva93@gmail.com>
	message dated "Sat, 24 Apr 2021 12:20:24 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1707306.1619282961.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 24 Apr 2021 12:49:21 -0400
Message-ID: <1707307.1619282961@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1707307.1619282961%40sss.pgh.pa.us>
Precedence: bulk

Jorge Silva <jorge.silva93@gmail.com> writes:
> The characters that it is not recognizing are both =E2=80=9C=C3=A7=E2=80=
=9D and =E2=80=9C=C3=A3=E2=80=9D because I think they are encoded differen=
tly in latin1 and utf-8. Is it possible to somehow use the xPath function =
with special characters in the XML and in a database which is not encoded =
with utf-8? =


I don't have a lot of expertise in this area, but I think you need
an explicit encoding indicator in the xml header, a la

    <?xml encoding=3D"latin1"?> ...

On the whole, the xml type is definitely easier to use with database
encoding set to utf8.  I think you'll be paying for encoding conversion
every time we interact with libxml, for instance.

			regards, tom lane