Hi, some people probably know my X-Symbol package (semi WYSIWYG for LaTeX, HTML, etc), http://www.fmi.uni-passau.de/~wedler/x-symbol/ I now started to make it a proper XEmacs package. I would appreciate if you could test my first attempt (obviously the second ;-) http://www.fmi.uni-passau.de/~wedler/x-symbol/x-symbol-0.02-pkg.tar.gz http://www.fmi.uni-passau.de/~wedler/x-symbol/x-symbol-0.02-src.tar.gz It uses the XEmacs.rules, modified by Jan Vroonhof for his toolbar-fancy. Thanks to Jan for all his explanations about XEmacs packages. I would appreciate to get comments concerning (1) The directory structure: * X-Symbol uses additional fonts: bin: etc/x-symbol/{fonts,origfonts,pcf}, src: x-symbol/{fonts,origfonts,pcf} * X-Symbol creates executables from its lisp code and variables via flex & cc. The proposed directory for these executables is etc/x-symbol/bin/SYSTEM-CONFIGURATION/ Is this consistent with XEmacs' standards? (2) My makeinfo-1.68 adds spurious spaces when called with option `-o' and a file name other than the original one. If this is specific here on my system, I should probably change the Makefile... (3) Package X-Symbol has two special lisp files: one is only used (and compilable) when used with XEmacs/Mule, the other only with XEmacs/no-Mule. How should I built the binary package? Currently, x-symbol-mule.el (or x-symbol-nomule.el) belongs to EXTRA_SOURCES. Or should I make x-symbol-nomule.el compilabe (but not runnable) under XEmacs/Mule and create the binary package with XEmacs/Mule? (4) You probably know that cus-dep.el is buggy (when defining an own custom-set function). I'd rather avoid special work-arounds like Jan did in his toolbar-fancy... Any suggestion is welcome! - Christoph