|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #59314] [octave forge] (mapping) str2angle fails to parse string with UTF-8 degree (°) character |
Date: | Thu, 22 Oct 2020 03:16:40 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.80 Safari/537.36 Edg/86.0.622.48 |
Follow-up Comment #5, bug #59314 (project octave): I think I lost you somewhere. Are you debating whether this change is save for Octave prior to version 6? If you are: I believe it is. A problematic pattern would e.g. be "[D°]" because in previous Octave versions that would match any of the three bytes 0x44, 0xC2, and 0xB0 independently. That means it would also match the first byte of e.g. UTF-8 encoded "µ" (0xC2 0xB5). If I read the regular expression correctly, there are no non-ASCII characters in bracket expressions. My comment was just meant to warn about potential changes to that regular expression. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?59314> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |