[Bug 11471] New: printf %q format not supported (yet)
bugzilla at busybox.net
bugzilla at busybox.net
Thu Nov 1 22:32:53 UTC 2018
https://bugs.busybox.net/show_bug.cgi?id=11471
Bug ID: 11471
Summary: printf %q format not supported (yet)
Product: Busybox
Version: 1.27.x
Hardware: All
OS: Linux
Status: NEW
Keywords: FIXME
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at busybox.net
Reporter: bbb30 at mailinater.com
CC: busybox-cvs at busybox.net
Target Milestone: ---
Created attachment 7851
--> https://bugs.busybox.net/attachment.cgi?id=7851&action=edit
Text file with sample of typographic open and close quotes around text.
I'm running busybox on android kitkat with a terminal emulator. Sometime files
I try to parse contain characters that cause grief. For example, a
typographical close quote (think 66-99 style quotes), when echo'd, printf'd %s
or a line with it displayed via set -x in sh or bash, causes multiple duplicate
lines of the same output, followed by a terminal hang. I'll attach a file with
a sample of that character. Other characters, like unescaped single quotes and
variants of that, also mess up scripts. I don't have an SDK so I can't compile
iconv and I don't have PERL etc. I saw no mention of this particular problem in
this bug database although there are some other unicode problem reports which
seem unrelated. Busybox printf reports %q as an invalid format. Without any
decent way to clean text strings, it can be extremely hard to write and test
scripts that encounter problematic characters. If I knew where to look for the
config file I would have attached it: I installed busybox with the Fdroid app.
But given the release notes, I expect this issue is cross-platform.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the busybox-cvs
mailing list