Date: Sun, 6 Nov 2016 22:30:16 +0100 From: Stefan Bethke <stb@lassitu.de> To: Stefan Ehmann <shoesoft@gmx.net> Cc: Baptiste Daroussin <bapt@FreeBSD.org>, Greg Rivers <gcr+freebsd-stable@tharned.org>, freebsd-stable@freebsd.org Subject: Re: Uppercase RE matching problems in FreeBSD 11 Message-ID: <B25CDC46-8E6E-42E9-BFD0-CC3E0371516D@lassitu.de> In-Reply-To: <a3f401a7-9dc9-d567-bf21-139364702599@gmx.net> References: <alpine.BSF.2.20.1611051912260.2462@flake.tharned.org> <20161106110729.z2px7mzlhcwxvrvu@ivaldir.etoilebsd.net> <29451103-E8DB-4656-A5BB-AEB924A728D6@lassitu.de> <a3f401a7-9dc9-d567-bf21-139364702599@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 06.11.2016 um 22:14 schrieb Stefan Ehmann <shoesoft@gmx.net>: >=20 >> That is rather surprising. Is there a normative reference for the >> treatment of bracket expressions and character classes when using >> locales other than C and/or encodings like UTF-8? >=20 > I found an interesting article about this issue in gawk: > = https://www.gnu.org/software/gawk/manual/html_node/Ranges-and-Locales.html= OK, I give up. Back to jwz: "now you have two problems.=E2=80=9C Although with en_US.UTF-8 on other systems, I have not had that = experience. A quick check on stuff I have immediate access to: macOS 10.12: $ echo 'abcdABCD' | sed 's/[A-Z]/X/g=E2=80=99 abcdXXXX Ubuntu 14.04.5 $ echo 'abcdABCD' | sed 's/[A-Z]/X/g=E2=80=99 abcdXXXX FreeBSD 10-stable $ echo 'abcdABCD' | sed 's/[A-Z]/X/g' abcdXXXX Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B25CDC46-8E6E-42E9-BFD0-CC3E0371516D>