I'm guessing you do have non-ASCII file names, they are utf8-encoded, and you probably don't have these lines near the top of the script:

binmode STDOUT, ":utf8";
binmode STDERR, ":utf8";
[download]

use Encode;
[download]

opendir( my $dir, "/usr/local/bin" ) or die "Can't read /usr/local/bin
+: $!\n";
while ( my $fname = decode( "utf8", readdir( $dir ))) {
    print $fname, "\n";
}
[download]

#!/usr/bin/perl

use strict;
use warnings;
use Encode;

binmode STDOUT, ":utf8";
binmode STDERR, ":utf8";

open(my $find,"|-:utf8","find /usr/local/bin -type f") or die "Can't r
+un find: $!\n";
while ( <$find> ) {
    print;
}
[download]

(Also, if all your file names are plain ASCII, the above scripts still work, because ASCII is a subset of utf8.)

Now, if some of your file names have non-ASCII characters, and use some character encoding other than utf8 (e.g. koi8-r or iso-8859-5 or cp1251 or whatever), you have to figure what that encoding is, and use it in place of "utf8" when you call decode() or open( ..., "|-...", "find ...").

If some of your file names have been corrupted (e.g. they were utf8-encoded but somehow got "renamed" with a bad byte sequence), you'll need to fix that.

(Update: I believe it is possible that a single directory can contain some file names that use one encoding, and other file names that use a different encoding. You might want to look closely at the man page for Encode, especially the part about catching errors ("FB_CROAK"), and you may also want to look at Encode::Guess.)

I will gladly do!

Yes, scripts live in Russian alphabet directory, that is in /usr/local/bin -- all in UTF8.

I did place the binmode lines in the script (the one that actually gives me the error and the one from which it is called) but i still get error message as above (regarding the script path (not readable characters).

I have tried open operator for find command. And can not understand how to get files it has found: how to put it into array. -- For

open(my $find, "|-:utf8", "/usr/bin/find -type f >/dev/null") or die "
+Can't run find: $!\n";
while( <$find> ){
  push @array, $_;
}
[download]

Does not put anything into array.

Thank you for your extended answer, graff.

"find /usr/local/bin -type f >/dev/null"

Of course this will produce no data because you are directing the output to /dev/null. What happens if you remove the output direction and instead just use find /usr/local/bin -type f ?

If you look at the code snippet I posted, you'll see that I did not redirect the output of "find" to /dev/null -- as pointed out in the other replies above, that's why your array remained empty.

One other point: now that you're pushing entries into an array, you'll probably want to use chomp -- e.g. like this:

open(my $find,"|-:utf8","find /usr/local/bin -type f") or die "find fa
+iled: $!\n";

while( <$find> ){
  chomp;
  push @array, $_;
}
[download]

or leave out the while loop and chomp the whole array, like this:

open( my $find, ... ) # (same as above, without redirecting to "/dev/n
+ull")
my @array = <$find>;  # reads all lines into array
chomp @array;         # strips linefeeds from all array elements
[download]

>/dev/null discards any output. What do you expect to obtain by reading it?
لսႽ� ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ

I don't think its possible (easy) for qx to trigger https://metacpan.org/pod/perldiag#s-x-X-does-not-map-to-Unicode

I think you need to read perlunitut: Unicode in Perl

and see about getting STDOUT/STDERR to encode stutf by default (maybe utf8::all maybe not)

I don't think its possible (easy) for qx to trigger https://metacpan.org/pod/perldiag#s-x-X-does-not-map-to-Unicode

Why, it's pretty easy

$ touch $'\xB7'
$ perl -wE 'use open qw( :encoding(utf-8) :std ); qx( ls )'
utf8 "\xB7" does not map to Unicode at -e line 1.
[download]

To the OP:

So, i suppose error appears because of the output that qx operator returns

I suppose the error appears because your file name is not in valid UTF-8. You should check that.