[Bug 3697] [Patch] 1.19.0 (git) Allow unicode output for "busybox ls"

bugzilla at busybox.net bugzilla at busybox.net
Thu May 12 10:02:11 UTC 2011


https://bugs.busybox.net/show_bug.cgi?id=3697

--- Comment #9 from Denys Vlasenko <vda.linux at googlemail.com>  ---
(In reply to comment #8)
> CONFIG_UNICODE_PRESERVE_BROKEN is made to skip filter, so why not doing the
> same if unicode is auto-disabled?

UNICODE_PRESERVE_BROKEN enables invalid Unicode sequences *on input*, not on
output. Read its help text:

config UNICODE_PRESERVE_BROKEN
        bool "Make it possible to enter sequences of chars which are not
Unicode"
        default n
        depends on UNICODE_SUPPORT
        help
          With this option on, invalid UTF-8 bytes are not substituted
          with the selected substitution character.
          For example, this means that entering 'l', 's', ' ', 0xff, [Enter]
          at shell prompt will list file named 0xff (single char name
          with char value 255), not file named '?'.

When we are in UNICODE_OFF mode, it means that we think that *output* devices
don't support Unicode. And since bbox doesn't support anything else than ASCII
and Unicode, and since bbox ls wants to produce non-garbled output, in
UNICODE_OFF mode it replaces any non-ASCII-printable bytes in filenames with
'?'.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the busybox-cvs mailing list