1 @c This is part of the XEmacs manual.
2 @c Copyright (C) 1985, 86, 87, 93, 94, 95, 1997 Free Software Foundation, Inc.
3 @c See file xemacs.texi for copying conditions.
4 @node Packages, Basic, Startup Paths, Top
5 @comment node-name, next, previous, up
10 The XEmacs 21 distribution comes only with a very basic set of
11 built-in modes and packages. Most of the packages that were part of
12 the distribution of earlier versions of XEmacs are now available
13 separately. The installer as well as the user can choose which
14 packages to install; the actual installation process is easy.
15 This gives an installer the ability to tailor an XEmacs installation for
16 local needs with safe removal of unnecessary code.
19 * Package Terminology:: Understanding different kinds of packages.
20 * Installing Packages:: How to install packages.
21 * Building Packages:: Building packages from CVS sources.
22 * Local.rules File:: This is an important file that you must create.
23 * Creating Packages:: The basics.
24 * Available Packages:: A brief directory of packaged LISP.
27 @node Package Terminology, Installing Packages, , Packages
28 @comment node-name, next, previous, up
29 @heading Package Terminology:
30 @subsection Package Flavors
32 There are two main flavors of packages.
37 @cindex regular packages
38 A regular package is one in which multiple files are involved and one
39 may not in general safely remove any of them.
43 @cindex single-file packages
44 A single-file package is an aggregate collection of thematically
45 related but otherwise independent lisp files. These files are bundled
46 together for download convenience and individual files may be deleted at
47 will without any loss of functionality. However, we would recommend
48 that you follow this rule of thumb: "When in doubt, don't delete".
51 @subsection Package Distributions
52 @cindex package distributions
53 XEmacs Lisp packages are distributed in two ways, depending on the
54 intended use. Binary Packages are for installers and end-users that can
55 be installed directly into an XEmacs package directory. Source Packages
56 are for developers and include all files necessary for rebuilding
57 bytecompiled lisp and creating tarballs for distribution.
59 @subsection Binary Packages
60 @cindex binary packages
61 Binary packages may be installed directly into an XEmacs package
64 @subsection Source Packages
65 @cindex source packages
66 Source packages contain all of the Package author's (where appropriate
67 in regular packages) source code plus all of the files necessary to
68 build distribution tarballs (Unix Tar format files, gzipped for space
71 Currently, source packages are only available via CVS. See
72 @url{http://cvs.xemacs.org/} for details.
73 @node Installing Packages, Building Packages, Package Terminology, Packages
74 @comment node-name, next, previous, up
75 @cindex installing packages
77 @heading Installing Packages:
78 @subsection Getting Started
80 When you first download XEmacs 21, you will usually first grab the
81 @dfn{core distribution},
82 @cindex core distribution
84 @file{xemacs-21.x.x.tar.gz}. (Replace the @t{21.x.x} by the current version
85 number.) The core distribution contains the sources of XEmacs and a
86 minimal set of Emacs Lisp files, which are in the subdirectory named
87 @file{lisp}. This subdirectory used to contain all Emacs Lisp files
88 distributed with XEmacs. Now, to conserve disk space, most
89 non-essential packages were made optional.
91 @subsection Choosing the Packages You Need
92 @cindex choosing packages
93 The @ref{Available Packages} can currently be found in the same ftp directory
94 where you grabbed the core distribution from, and are located in the
95 subdirectory @file{packages}. Package file names follow
96 the naming convention @file{<package-name>-<version>-pkg.tar.gz}.
98 If you have EFS @ref{(EFS)}, packages can be installed over the network.
99 Alternatively, if you have copies of the packages locally, you can
100 install packages from a local disk or CDROM.
102 The file @file{etc/PACKAGES} in the core distribution contains a list of
103 the @ref{Available Packages} at the time of the XEmacs release. Packages are
104 also listed on the @code{Options} menu under:
107 Options->Customize->Emacs->Packages
110 However, don't select any of these menu picks unless you actually want
111 to install the given package (and have properly configured your system
114 You can also get a list of available packages, and whether or not they
115 are installed, using the visual package browser and installer. You can
116 access it via the menus:
119 Options->Manage Packages->List & Install
122 Or, you can get to it via the keyboard:
125 M-x pui-list-packages
128 Hint to system administrators of multi-user systems: it might be a good
129 idea to install all packages and not interfere with the wishes of your
132 If you can't find which package provides the feature you require, try
133 using the @code{package-get-package-provider} function. Eg., if you know
134 that you need @code{thingatpt}, type:
137 M-x package-get-package-provider RET thingatpt
140 which will return something like (fsf-compat "1.08"). You can the use
141 one of the methods above for installing the package you want.
143 @subsection XEmacs and Installing Packages
145 There are three main ways to install packages:
148 * Sumo:: All at once, using the 'Sumo Tarball'.
149 * Manually:: Using individual package tarballs.
150 * Automatically:: Using the package tools from XEmacs.
151 * Which Packages:: Which packages to install.
152 * Removing Packages:: Removing packages.
155 But regardless of the method you use to install packages, they can only
156 be used by XEmacs after a restart.
158 @node Sumo, Manually, ,Installing Packages
159 @comment node-name, next, previous, up
160 @cindex sumo package install
161 @heading Installing the Sumo Packages:
162 Those with little time, cheap connections and plenty of disk space can
163 install all the packages at once using the sumo tarballs.
164 Download the file: @file{xemacs-sumo.tar.gz}
166 For an XEmacs compiled with Mule you also need: @file{xemacs-mule-sumo.tar.gz}
168 N.B. They are called 'Sumo Tarballs' for good reason. They are
169 currently about 19MB and 4.5MB (gzipped) respectively.
173 @code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xvf - RET}
175 Or, if you have GNU tar:
177 @code{cd $prefix/lib/xemacs ; tar zxvf /path/to/<tarballname> RET}
179 As the Sumo tarballs are not regenerated as often as the individual
180 packages, it is recommended that you use the automatic package tools
181 afterwards to pick up any recent updates.
183 @node Manually, Automatically, Sumo, Installing Packages
184 @comment node-name, next, previous, up
185 @cindex manual package install
186 @heading Manual Package Installation:
187 Fetch the packages from the FTP site, CD-ROM whatever. The filenames
188 have the form @file{name-<version>-pkg.tar.gz} and are gzipped tar files. For
189 a fresh install it is sufficient to untar the file at the top of the
192 Note: If you are upgrading packages already installed, it's best to
193 remove the old package first @ref{Removing Packages}.
195 For example if we are installing the @file{xemacs-base}
196 package (version 1.48):
199 mkdir $prefix/lib/xemacs/xemacs-packages RET # if it does not exist yet
200 cd $prefix/lib/xemacs/xemacs-packages RET
201 gunzip -c /path/to/xemacs-base-1.48-pkg.tar.gz | tar xvf - RET
203 Or if you have GNU tar, the last step can be:
205 tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET
208 For MULE related packages, it is best to untar into the mule-packages
209 hierarchy, i.e. for the @file{mule-base} package, version 1.37:
212 mkdir $prefix/lib/xemacs/mule-packages RET # if it does not exist yet
213 cd $prefix/lib/xemacs/mule-packages RET
214 gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET
216 Or if you have GNU tar, the last step can be:
218 tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET
221 @node Automatically, Which Packages ,Manually, Installing Packages
222 @comment node-name, next, previous, up
223 @cindex automatic package install
224 @cindex package tools
225 @heading Automatic Package Installation:
226 XEmacs comes with some tools to make the periodic updating and
227 installing easier. It will notice if new packages or versions are
228 available and will fetch them from the FTP site.
230 Unfortunately this requires that a few packages are already in place.
231 You will have to install them by hand as above or use a SUMO tarball.
232 This requirement will hopefully go away in the future. The packages
236 efs - To fetch the files from the FTP site or mirrors.
237 xemacs-base - Needed by efs.
241 mule-base - Needed if you want to use XEmacs with MULE.
244 After installing these by hand, fire up XEmacs and follow these
247 Note: The menus in XEmacs 21.2.x and up have changed slightly, so
248 where I mention "Options -> Manage Packages", substitute "Tools ->
253 Choose a download site.
254 via menu: Options -> Manages Packages -> Add Download Site
255 via keyb: @code{M-x customize-variable RET package-get-remote RET}
256 (put in the details of remote host and directory)
258 If the package tarballs _AND_ the package-index file are in a
259 local directory, you can: @code{M-x pui-add-install-directory RET}
262 Obtain a list of packages and display the list in a buffer named
264 menu: Options -> Manage Packages -> List & Install
265 keyb: @code{M-x pui-list-packages RET}
267 XEmacs will now connect to the remote site and download the
268 latest package-index file. If you see an error about the
269 package-index entries not being PGP signed, you can safely
270 ignore this because PGP has not been integrated into the XEmacs
273 The visual package browser will then display a list of all packages.
274 Help information will be displayed at the very bottom of the buffer; you
275 may have to scroll down to see it. You can also press @kbd{?} to get
276 the same help. From this buffer, you can tell the package status by the
277 character in the first column:
281 The package has not been installed.
283 The package has been installed, but a newer version is available. The
284 current version is out-of-date.
286 The package has been marked for installation/update.
289 If there is no character in the first column, the package has been
290 installed and is up-to-date.
292 From here, you can select or unselect packages for installation using
293 the @key{RET} key, the @kbd{Mouse-2} button or selecting "Select" from
295 Once you've finished selecting the packages, you can
296 press the @kbd{x} key (or use the menu) to actually install the
297 packages. Note that you will have to restart XEmacs for XEmacs to
298 recognize any new packages.
307 Toggle between selecting and unselecting a package for installation.
309 Install selected packages.
311 View, in the minibuffer, additional information about the package, such
312 as the package date (not the build date) and the package author. Moving
313 the mouse over a package name will also do the same thing.
315 Toggle between verbose and non-verbose package display.
317 Refresh the package display.
319 Kill the package buffer.
322 Moving the mouse over a package will also cause additional information
323 about the package to be displayed in the minibuffer.
327 Choose the packages you wish to install.
328 mouse: Click button 2 on the package name.
329 keyb: @kbd{RET} on the package name
332 Make sure you have everything you need.
333 menu: Packages -> Add Required
336 XEmacs will now search for packages that are required by the
337 ones that you have chosen to install and offer to select
340 For novices and gurus alike, this step can save your bacon.
341 It's easy to forget to install a critical package.
344 Download and install the packages.
345 menu: Packages -> Install/Remove Selected
349 You can also install packages using a semi-manual interface:
352 M-x package-get-all <return>
355 Enter the name of the package (e.g., @code{prog-modes}), and XEmacs
356 will search for the latest version and install it and any packages that
359 @node Which Packages, Removing Packages, Automatically, Installing Packages
360 @comment node-name, next, previous, up
361 @cindex which packages
362 @cindex choosing packages
363 @heading Which Packages to Install:
364 This is difficult to say. When in doubt install a package. If you
365 administrate a big site it might be a good idea to just install
366 everything. A good minimal set of packages for XEmacs-latin1 would be
368 xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs,
369 edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes,
372 If you are using the XEmacs package tools, don't forget to do:
374 Packages -> Add Required
376 To make sure you have everything that the packages you have chosen to
379 See also @ref{Available Packages} for further descriptions of the individual
382 @node Removing Packages, ,Which Packages, Installing Packages
383 @comment node-name, next, previous, up
384 @cindex removing packages
385 @cindex deleting packages
386 @heading Removing Packages:
387 Because the exact files and their locations contained in a package may
388 change it is recommended to remove a package first before installing a
389 new version. In order to facilitate removal each package contains an
390 @file{pgkinfo/MANIFEST.pkgname} file which list all the files belonging
393 No need to panic, you don't have to go through the
394 @file{pkinfo/MANIFEST.pkgname} and manually delete the files. Instead, use
395 @code{M-x package-admin-delete-binary-package RET}.
397 Note that the interactive package tools included with XEmacs already do
400 @node Building Packages, Local.rules File, Installing Packages, Packages
401 @comment node-name, next, previous, up
402 @cindex building packages
403 @cindex package building
404 @heading Building Packages:
405 Currently, source packages are only available via anonymous CVS. See
406 @url{http://cvs.xemacs.org/} for details of checking out the
407 @file{xemacs-packages} module.
409 @subsection Prerequisites for Building Source Packages
414 (or a BSD compatible install program).
416 (3.75 or later preferred).
418 (1.68 from texinfo-3.11 or later required).
423 @item A properly configured @file{Local.rules} file.
424 @ref{Local.rules File}.
426 And of course, XEmacs 21.0 or higher.
428 @subsection What You Can Do With Source Packages
430 The packages CVS sources are most useful for creating XEmacs package
431 tarballs for installation into your own XEmacs installations or for
432 distributing to others.
434 Supported operations from @file{make} are:
438 Bytecompile all files, build and bytecompile byproduct files like
439 @file{auto-autoloads.el} and @file{custom-load.el}. Create info version
440 of TeXinfo documentation if present.
443 Does a @code{make all} as well as create a binary package tarball in the
447 Bytecompile all files, build and bytecompile byproduct files like
448 @file{auto-autoloads.el} and @file{custom-load.el}. Create info version
449 of TeXinfo documentation if present. And install everything into the
453 Usually aliased to @code{srckit-std}. This does a @code{make
454 distclean} and creates a package source tarball in the staging
455 directory. This is generally only of use for package maintainers.
458 May be aliased to @code{binkit-sourceonly}, @code{binkit-sourceinfo},
459 @code{binkit-sourcedata}, or
460 @code{binkit-sourcedatainfo}. @code{sourceonly} indicates there is
461 nothing to install in a data directory or info directory.
462 @code{sourceinfo} indicates that source and info files are to be
463 installed. @code{sourcedata} indicates that source and etc (data) files
464 are to be installed. @code{sourcedatainfo} indicates source, etc
465 (data), and info files are to be installed. A few packages have needs
466 beyond the basic templates so this is not yet complete.
469 Runs the rules @code{srckit} followed by @code{binkit}. This is
470 primarily of use by XEmacs maintainers producing files for distribution.
473 Remove all built files except @file{auto-autoloads.el} and @file{custom-load.el}.
476 Remove all created files.
479 @node Local.rules File, Creating Packages, Building Packages, Packages
480 @comment node-name, next, previous, up
482 @heading The Local.rules File:
483 This file is used when building and installing packages from source. In
484 the top level of the CVS module, @file{xemacs-packages}, contains the
485 file, @file{Local.rules.template}. Simply copy that to
486 @file{Local.rules} and edit it to suit your needs.
488 These are the variables in 'Local.rules' that you will need to
493 Set this to 't' if you want to do a "run in place".
494 Setting this doesn't work well with 'make bindist'
496 @item XEMACS_PACKAGES =
497 This is where you set the normal packages that you
500 XEMACS_PACKAGES = xemacs-packages/xemacs-base xemacs-packages/bbdb
503 @item XEMACS_STAGING = $@{XEMACS_PACKAGES_BASE@}/../Packages
504 Set this to where you want normal packages to be
507 @item PACKAGE_INDEX = package-index
508 If you want the package-index file to have a different
511 @item BUILD_WITHOUT_MULE =
512 Building from CVS defaults to building the Mule
513 packages. Set this to 't' if you don't want/have Mule
515 @item MULE_PACKAGES =
516 Same as for 'XEMACS_PACKAGES' except you list the Mule
517 packages you want to install here. eg:
519 MULE_PACKAGES = mule-packages/mule-base mule-packages/skk
522 @item MULE_STAGING = $@{XEMACS_PACKAGES_BASE@}/../Mule-Packages
523 Set this to where you want Mule packages installed
524 to. Note: 'make bindist' does not use this variable.
526 @item XEMACS = xemacs
527 If your XEmacs isn't in your path, change this.
529 @item XEMACS_NATIVE_NT =
530 Set this to 't' if you are building on WinNT.
532 @item INSTALL = install -c
533 The path to your BSD compatible install program.
536 The path to your tar program
539 If you want bzip2 tarballs, set this.
541 @item MAKEINFO = makeinfo
542 The path to your makeinfo program
546 @node Creating Packages, Available Packages, Local.rules File, Packages
547 @comment node-name, next, previous, up
548 @cindex creating packages
549 @heading Creating Packages:
550 Creating a package from an existing Lisp library is not very difficult.
552 In addition to the Lisp libraries themselves, you need a
553 @file{package-info.in} file and a simple @file{Makefile}. The rest is
554 done by @file{XEmacs.rules}, part of the packaging system
557 @file{package-info.in} contains a single Lisp form like this:
560 (name ; your package's name
561 (standards-version 1.1
563 author-version AUTHOR_VERSION
565 build-date BUILD_DATE
566 maintainer MAINTAINER
567 distribution xemacs ; change to "mule" if MULE is needed
571 description "description" ; a one-line description string
575 provides (feature1 feature2) ; one for every `provides' form
581 You must fill in the four commented lines. The value of @code{name} is
582 the name of your package as an unquoted symbol. Normally it is the name
583 of the main Lisp file or principal feature provided. The allowed values
584 for distribution are @code{xemacs} and @code{mule}. Write them as
585 unquoted symbols. The @code{description} is a quoted Lisp string; use
586 the usual conventions. The value for @code{provides} is a list of
587 feature symbols (written unquoted). All of the features provided by
588 libraries in your package should be elements of this list. Implementing
589 an automatic method for generating the @file{provides} line is
590 desirable, but as yet undone.
592 The variables in upper-case are references to variables set in the
593 @file{Makefile} or automatically generated. Do not change them; they
594 are automatically filled in by the build process.
596 The remaining lines refer to implementation constants
597 (@code{standards-version}), or features that are unimplemented or have
598 been removed (@code{priority} and @code{dump}). The @code{type} line is
599 not normally relevant to external maintainers; the alternate value is
600 @code{single-file}, which refers to packages consed up out of a number
601 of single-file libraries that are more or less thematically related. An
602 example is @code{prog-modes}. Single-file packages are basically for
603 administrative convenience, and new packages should generally be created
606 The @file{Makefile} is quite stylized. The idea is similar to an
607 @file{Imakefile} or an @code{automake} file: the complexity is hidden in
608 generic rules files, in this case the @file{XEmacs.rules} include file
609 in the top directory of the packages hierarchy. Although a number of
610 facilities are available for complex libraries, most simple packages'
611 @file{Makefile}s contain a copyright notice, a few variable definitions,
612 an include for @file{XEmacs.rules}, and a couple of standard targets.
614 The first few @code{make} variables defined are @code{VERSION},
615 @code{AUTHOR_VERSION}, @code{MAINTAINER}, @code{PACKAGE},
616 @code{PKG_TYPE}, @code{REQUIRES}, and @code{CATEGORY}. All but one were
617 described in the description of @file{package-info.in}. The last is an
618 administrative grouping. Current categories include @code{standard},
621 Next, define the variable @code{ELCS}. This contains the list of the
622 byte-compiled Lisp files used by the package. These files and their
623 @file{.el} versions will be included in the binary package. If there
624 are other files (such as extra Lisp sources or an upstream
625 @file{Makefile}) that are normally placed in the installed Lisp
626 directory, but not byte-compiled, they can be listed as the value of
627 @code{EXTRA_SOURCES}.
629 The include is simply
631 include ../../XEmacs.rules
634 The standard targets follow. These are
637 all:: $(ELCS) auto-autoloads.elc
644 Other targets (such as Texinfo sources) may need to be added as
645 dependencies for the @code{all} target. Dependencies for @code{srckit}
646 and @code{binkit} (that is, values for @var{srckit-alias} and
647 @var{binkit-alias}) are defined in @file{XEmacs.rules}. The most useful
648 of these values are given in the following table.
652 Usually set to @code{srckit-std}.
655 May be set to @code{binkit-sourceonly}, @code{binkit-sourceinfo},
656 @code{binkit-sourcedata}, or
657 @code{binkit-sourcedatainfo}. @code{sourceonly} indicates there is
658 nothing to install in a data directory or info directory.
659 @code{sourceinfo} indicates that source and info files are to be
660 installed. @code{sourcedata} indicates that source and etc (data) files
661 are to be installed. @code{sourcedatainfo} indicates source, etc
662 (data), and info files are to be installed.
665 Data files include things like pixmaps for a package-specific toolbar,
666 and are normally installed in @file{etc/@var{PACKAGE_NAME}}. A few
667 packages have needs beyond the basic templates. See @file{XEmacs.rules}
668 or a future revision of this manual for details.
670 @node Available Packages, , Creating Packages, Packages
671 @comment node-name, next, previous, up
672 @cindex available packages
674 @heading Available Packages:
675 This section lists the Lisp packages that are currently available from
676 xemacs.org and it's mirrors. If a particular package that you are
677 looking for isn't here, please send a message to the
678 @email{xemacs-beta@@xemacs.org, XEmacs Beta list}.
680 This data is up-to-date as of May 15, 2001.
682 @subsection Normal Packages
683 A very broad selection of elisp packages.
687 Support for Sparcworks.
690 Ada language support.
693 A Portable Emacs Library. Used by XEmacs MIME support.
696 Basic TeX/LaTeX support.
699 The Big Brother Data Base
702 Build XEmacs using custom widgets.
705 Basic single-file add-ons for editing C code.
711 Calendar and diary support.
714 C, C++ and Java language support.
717 Spook and Yow (Zippy quotes).
720 Crisp/Brief emulation.
723 GUD, gdb, dbx debugging support.
726 The DIRectory EDitor is for manipulating, and running commands on
727 files in a directory.
733 Interface over patch.
736 Single file lisp packages for various XEmacs goodies. Load this and
737 weed out the junk you don't want.
740 DEC EDIT/EDT emulation.
743 Treat files on remote systems the same as local files.
746 ICQ Client developed and tested on Linux x86;
747 only supported on that platform
750 Enhanced Implementation of Emacs Interpreted Objects.
753 Portable Emacs Lisp utilities library.
756 Another interface over patch.
759 Command shell implemented entirely in Emacs Lisp.
765 Emacs Unified Directory Client (LDAP, PH).
768 Footnoting in mail message editing modes.
771 Forms editing support (obsolete, use the built-in Widget instead).
774 Provide a WM icon based on major mode.
777 FSF Emacs compatibility files.
780 Tetris, Sokoban, and Snake.
786 The Gnus Newsreader and Mailreader.
792 Editing and Shell mode for the Interactive Data Language.
795 Enhanced front-end for Grep.
798 Front-end for Inferior Lisp.
801 Spell-checking with ispell.
804 Java language and development support.
807 Fundamental lisp files for providing email support.
810 Support for messaging encryption with PGP.
813 Messaging in an Emacs World.
816 Front end support for MH.
822 Other amusements and diversions.
825 Miscellaneous Networking Utilities. This is a single-file package and
826 files may be deleted at will.
829 Miscellaneous single-file O/S utilities, for printing, archiving,
830 compression, remote shells, etc.
833 PC style interface emulation.
839 Provides programmatic completion.
842 Miscellaneous single-file lisp files for various programming languages.
844 @item ps-print-nomule
845 Old, but no-Mule safe ps-print.
848 Validated HTML/SGML editing.
851 Emacs support for LaTeX cross-references, citations.
854 An obsolete Emacs mailer. If you do not already use it don't start.
857 Front-end support for Inferior Scheme.
863 SGML/Linuxdoc-SGML editing.
866 Support for editing shell scripts.
872 XEmacs Sun sound files.
875 XEmacs Microsoft sound files.
878 Provides a separate frame with convenient references.
881 Mouse enhancement utility.
884 An Emacs citation tool. Useful with all Emacs Mailers and Newsreaders.
887 XEmacs TeXinfo support.
890 Various single file lisp packages for editing text files.
893 Single-file TeX support.
896 Display time & date on the modeline.
899 Emacs MIME support. Not needed for Gnus >= 5.8.0
902 Support for building with Tooltalk.
905 DEC EDIT/TPU support.
908 Version Control for Free systems.
911 Version Control for ClearCase. This package will shortly be
912 replaced with clearcase.el
918 A Unix process browsing tool.
921 VI emulation support.
930 Fundamental XEmacs support. Install this unless you wish a totally
934 XEmacs Lisp developer support. This package contains utilities for
935 supporting Lisp development. It is a single-file package so it may be
939 A minor mode for (X)Emacs which allows running an XSLT processor on a
946 @subsection Mule Support (mule)
948 MULti-lingual Enhancement. Support for world scripts such as
949 Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc.
950 To use these packages your XEmacs must be compiled with Mule
955 Lisp Interface to EDICT, Kanji Dictionary.
958 Wnn (4.2 and 6) support. SJ3 support. Must be installed prior to
962 Quail. Used for everything other than English and Japanese.
965 Used for localized menubars (French and Japanese) and localized splash
969 Dictionary support. (This isn't an English dictionary program)
972 Basic Mule support. Must be installed prior to building with Mule.
975 Another Japanese Language Input Method. Can be used without a
976 separate process running as a dictionary server.