INSTALL zeta DOM interface

To minimize problems, initial installing of sqwebmail is recommended. Any difficulties, subsequent to a successfull sqwebmail installation, are thus likely to be zeta related. THEN turn yourself to zeta-mailinglist.

If you don't want that, at least for starters, read INSTALL in sources root directory.

REQUIREMENTS

Besides the zeta package and everything stated above in sqwebmail INSTALL instructions, you will need:

• The TRE package
  Tre is a very fast, lightweight, fuzzy matching capable regex package. Get it from http://www.laurikari.net/tre.

---

CONFIGURING

For zeta, use the same arguments as for sqwebmail installation, with the following exceptions:

Compulsory
• --prefix=[/path/to/zeta]
  Currently zeta is only available as a standalone package, and a default is used, different from sqwebmail. Hence this is actually NOT compulsory, for now.
  
  To avoid overwriting eventual sqwebmail installation, configure using a unique installation prefix, eg
  
  --prefix=/usr/lib/zeta [default]
• --with-cachedir=[path/to/sqwebmailcache]
  If sqwebmail is installed, you must use the same cache file for zeta. If a cache configuring option was used when configuring sqwebmail, use the same here. Without an argument given, the default cache file will be used ( /var/cache/sqwebmail).
• --enable-imagedir=[/path/to/zetaimages]
  Do not mix sqwebmail and zeta imagedirs. Image name conflicts may occur, and installing overwrites the clashing sqwebmail images.
  Eg. use
  --enable-imagedir=/var/www/html/zeta
• --enable-imageurl=[/url/to/zetaimages]
  Use unique zeta url.

Optional
• --without-attachmentcount
  Disable attachments counting. Enabled by default.
  To determine count attachments in a message, the whole message contents must be parsed all the way to the bitter end. This obviously takes a bit longer than skipping after message headers. Cache creation is very fast though, but it might be an issue with huge mailboxes with huge attachments.

---

LANGUAGES

If a language module is available on the download page, you're lucky. Just cd to ....zeta/html/ , untar the module, and issue the command
If no module is available, you have to do it the hard way. First cd to zeta installation html subdir: Read README_LANG.txt or README_LANG.html.
Issue the command
Follow the instructions in README_LANG to create LANGUAGE_PREF, LOCALE, CHARSET and ISPELLDICT files.
To translate the html files, cd now to the po directory, and edit the newly created [LANG].po file. You will need some gettext capability to accomplish the translation. Using eg. emacs, the task is actually quite simple: After the translation is done, cd to the new language subdirectory. The help page, containing mostly language specific text, is not included in the *.po file. Edit the help.html file separately.
When done with help page, cd ../ to ...zeta/html directory, and issue the command: This will install the new language, and reinstall the previous installed languages, specifically the updated locale.js, containing the array of installed language names.

To post fix an installed language translation:

When done with fixes,

No scripts are available for language removal.

---

CUSTOMIZE

After extracting the package, the html/en-us directory contains no html files. They will be generated at installation. Afterwards, when reinstalling, any changes to those files will be overwritten. To edit html files, edit templates in templates directory and reinstall.

NOTE: not the whole package has to be reinstalled after a template change. Cd to the html subdirectory and issue the command

This will update html templates in all installed languages.

© 2006 / Matti Riikari

This page was last modified on