Re: proposal: unescape_text function - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: unescape_text function
Date
Msg-id CAFj8pRB6pp+fu5M6fSZeG9QH11M=KFUnYVBZnsRwVLoma30ffw@mail.gmail.com
Whole thread Raw
In response to Re: proposal: unescape_text function  (Chapman Flack <chap@anastigmatix.net>)
List pgsql-hackers


út 1. 12. 2020 v 20:20 odesílatel Chapman Flack <chap@anastigmatix.net> napsal:
>> po 30. 11. 2020 v 22:15 odesílatel Pavel Stehule <pavel.stehule@gmail.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

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: PG vs LLVM 12 on seawasp, next round
Next
From: Dmitry Dolgov
Date:
Subject: Re: Index Skip Scan (new UniqueKeys)