Hi Tom,
Thanks for looking into this issue. Would this help?
> psql -l
List of databases
Name | Owner | Encoding | Collate |
Ctype | Access privileges
------------------------+---------------+----------+-------------+---------=
----+---------------------------------
grand-central | michaelgradek | UTF8 | en_US.UTF-8 |
en_US.UTF-8 |
Here's a case showing the transformation failing, and another succeeding
> psql grand-central
psql (9.4.1, server 9.3.5)
Type "help" for help.
grand-central=3D# select '=C8=9B' as input, unaccent('=C8=9B') as observed,=
't' as
expected;
input | observed | expected
-------+----------+----------
=C8=9B | =C8=9B | t
(1 row)
grand-central=3D# select '=C3=A9' as input, unaccent('=C3=A9') as observed,=
'e' as
expected;
input | observed | expected
-------+----------+----------
=C3=A9 | e | e
(1 row)
On Sun, Jun 14, 2015 at 1:59 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> mike@busbud.com writes:
> > Sorry, I couldn't install the most recent minor release, but I did try
> this
> > on several different versions. I used Heroku to try a 9.4.3 build, and
> got
> > the same results
>
> > select '=C8=9B' as input, unaccent('=C8=9B') as observed, 't' as expect=
ed;
> > input | observed | expected
> > -------+----------+----------
> > =C8=9B | =C8=9B | t
> > (1 row)
>
> Hm, I do see
>
> =C5=A3 t
>
> in unaccent.rules, so the transformation ought to happen. I suspect
> an encoding issue, eg your terminal window is not transmitting characters
> in the encoding Postgres thinks you're using. You did not provide any
> info about server encoding, client encoding, or client LC_xxx environment=
,
> so it's hard to debug from here.
>
> regards, tom lane
>
--=20
Cheers,
Mike
--=20
Mike Gradek
Co-founder and CTO, Busbud
Busbud.com <http://busbud.com/> | mike@busbud.com
*We're hiring!: Jobs at Busbud <http://www.busbud.com/en/about/jobs>*