Difference between revisions of "Zipped modules"
David Haslam (talk | contribs) m (-from (grammar)) |
David Haslam (talk | contribs) m (lightly edited para 3 to improve readability) |
||
| Line 3: | Line 3: | ||
JSword front-ends also require (for the moment at least) having zipped modules available. | JSword front-ends also require (for the moment at least) having zipped modules available. | ||
| − | It is also helpful for people who have no access to | + | It is also helpful for people who have no direct access to the Internet or who live in countries with monitored access to the Internet to be able to download (and possibly distribute) zipped modules. This is a zipped archive of a module in the file and directory layout used in the local module directory. |
E.g. to create from your own module directory a zipped module of a uncompressed GenBook do this: | E.g. to create from your own module directory a zipped module of a uncompressed GenBook do this: | ||
Revision as of 17:26, 5 November 2010
Some of the smaller devices running a sword front-end might not not have a network enabled module manager or network use might be slow and expensive. Users of these devices need to download their modules as zipped files and unzip them in the right place - e.g. a SD card.
JSword front-ends also require (for the moment at least) having zipped modules available.
It is also helpful for people who have no direct access to the Internet or who live in countries with monitored access to the Internet to be able to download (and possibly distribute) zipped modules. This is a zipped archive of a module in the file and directory layout used in the local module directory.
E.g. to create from your own module directory a zipped module of a uncompressed GenBook do this:
cd ~ftp/pub/sword zip zip/mybook.zip mods.d/mybook.conf modules/genbook/rawgenbooks/mybook
