[Octave-bug-tracker] [bug #57107] regexp functions fail on ISO-8859-1 input

[Markus Mützel]

Follow-up Comment #44, bug #57107 (project octave):


> 1. instead of throwing an error, can regexp give an warning yet still
proceed with the old behavior?

That's the behavior of PCRE(2). Octave only implemented a manual check because
PCRE's own check was slow (at least at some point).

> 2. if 1 is not possible, can regexp test if the matching pattern contains no
multi-byte characters and if yes, ignore utf-8 string restriction of the
input?

That would break other use cases. See comment #43.

> 3. add an octave-specific option to regexp/regexpi/regexprep to allow manual
encoding handling (and ignore utf-8 input restriction)?

We've had bad experiences with syntax extensions in the past. I'll leave that
decision to others.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57107>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/