Strange 'find' case?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




I was decoding and encoding a flac/cue file and noticed that
if there are embedded encoded characters in the filenames as
they are specified from the Cue file, Nautilus adds the
tag: (invalid encoding) to the end of the filename.

But, if one does a simple find command like:

find . -type f

All of the files are found, however, with one difference,
the tag: (invalid encoding) is not displayed, so I assume
that this is a Nautilus 'feature'.  With that assumption,
in mind, one might think that the following find command
would work:

find . -type f -iname '*.flac'

But no, it fails to find *any* file that has the embedded encoded
characters!

Strangely, if the "offending" encoded characters AND (invalid encoding)
is removed (via Nautilus), only then, would the find (-iname) command
locate the "cleaned up" files.

So, my question is, how do I get around this issue - to either write a script to convert these files to a `sane' encoded characters or change something like
the Language environment that the OS can handle any encoded file names?

Thanks!
Dan

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux