Difference between revisions of "Mod2zmod"
David Haslam (talk | contribs) (See also) |
David Haslam (talk | contribs) (added introduction and usage sections) |
||
| Line 1: | Line 1: | ||
| + | == Introduction == | ||
| + | |||
| + | '''mod2zmod''' creates a compressed module from an installed module. | ||
| + | |||
| + | In practice, <tt>tei2mod</tt> and <tt>osis2mod</tt> really only need to turn XML into raw{text|com|ld} modules. The reason for this is that <tt>mod2zmod</tt> (which works all module types except genbooks) will produce better compressed modules than the other conversion tools. In turn, the reason for this is that the conversion tools build modules incrementally and compress them incrementally, resulting in compressed modules that are not compressed as well as modules that are compressed all at once, as <tt>mod2zmod</tt> does. So it's always better to build module in a 2-pass procedure: one pass to fix the contents and their order and one pass to compress/encipher. | ||
| + | |||
| + | <tt>mod2zmod</tt> can encipher as it compresses, so there's nothing preventing the creation of compressed TEI-sourced dictionaries. | ||
| + | |||
| + | == Usage == | ||
| + | |||
| + | <pre> | ||
| + | utils\mod2zmod - a tool to create compressed Sword modules | ||
| + | version 0.1 | ||
| + | |||
| + | usage: utils\mod2zmod <modname> <datapath> [blockType [compressType [cipherKey]]] | ||
| + | |||
| + | datapath: the directory in which to write the zModule | ||
| + | blockType : (default 4) | ||
| + | 2 - verses | ||
| + | 3 - chapters | ||
| + | 4 - books | ||
| + | compressType: (default 1): | ||
| + | 1 - LZSS | ||
| + | 2 - Zip | ||
| + | </pre> | ||
| + | |||
== See also == | == See also == | ||
Revision as of 10:45, 15 November 2011
Introduction
mod2zmod creates a compressed module from an installed module.
In practice, tei2mod and osis2mod really only need to turn XML into raw{text|com|ld} modules. The reason for this is that mod2zmod (which works all module types except genbooks) will produce better compressed modules than the other conversion tools. In turn, the reason for this is that the conversion tools build modules incrementally and compress them incrementally, resulting in compressed modules that are not compressed as well as modules that are compressed all at once, as mod2zmod does. So it's always better to build module in a 2-pass procedure: one pass to fix the contents and their order and one pass to compress/encipher.
mod2zmod can encipher as it compresses, so there's nothing preventing the creation of compressed TEI-sourced dictionaries.
Usage
utils\mod2zmod - a tool to create compressed Sword modules version 0.1 usage: utils\mod2zmod <modname> <datapath> [blockType [compressType [cipherKey]]] datapath: the directory in which to write the zModule blockType : (default 4) 2 - verses 3 - chapters 4 - books compressType: (default 1): 1 - LZSS 2 - Zip
