You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @renggli! First of all, thanks for this great piece of software. I was hoping to use petitparser to implement a function to validate I-Regex expressions in my json_path implementation. The I-Regex standard requires full unicode compatibility, including the character from the higher planes. Here's the corresponding part of the ABNF:
I have tried to quickly "hack" your code by replacing .codeUnit calls with .runes, but it seems to go deeper than I thought and also might affect performance, since converting to runes will make access by index impossible. So my question is: do you plan to add support for higher planes?
The text was updated successfully, but these errors were encountered:
Hi @renggli! First of all, thanks for this great piece of software. I was hoping to use
petitparser
to implement a function to validate I-Regex expressions in my json_path implementation. The I-Regex standard requires full unicode compatibility, including the character from the higher planes. Here's the corresponding part of the ABNF:Unfortunately, it seems that petitparser does not support surrogate UTF-16 pairs. Here's an example code to reproduce the issue:
I have tried to quickly "hack" your code by replacing
.codeUnit
calls with.runes
, but it seems to go deeper than I thought and also might affect performance, since converting to runes will make access by index impossible. So my question is: do you plan to add support for higher planes?The text was updated successfully, but these errors were encountered: