| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tasos Maschalidis <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-24 02:07:30 |
| Message-ID: | 25859.1535076450@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> On Fri, Aug 24, 2018 at 12:12 PM, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>> Perhaps it would be better to avoid non-ASCII characters in this script?
> You mean in the Python script? Why? At the top it has a PEP-263
> encoding declaration:
> # -*- coding: utf-8 -*-
What happens if someone tries to view this in a non-UTF8 encoding?
As a comparison point, we generally avoid using non-ASCII characters
directly in the SGML docs; we write out the appropriate SGML entity
instead. I think we should try to do the equivalent thing here ---
I assume python has some way to write "U+nnnn" or some such.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-08-24 03:32:28 | Re: BUG #15347: Unaccent for greek characters does not work |
| Previous Message | Thomas Munro | 2018-08-24 00:16:16 | Re: BUG #15347: Unaccent for greek characters does not work |