The interesting thing is that, if "echo *" is invoked, these non-Latin characters show up nicely. Module nls_utf8 is loaded. An attempt to build r23097 with CONFIG_BUSYBOX_CONFIG_UNICODE_SUPPORT=y didn't make any difference. Nothing special was done to BusyBox v1.11.3 to make "ls" display the filenames.

Change History (13)

An update: with r23757 and its busybox v1.17.3, the problem persists. Command "touch" creates a file with utf-8 encoded name, command "echo *" displays it, but command "ls" still shows a bunch of ??????.

Please find file 7993.diff in Attachments, which adds 700-make_unicode_printable.patch to package busybox to allow utf-8 encoded filenames to be displayed by command "ls".

By default, it's fine that busybox's unicode support is not activated (# CONFIG_BUSYBOX_CONFIG_UNICODE_SUPPORT is not set).
In this case, busybox should not turn all the "unprintable" characters, c >= 0x7f, to '?' because they are likely unicode that can be handled by libc unicode support.

pleas close it / fix it :( this is so basic.. it should make it into the AA final release.. it is not only LS that is affected, also people cannot copy folders etc.. using winscp etc.. it s so depressing! :( :)
merry xmas to all!

Add Comment

This ticket has been modified since you started editing. You should review the
other modifications which have been appended above,
and any conflicts shown in the preview below.
You can nevertheless proceed and submit your changes if you wish so.