| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | ppkrauss(at)gmail(dot)com |
| Subject: | Add NOTICE about non-NFC-characters and clues for solution |
| Date: | 2018-11-16 10:54:25 |
| Message-ID: | 154236566566.1325.15566173904955824857@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/unaccent.html
Description:
Seems a bug, because the `select unaccent('Iglésias')` result in accented
"iglésias" again... It is correct because length('Iglésias') is 9 instead
8.
The problem is not rare as you can check by pageviews of
https://stackoverflow.com/questions/24863716
The solution is to feed database with good UTF8 (NFC characteres).
**SUGGESTION**: add a notice for reders, about the aparent bug with non-NFC
input, showing examples and clues about solutions.
REF: https://en.wikipedia.org/wiki/Unicode_equivalence#Example
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-11-19 02:43:36 | Re: typo in parallel safety doc |
| Previous Message | Jonathan S. Katz | 2018-11-14 14:39:49 | Re: Images in the official documentation |