[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34316: sed misbehavior on BRE's
From: |
Assaf Gordon |
Subject: |
bug#34316: sed misbehavior on BRE's |
Date: |
Wed, 13 Feb 2019 16:15:08 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 |
tags 34316 notabug
close 34316
stop
Hello,
On 2019-02-11 12:45 a.m., Lange, Markus wrote:
# sed --version
sed (GNU sed) 4.7
...
Using LANG=C (LC_* unset) works as expected:
# LANG=C sed -n 's/^.*004K...\([0-
9xX]\{13\}\).*006V...\(.\{1,32\}\).*\(.020F.*\)021A.*$/\2 \1\3/p'
Fehlerpica.dat
138742c156c1445f8bdc3a7845548c00 9783507435339020F a19.04.03
18290030a02544e6a451538b0e44f9e2 9783507435377020F a19.04.03
4c7ff6d790b34470852434f5ee41200b 9783034312189020F a12.12.11
Using LANG=en_us.utf8 don't get results.
Thanks for confirming.
Since the file contains binary bytes, they would not match as valid
characters under UTF8 locale.
Using LC_ALL=C is indeed the solution.
As such, I'm closing this as "not a bug" but discussion can
continue by replying to this thread.
-assaf