Sylpheed / Claws for Win32:
Before downloading, please note:
- Have a look at the README-w32.txt
and the tips section below.
- The window ports of Sylpheed and especially Sylpheed-claws are work in progress.
- Although they usually run stable, they may crash and even destroy your
data, so be sure to make backups.
- The main part of porting Sylpheed to Windows
was done by Munesato Nakada <munesato@post.co.jp>.
- This english installation help and the Sylpheed-Claws port are derived from
his work by Thorsten Maerz <info@netztorte.de>.
More files available at the download archive.
Binaries :
Sylpheed binaries
|
|
|
Complete Sylpheed for Win32 installer.
|
|
Sylpheed claws binaries
|
|
|
Complete Sylpheed-Claws for Win32 installer and updates.
The executable will be updated quite regularly. To update, just extract
it into the "bin" subdir of your Claws installation.
|
|
Sources :
Compiling sylpheed / sylpheed-claws using MS VisualC++ 6.0
|
|
- The Gtk+ and support libraries
below are needed for both sylpheed versions.
- Create the directory tree for the sources as shown in the readme.txt.
- To compile standard sylpheed, you need the sylpheed-dev package
in addition to the original sylpheed sources.
- Be sure to apply the provided patches.
To get the cvs checkout :
- cvs -z3 -d:pserver:anonymous@cvs.sylpheed-claws.sf.net:/cvsroot/sylpheed-claws
login
(enter an empty password)
- cvs -z3 -d:pserver:anonymous@cvs.sylpheed-claws.sf.net:/cvsroot/sylpheed-claws
co -r win32 sylpheed-claws
CVS and some other unix utilities needed to build the claws version are contained in unix-tools.zip
|
|
|
Sylpheed sources
|
|
|
To compile the standard sylpheed, first extract the original
sources, then unpack the MSVC project and apply the provided patch.
|
|
Sylpheed claws sources
|
|
- checkout from CVS
- or -
- download a nightly snapshot
|
The CVS checkout and nightly snapshot need to generate some files
before compilation. Call "patch_claws.bat" or compile using the
provided Makefile in win32 directory.
|
|
Tips :
Naming convention:
- Win9x : Windows 95, 98, 98se, Millenium
- WinNT : Windows NT 4.0, NT 2000, XP (all flavours)
Configuration:
- Set the evironment variable
LANG
to select your native language.
Available translations: cs de el en_GB es fr hr it ja ko nl pl pt_BR ru sv
- Set the evironment variable
HOME
to a path where Gtk+ and Sylpheed
store their configuration and data files.
- Sylpheed requires following registry key to work:
-
in
[HKEY_CURRENT_USER\Software\Sylpheed]
create a new string value called
InstalledDir
that points to your Sylpheed root directory (e.g. C:\Sylpheed
).
-
in
[HKEY_CURRENT_USER\Software\Sylpheed]
create a new string value called
HomeDir
that points to your home directory (e.g. C:\home
).
-
or download sylpheed.reg,
patch it to your needs and import it using a double click.
Otherwise, Sylpheed assumes it is installed in C:\Sylpheed
.
- The GPGME interface requires following registry key to work:
-
in
[HKEY_CURRENT_USER\Software\GNU\GnuPG]
create a new string value called
gpgProgram
that points to your gnupg executable (e.g. C:\gnupg\gpg.exe
)
-
or download gpgme_sylpheed.reg,
patch it to your needs and import it using a double click.
- To install sylpheed as the default mailer when clicking mailto: links,
download and doubleclick default-mailer.reg (thanks to Jonas Diemer)
(thanks to Jonas Diemer)
- To track down problems, start sylpheed with the --debug option. It appends
many useful information to
.sylpheed\debug.log
.
You can also use the binary debug versions from the additional
download section (you will need the debug-dll pack as well), which gives some more
output and prints it to a console window.
- If Sylpheed hangs during transfer, you may have a different glib.dll
(e.g. the original). Get the patched standard-dll pack.
- The external editor must neither fork nor be started by a loader, as the
PID is used to watch the application.
- If parts of the text are not displayed correctly, this could be caused by a wrong charset / encoding.
Standard Sylpheed does not yet offer all font settings in the menu (Claws does),
so you need to edit the font entries in .sylpheed\sylpheedrc
manually. Change entries like
bold_font=-*-*-normal-r-normal--10-*-*-*-m-*-jisx0208.1983-0
to
bold_font=-*-*-normal-r-normal--10-*-*-*-m-*-*-*
(you can also force a specific encoding by using e.g. iso8859-2
instead of *-*
).
- Menufonts and widgetcolours can be set using gtk themes. There are two sample gtkrc
which select a smaller menufont (you may need them to get Claws configure dialog fit
into 800x600 pixels). Put either gtkrc.95
or gtkrc.xp into
%HOME%\.sylpheed\gtk\
and rename it to gtkrc to install them.
- Sharing the local mailbox between several OS is possible.
a symlink to it in your *nix HOME directory:
A common setup is having the mail folder on a FAT32 partition and creating a symlink to it in your *nix HOME directory:
ln -s /windows/C/home/Mail ~/Mail
If you have problems mounting the partition at startup and/or grant write access
to users, you may get some tips from following email conversation
- You can use placeholders for Windows specific path names (only Claws/Win32):
- ?p : program files (e.g. "C:\Program files")
- ?w : windows dir (e.g. "C:\Windows")
- ?s : system dir (e.g. "C:\Windows\system")
- ?t : temp dir (e.g. "C:\TEMP")
- ?? : question mark
- You can define applications for opening attachments in a
mailcap.win32
file in your %install%/etc
(global) or %HOME%
directory.
You can download a sample here.
- When working with local mail- or newsservers (e.g. Hamster), make sure your
HOSTS
file
contains a localhost entry like:
localhost 127.0.0.1
This file should be located in \WINDOWS
on Win9x or
\WINNT\SYSTEM32\DRIVERS\ETC
on WinNT and above.
- GnuPG isnt distributed with Sylpheed / Claws any longer, as it caused problems on
systems, which already had a working gpg installation (gpg version, HOME directory,...).
You can download GnuPG from following locations:
Compilation:
- When running in debugger: If you encounter lots of exceptions on pop transfers, you will also need the patched dlls.
- When compiling -standard- sylpheed, you have to copy all
*.lib
to \dev\lib
and
all *.h
to \dev\include
, or adjust the path settings in the project options.
- There are some autogenerated files on *nix systems (translations, bison/flex
generated parsers, config.h, version.h). The standard sylpheed currently provides
them, the Claws version creates them using the unix-tools from below.
- When compiling translations using msgfmt, remember to convert the
*.po
files to utf8 first.
Known bugs:
- Actions: Running external apps not yet implemented (matchactions are working).
- Image display in MIME-view: Not working yet.
- Double-clicks in textview: Not working ->use <Shift-RightClick>
and <RightClick> instead.
- News: Crashes after retrieving the group list have been reported. To fix this,
create a folder in the newscache directory with the name of your NNTP server, e.g.
.sylpheed\newscache\news.provider.com
.
- Attachments: Standard Sylpheed seems to have difficulties with attachment names containing locale characters.
Getting Help:
Win32 related questions and experience reports regarding both Sylpheed versions
are welcome at the claws-w32-users mailinglist.
- claws-w32-users (no subscription needed for postings)
If you have feature requests, usage questions or bugreports not related to Windows,
please commit them via the mailing lists or tracking system below.
- Sylpheed Mailinglist
- Claws-Users Mailinglist
- Claws Support/Patch/Bugtracker (no subscription needed for postings)
Additional downloads :
Links :
Original Sylpheed : by Hiroyuki Yamamoto <hiro-y@kcn.ne.jp>
http://sylpheed.good-day.net
Sylpheed-Claws homepage :
http://sylpheed-claws.sourceforge.net
Gtk+ / Win32 homepage : by Tor Lillqvist (tml) <tml@iki.fi>
http://www.gimp.org/~tml/gimp/win32
Sylpheed forWin32 : by Munesato Nakada (NAK) <munesato@post.co.jp>
http://www2.odn.ne.jp/munesato/sylpheed
Sylpheed-Claws for Win32 : by Thorsten Maerz <torte@netztorte.de>
http://netztorte.de/sylpheed