Skip to content

Commit e84851b

Browse files
committed
Put explicit little endian format in documentation for unique lengths
1 parent 70e94cd commit e84851b

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

docs/source/unique_format.rst

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,8 @@ Data types
1818
The suffix of the filename specifies the type of the underlying binary data.
1919
The suffix ``uint8`` specifies that each minimum length is represented with a
2020
single unsigned 8 bit integer (1 byte each), and ``uint16`` likewise has each
21-
length represented by unsigned 16 bit integer (2 bytes each). No other data is
21+
length represented by unsigned 16 bit integer (2 bytes each). All lengths that
22+
need more than 1 byte are stored in little endian format. No other data is
2223
stored in the file. The data type is chosen based on the maximum length
2324
specified in range specified to :ref:`search`. For example, in a search
2425
range from 20 to 255, the maximum unique minimum length is less than or equal

0 commit comments

Comments
 (0)