| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | tas(dot)o(dot)s(at)hotmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15347: Unaccent for greek characters does not work |
| Date: | 2018-08-23 05:36:32 |
| Message-ID: | 20180823053632.GA21506@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Aug 23, 2018 at 05:22:21PM +1200, Thomas Munro wrote:
> There is a precedent already that it knows how to remove a diacritic
> from at least one Cyrillic character. I think there is no reason at
> all we shouldn't take a patch to support Greek or any other alphabet
> that a native speaker can advise us on.
+1. ec0a69e4 has added recently support for Vietnamese characters.
Once you get into it hacking this python code is not that difficult.
> I think the chances of squeaking a change into PostgreSQL 11 are slim,
> since it would require a special exception from the Release Management
> Team at this point. Failing that, it'd be for PostgreSQL 12. We
> don't usually back-patch unaccent.rules changes because they can
> affect in indexed data, and we don't want minor version upgrades to
> break stuff.
Getting that into v11 would be too late :(
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Kukushkin | 2018-08-23 08:01:08 | Re: BUG #15346: Replica fails to start after the crash |
| Previous Message | Thomas Munro | 2018-08-23 05:22:21 | Re: BUG #15347: Unaccent for greek characters does not work |