View Single Post
Old 05-29-2024, 05:38 PM   #28
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,691
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by KevinH View Post
Okay, I just pushed a fix for this to master.

The following *replacement* escapes will now be recognized:

\x{hh}
\x{hhhh}
\x{hhhhhh}

where h is any hex character (0-9, a-f, A-F).

Note 1: the 6 hex character version is there to support the extended plane above the BMP allowing the first two hex chars to be less than or equal to "10" to indicate the plane. This may result in QChar pairs as needed to properly encode the entire value.

Note 2: using < 2, 3, 5, >6 hex chars will result in that escape code being ignored and treated just like any other string of characters so remember to prepend a "0" when needed to fit one of the required formats.
Working great on Windows and Linux!
DiapDealer is online now   Reply With Quote