Currently, enscript(1) doesn't support Defoma-managed fonts for
	--font, since being registered within Defoma doesn't imply that:

	* there'll be an AFM file;

	* the file will be linked to /usr/share/enscript/afm/;

	* mkafmmap(1) will be ran.

	It seems to me that the most simple solution would be to provide
	a Defoma script (for /usr/share/defoma/scripts/), to symlink AFM
	files as they're installed, or to use the `ttf2afm' utility
	(provided by `texlive-font-utils') for .ttf files.

	Alternatively, it may be worth implementing a generic
	AFM-acquiring hook for enscript (say, an AFMGet: option, with
	value to be passed to popen(3).)  The default will then be to
	run a script, which:

	* will check AFMPath and font.map for a suitable file;

	* if none found, will query Defoma for an AFM file matching
	  given fontname,

	* and as a last resort, will try to find TTF (via Defoma) and
          use the aforementioned `ttf2afm' utility on it.

	(Though Defoma, at the first glance, doesn't seem to fit well
	the two latter tasks.)