Changes

Jump to: navigation, search

ZIM File Example

1,336 bytes added, 22:25, 8 May 2011
Cluster
0000100: <u>0159 5a</u>78 bdf4 58bd 108c 16c6 9ef5 d42c .YZx..X........,
0000110: a3f4 e3 ...
This is the cluster. Note that you can't know how large the cluster is until you uncompress the first bytes.
00000b0: 0000 <u>04</u>fd 377a 585a 0000 0169 22de 3602 ....7zXZ...i".6.
The first byte specifies the compression algorithm, which is 4, which means lzma (or more precise xz) here.
 
===uncompressed cluster===
When uncompressing the data we get
0000000: 0c00 0000 1900 0000 1d00 0000 3c68 313e ............&lt;h1&gt;
0000010: 4175 746f 3c2f 6831 3e41 7574 6f Auto&lt;/h1&gt;Auto
 
0000000: <u>0c00 0000</u> 1900 0000 1d00 0000 3c68 313e ............&lt;h1&gt;
The offset to the first blob in the uncompressed data is 0000 000c. There are 3 offsets in the cluster since 0c are 3*4 byte offsets. 2 offsets to the start and the last is always a offset to the end of the cluster.
 
0000000: 0c00 0000 <u>1900 0000</u> 1d00 0000 3c68 313e ............&lt;h1&gt;
 
The offset to the second blob in the uncompressed data is 0000 0019. This is also the end of the first blob.
 
0000000: 0c00 0000 1900 0000 <u>1d00 0000</u> 3c68 313e ............&lt;h1&gt;
The cluster has 0000 001d bytes uncompressed data and the end of the second (last) blob.
 
0000000: 0c00 0000 1900 0000 1d00 0000 <u>3c68 313e</u> ............<u>&lt;h1&gt;</u>
0000010: <u>4175 746f 3c2f 6831 3e</u>41 7574 6f <u>Auto&lt;/h1&gt;</u>Auto
This is the data of the first blob from offset 00c0 to 0019-1.
 
0000010: 4175 746f 3c2f 6831 3e<u>41 7574 6f</u> Auto&lt;/h1&gt;Auto
This is the data of the first blob from offset 0019 to 001d-1.

Navigation menu