Re: elisp-packages, mule and non-mule?

nix> I'm happy to have support for it *there*, but if it means that my nix> XEmacs size in core grows even larger, or that I have to use disk nix> space on huge Unicode tables for character sets I don't have nix> fonts for and can't even read, well, no thanks. Well I was hoping for some hard facts here like how much bigger it will get. Once in a while elisp developers seems to forget that their code should work both for mule and non-mule (if that even is feasible) and subtle bugs occur. If the non-mule version is dropped I guess these problems would go away. So I was curios about what consequences it would have to drop non mule. Footprint is one thing (I can probably check that myself just by building both versions) but there might be other considerations as well. Yours -- %% Mats