New answers tagged unicode
2
I wouldn't expect English strings to necessarily be positioned before all other strings after sorting. I'd rather expect that strings are first sorted by language order ("david" before "mario") and then either by Unicode code point number ("programmer's sort", corresponding to LC_ALL=C) or simply left in place (since the other strings are not English).
From ...
0
we wanted to convert the non-ascii open double quote and close double quote to regular double quotes ("). Also the non-ascii single quote to regular single quote (').
to see them in the file (ubuntu bash shell):
$ grep -P "\x92" infile.txt (single)
$ grep -P "\x93" infile.txt (open double)
$ grep -P "\x94" infile.txt (close double)
translate them:
$ ...
2
This is weird. (And this "answer" started as a comment ;), became a bit long for it.)
Looking at the strace it looks like there are no hidden characters or the like, else I suspect you would have seen it in e.g. (which should have resulted in -1 ENOENT and not 0 if everything was OK):
stat("akorg", {st_mode=S_IFDIR|0755, st_size=21, ...}) = 0
as you do ...
5
As you're using zsh, I recommend tab completion or shell globbing (always echo/ls before removing). If those doesn't work, you have a few options:
Check your filename through a hex dump and use $'...' to input it
% touch akorgā½
% ls | grep akorg | hexdump -C
00000000 61 6b 6f 72 67 e2 9c bd 0a |akorg....|
00000009
% ls ...
1
I'm guessing that you don't have an invisible directory, but rather that stat misprints the unicode characters so that the file name looks like akorg when on-screen.
Two possible solutions:
Use a shell with tab completion (zsh or bash). At the prompt do: rm -rf akorg<tab>. Zsh at least will complete the file name, escaping shell-special characters ...
Top 50 recent answers are included
