Sqwebmail roadmap
Brian Candler <[email protected]>
| Newsgroups | gmane.mail.sqwebmail |
|---|---|
| Message-ID | <[email protected]> |
I have a few suggestions for where I think Sqwebmail ought to go - and I wonder if other people concur or have other suggestions. It might be nice to have a wishlist which people can work on. Regards, Brian.
sqwebmail-wishlist
(text/plain, 1.9 KB)
SQWEBMAIL 4.1 ------------- (1) Sort out stderr capturing / courierlogger for sqwebmaild, pcpd (2) Introduce sqwebmaild.rc - startup script to start sqwebmaild and its corresponding authdaemond (3) Introduce sqwebmail.conf - read by sqwebmaild.rc at startup, replaces the separate files authmodulelist, nochangingfrom, nodsn, hostname, autoresponsesquota, usexsender, noimages Advantages: tidier, works in a more similar way to courier-imap SQWEBMAIL 5 ----------- (1) Bite the internationalization bullet What I suggest is - remove all natural language strings from templates; replace them with placeholders like "#123" which are pointers into a language-specific dictionary file - login.html / expired.html / invalid.html are replaced by a single page which just includes one of three dictionary strings - user can selected preferred character set(s) for outgoing mails as a preference option, perhaps also as a per-message option. If all the characters in the mail can be represented in the other character set, then use it instead of UTF-8. - maybe life is simpler if templates and all dictionary files are precompiled into UTF-8. Then the UTF-8 version is converted to the browser character set at runtime if necessary. - (todo: decide what to do about footer, TIMEZONELIST, ISPELLDICT) Advantages: a translation needs only a new dictionary file. There is only one template set. An alternative template set would only be needed for a radically different layout, not for a translation. More translations are likely to be forthcoming and they will remain current. (2) Stylesheets - rework templates and HTML output to use CSS entirely. An ancient non-CSS browser might give unattractive screen layout but it will still work. - it should be possible to completely redesign the screen layout just by replacing the images and the CSS (and perhaps also login.html for a very fancy login screen) - are we happy to lose the rounded corners??