|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #35910] Incorrect regex matching of multi-byte UTF-8 characters |
Date: | Mon, 29 Jul 2019 13:26:20 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36 |
Follow-up Comment #17, bug #35910 (project octave): The attached patch resolves the first issue for me. When the user environment variable settings declare a UTF-8 locale, the error message goes away in octave-cli. So the remaining question is, if the user intentionally does not declare a locale or sets the locale to a non-UTF-8 one, should we allow regexp to raise an error message now? That's still a regression, although a smaller one that can be worked around. (file #47275) _______________________________________________________ Additional Item Attachment: File name: octave-setlocale.patch Size:0 KB <https://savannah.gnu.org/file/octave-setlocale.patch?file_id=47275> _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?35910> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |