Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

75%
+4 −0
Q&A Why does the file command fail to recognize non-text files as such?

You might be enlightened by reading the man page for file(1). A brief quotation: This manual page documents version 5.35 of the file command. file tests each argument in an attempt to classify...

posted 3y ago by dsr‭  ·  edited 3y ago by Quasímodo‭

Answer
#2: Post edited by user avatar Quasímodo‭ · 2021-05-31T11:40:35Z (almost 3 years ago)
Fixed misplaced hyphenation
  • You might be enlightened by reading the man page for file(1).
  • A brief quotation:
  • > This manual page documents version 5.35 of the file command.
  • file tests each argument in an attempt to classify it. There are three sets of tests, performed in this order: filesystem tests, magic tests, and
  • language tests. The first test that succeeds causes the file type to be printed.
  • The type printed will usually contain one of the words text (the file contains only printing characters and a few common control characters and is
  • probably safe to read on an ASCII terminal), executable (the file contains the result of compiling a program in a form understandable to some UNIX
  • kernel or another), or data meaning anything else (data is usually “binary” or non-printable).
  • Then we skip a bit:
  • > If a file does not match any of the entries in the magic file, it is examined to see if it seems to be a text file. ASCII, ISO-8859-x, non-ISO 8-bit
  • extended-ASCII character sets (such as those used on Macintosh and IBM PC systems), UTF-8-encoded Unicode, UTF-16-encoded Unicode, and EBCDIC charac
  • ter sets can be distinguished by the different ranges and sequences of bytes that constitute printable text in each set. If a file passes any of
  • these tests, its character set is reported. ASCII, ISO-8859-x, UTF-8, and extended-ASCII files are identified as “text” because they will be mostly
  • readable on nearly any terminal; UTF-16 and EBCDIC are only “character data” because, while they contain text, it is text that will require translation before it can be read. In addition, file will attempt to determine other characteristics of text-type files. If the lines of a file are terminated by CR, CRLF, or NEL, instead of the Unix-standard LF, this will be reported. Files that contain embedded escape sequences or overstriking will also be identified.
  • So: you have very small UTF-8 files. file(1) does as specified by its man page, and announces that pretty much all of them are plausibly text.
  • You might be enlightened by reading the man page for file(1).
  • A brief quotation:
  • > This manual page documents version 5.35 of the file command.
  • file tests each argument in an attempt to classify it. There are three sets of tests, performed in this order: filesystem tests, magic tests, and
  • language tests. The first test that succeeds causes the file type to be printed.
  • The type printed will usually contain one of the words text (the file contains only printing characters and a few common control characters and is
  • probably safe to read on an ASCII terminal), executable (the file contains the result of compiling a program in a form understandable to some UNIX
  • kernel or another), or data meaning anything else (data is usually “binary” or non-printable).
  • Then we skip a bit:
  • > If a file does not match any of the entries in the magic file, it is examined to see if it seems to be a text file. ASCII, ISO-8859-x, non-ISO 8-bit
  • extended-ASCII character sets (such as those used on Macintosh and IBM PC systems), UTF-8-encoded Unicode, UTF-16-encoded Unicode, and EBCDIC character sets can be distinguished by the different ranges and sequences of bytes that constitute printable text in each set. If a file passes any of
  • these tests, its character set is reported. ASCII, ISO-8859-x, UTF-8, and extended-ASCII files are identified as “text” because they will be mostly
  • readable on nearly any terminal; UTF-16 and EBCDIC are only “character data” because, while they contain text, it is text that will require translation before it can be read. In addition, file will attempt to determine other characteristics of text-type files. If the lines of a file are terminated by CR, CRLF, or NEL, instead of the Unix-standard LF, this will be reported. Files that contain embedded escape sequences or overstriking will also be identified.
  • So: you have very small UTF-8 files. file(1) does as specified by its man page, and announces that pretty much all of them are plausibly text.
#1: Initial revision by user avatar dsr‭ · 2021-05-27T23:12:22Z (almost 3 years ago)
You might be enlightened by reading the man page for file(1).

A brief quotation:

> This manual page documents version 5.35 of the file command.
     file tests each argument in an attempt to classify it.  There are three sets of tests, performed in this order: filesystem tests, magic tests, and
     language tests.  The first test that succeeds causes the file type to be printed.
     The type printed will usually contain one of the words text (the file contains only printing characters and a few common control characters and is
     probably safe to read on an ASCII terminal), executable (the file contains the result of compiling a program in a form understandable to some UNIX
     kernel or another), or data meaning anything else (data is usually “binary” or non-printable). 
    

Then we skip a bit:


 >   If a file does not match any of the entries in the magic file, it is examined to see if it seems to be a text file.  ASCII, ISO-8859-x, non-ISO 8-bit
     extended-ASCII character sets (such as those used on Macintosh and IBM PC systems), UTF-8-encoded Unicode, UTF-16-encoded Unicode, and EBCDIC charac‐
     ter sets can be distinguished by the different ranges and sequences of bytes that constitute printable text in each set.  If a file passes any of
     these tests, its character set is reported.  ASCII, ISO-8859-x, UTF-8, and extended-ASCII files are identified as “text” because they will be mostly
     readable on nearly any terminal; UTF-16 and EBCDIC are only “character data” because, while they contain text, it is text that will require translation before it can be read.  In addition, file will attempt to determine other characteristics of text-type files.  If the lines of a file are terminated by CR, CRLF, or NEL, instead of the Unix-standard LF, this will be reported.  Files that contain embedded escape sequences or overstriking will also be identified.

So: you have very small UTF-8 files. file(1) does as specified by its man page, and announces that pretty much all of them are plausibly text.