[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #35910] Incorrect regex matching of multi-byte
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #35910] Incorrect regex matching of multi-byte UTF-8 characters |
Date: |
Fri, 2 Aug 2019 15:47:09 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.87 Safari/537.36 |
Follow-up Comment #20, bug #35910 (project octave):
I pushed a change on default to initialize the locale / character encoding
always when the interpreter starts, added the setlocale gnulib module, and
deleted some extraneous checks for the setlocale function from configure
https://hg.savannah.gnu.org/hgweb/octave/rev/463fc0cfed90
This fixes the main regression I saw with this change.
The remaining question is do we want to report an error if a user runs Octave
in a non-UTF-8 locale with a regular expression that contains a UTF-8
character? Probably yes, but we didn't in earlier versions of Octave. It might
be worth mentioning in NEWS that regular expressions now support multi-byte
character matching and that all patterns are now implicitly UTF-8.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?35910>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #35910] Incorrect regex matching of multi-byte UTF-8 characters,
Mike Miller <=