From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, 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 20:16:05 |
Message-ID: | CAFj8pRB6pp+fu5M6fSZeG9QH11M=KFUnYVBZnsRwVLoma30ffw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
út 1. 12. 2020 v 20:20 odesílatel Chapman Flack <chap(at)anastigmatix(dot)net>
napsal:
> >> 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?
>
the detection of decimal or hexadecimal codes can be a hard problem -
string "12" is valid in both systems, but the numbers are different. So
there should be external specification as an argument.
Regards
Pavel
> Regards,
> -Chap
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Dolgov | 2020-12-01 20:21:19 | Re: Index Skip Scan (new UniqueKeys) |
Previous Message | Andres Freund | 2020-12-01 20:08:10 | Re: PG vs LLVM 12 on seawasp, next round |