Post History
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...
Answer
#2: Post edited
- 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
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.