diff options
| author | Nick Clifton <nickc@redhat.com> | 2022-04-12 16:24:10 +0100 |
|---|---|---|
| committer | Nick Clifton <nickc@redhat.com> | 2022-04-12 16:24:10 +0100 |
| commit | 8e6b35366073a1a71df805061ecf016cc915a9f9 (patch) | |
| tree | 6ddbc8123ab4bdbcd3fba1a4c6e0f1091f66964e /zlib/doc | |
| parent | 63e0ee15a327b933a9e325908f6e5b334106290c (diff) | |
| download | gdb-8e6b35366073a1a71df805061ecf016cc915a9f9.zip gdb-8e6b35366073a1a71df805061ecf016cc915a9f9.tar.gz gdb-8e6b35366073a1a71df805061ecf016cc915a9f9.tar.bz2 | |
Rebase the zlib sources to the 1.2.12 release
Diffstat (limited to 'zlib/doc')
| -rw-r--r-- | zlib/doc/crc-doc.1.0.pdf | bin | 0 -> 776142 bytes | |||
| -rw-r--r-- | zlib/doc/txtvsbin.txt | 12 |
2 files changed, 6 insertions, 6 deletions
diff --git a/zlib/doc/crc-doc.1.0.pdf b/zlib/doc/crc-doc.1.0.pdf Binary files differnew file mode 100644 index 0000000..d6942ec --- /dev/null +++ b/zlib/doc/crc-doc.1.0.pdf diff --git a/zlib/doc/txtvsbin.txt b/zlib/doc/txtvsbin.txt index 3d0f063..2a901ea 100644 --- a/zlib/doc/txtvsbin.txt +++ b/zlib/doc/txtvsbin.txt @@ -38,15 +38,15 @@ The Algorithm The algorithm works by dividing the set of bytecodes [0..255] into three categories: -- The white list of textual bytecodes: +- The allow list of textual bytecodes: 9 (TAB), 10 (LF), 13 (CR), 32 (SPACE) to 255. - The gray list of tolerated bytecodes: 7 (BEL), 8 (BS), 11 (VT), 12 (FF), 26 (SUB), 27 (ESC). -- The black list of undesired, non-textual bytecodes: +- The block list of undesired, non-textual bytecodes: 0 (NUL) to 6, 14 to 31. -If a file contains at least one byte that belongs to the white list and -no byte that belongs to the black list, then the file is categorized as +If a file contains at least one byte that belongs to the allow list and +no byte that belongs to the block list, then the file is categorized as plain text; otherwise, it is categorized as binary. (The boundary case, when the file is empty, automatically falls into the latter category.) @@ -84,9 +84,9 @@ consistent results, regardless what alphabet encoding is being used. results on a text encoded, say, using ISO-8859-16 versus UTF-8.) There is an extra category of plain text files that are "polluted" with -one or more black-listed codes, either by mistake or by peculiar design +one or more block-listed codes, either by mistake or by peculiar design considerations. In such cases, a scheme that tolerates a small fraction -of black-listed codes would provide an increased recall (i.e. more true +of block-listed codes would provide an increased recall (i.e. more true positives). This, however, incurs a reduced precision overall, since false positives are more likely to appear in binary files that contain large chunks of textual data. Furthermore, "polluted" plain text should |