https://sourceware.org/bugzilla/show_bug.cgi?id=27551

--- Comment #14 from Nick Clifton <nickc at redhat dot com> ---
(In reply to Vincent Lefèvre from comment #13)

>> No - this is the correct behaviour.  The 's' encoding says that the
>> characters in the file being examined are 7-bits long, not 8-bits.  

> Then the 's' encoding must not be the default for non-ASCII encodings.

But that is the point.  The encoding of characters in the file being scanned is
not known.  Using LC_CTYPE is incorrect, because that specifies how to display
characters, not to read them.  So strings has a default encoding of 's', which
matches the most common case of ASCII strings being stored in the binary.  But
if the user knows that the strings were encoded using a different character
set, then they can use the --encoding command line option to tell strings what
to do.

Cheers
  Nick

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to