String with the URL as refered in the URL pointer list (not used) identifies a revision of the contents of this directory entry, needed to identify updates or revisions in the original history (must be 0)Ĭluster number in which the data of this directory entry is storedīlob number inside the compressed cluster where the contents are stored (not used) length of extra paramters (must be 0)ĭefines to which namespace this directory entry belongs MIME type number as defined in the MIME type list There are different types of directory entries: accessing directory entries by title also makes use of cached directory entries which are referenced by the URL pointers, as implemented in zimlib.ĭirectory entries hold the meta information about all entries, images and other objects in a ZIM archive.the pointer list is only half in size as 4 bytes are enough for each entry.The indirection from titles via URLs to directory entries has two reasons: To get the offset of an entry from the title pointer list, you have to look it up in the URL pointer list. They are not offsets in the file but entry numbers. Note that the title pointers are only 4 bytes. The title pointer list actually points to entries in the URL pointer list. The title pointer list is a list of entry indices ordered by title ( ). Zimlib caches directory entries and references the cached entries via the URL pointers. Since directory entries have variable sizes this is needed for random access. Ordering is simply done by comparing the URL strings. The directory entries are always ordered by "full" URL ( ). The URL pointer list is a list of 8 byte offsets to the directory entries. An empty string marks the end of the MIME type list. The MIME types in this list are zero terminated strings. The MIME type list always follows directly after the header, so the mimeListPos also defines the end and size of the ZIM file header. Readers allowing to read an embedded archive must adapt offset accordingly. In the context of zim format, the start of the zim header is the offset 0. 1 : We use the new namespace usage (describe here).Ī zim archive may be embedded in another file at a specific offset.0 : We use the old namespace usage (see ZIM file format old namespace).They are the same than 6 less extended cluster, so you can read a 5 major version as if it was a 6. You may found old zim archives with major version 5. Minor version is updated when an compatible change is integrated (a lib made for a minor version n will be able to read a version n+1) Major version is updated when an incompatible change is integrated in the format (a lib made for a version N will probably not be able to read a version N+1) This points always 16 bytes before the end of the archive. Pointer to the md5checksum of this archive without the checksum itself. Layout page or 0xffffffffff if no layout page (deprecated, always 0xffffffffff) Position of the MIME type list (also header size) This is considered as obsolete, readers should use X/listing/titleordered/v0 instead and fallback to titlePtrPos if entry is not present. Position of the directory pointerlist ordered by Title Position of the directory pointerlist ordered by URL Minor version of the ZIM archive format (1 for new namespace usage, 0 for old namespace usage) Major version of the ZIM archive format (6) Magic number to recognise the file format, must be 72173914 (0x44D495A) 5.3 Linktarget or deleted Entry (DEPRECATED).This is what you want for Android: 2.3 from sourceforge and split.į-droid 2. However this version WORKS JUST FINE with the 2GB split file (split -bytes=2000M). HOWEVER kiwix has a sourceforge page and the 2.3 versions from there DO work, more specifically:įirefox extension (.xpi) works just fine with the 70+GB file (BTW there is one from 2018-06 now)Īndroid version (2.3 from sourceforge) will open the huge file on the phone and display fine but there's something wrong with the indexes, in the sense that it won't find anything (can't even navigate to specific "word", you can only click on hyperlinks starting from the original page or use random page. I'm writing this as follow-up to which suggested the recent big files are broken. UPDATE UPDATE UPDATE - the recent versions from do not work with the latest "normal" versions of kiwix you would get from their page or Android/Google Play Store.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |