| From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Asif Rehman <asifr(dot)rehman(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: unescape_text function |
| Date: | 2020-12-01 19:20:40 |
| Message-ID: | 5FC69788.30401@anastigmatix.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> po 30. 11. 2020 v 22:15 odesílatel Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
>> napsal:
>>> I checked this and it is "prefix backslash-u hex" used by Java,
>>> JavaScript or RTF -
>>> https://billposer.org/Software/ListOfRepresentations.html
If I look on that page, it appears that RTF is using a similar-looking
escape but in decimal rather than hex.
It would be important to define what is done with non-BMP characters?
Will there be another escape for a six- or eight-hexdigit format for
the codepoint, or will it be represented by two four-hexdigit escapes
for consecutive UTF-16 surrogates?
Regards,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2020-12-01 20:04:44 | Re: PG vs LLVM 12 on seawasp, next round |
| Previous Message | Alvaro Herrera | 2020-12-01 18:57:24 | Re: error_severity of brin work item |