http://bugs.openzim.org/show_bug.cgi?id=16
Summary: Version & Subversion ZIM format handling Product: openZIM Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P1 Component: zimlib AssignedTo: tommi@tntnet.org ReportedBy: emmanuel@engelhart.org CC: dev-l@openzim.org Estimated Hours: 0.0
Currently, the zimlib is only able to deal with a specific version of the ZIM file format and otherwise generates an error.
We want: * to be able to improve as often as possible the format. * to have a zimlib able to deal with a maximum of ZIM files (potentially with different ZIM format versions).
... consequently, the current implementation may be improved.
We discussed about that during our last meeting and if I correctly remember the best proposition was IMO: * Introduce the concept of ZIM format subversion. * Zimlib can deal with all subversions of a specific ZIM format version. * If we want to add a feature which does not need to break the format, we increment the subversion counter and if necessary add subversion conditional code. * If we want to add a feature which need to break the backward compatibility, we need to increment the version counter.
With such a system, the goal is to make as much as possible subversions and no new version (but this is another topic).
http://bugs.openzim.org/show_bug.cgi?id=16
Tommi Mäkitalo tommi@tntnet.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #1 from Tommi Mäkitalo tommi@tntnet.org 2010-01-06 14:11:51 CET --- I already changed the zimlib to check just the first 2 bytes of the 4 bytes version number. In future versions we can then use the remaining bytes for a minor number. The current zimlib then will ignore, if this minor number is not zero, while zimwriter writes a zero minor number.