Adobe fonts, to be properly identified as fonts, have to have the right header,
for example %!PS-AdobeFont-1.1
This file has a generic PostScript header "%!PS-Adobe-3.0".
so file does nothing wrong: it identifies the file according to the header
closing this: the file is a part of the package "enscript", so you can reassign this to this component, if you think the file format is wrong

(In reply to comment #2)
> matrix.pfa is a type3 font, not a type1.
>
> As such, file(1)’s current output is exactly what is desired from that file.
If file's output does not include "font" the file won't be recognized by apps that rely on libmagic to identify fonts.
Right now labels for font files are:
Clean:
TTF : TrueType font data
TTC : TrueType font collection data
OTF : OpenType font data
Not:
the PS and PCF font labels are a mess but they at least include "font" somewhere" (Though the upper)

But which apps on the system can handle type3 fonts?
They are only useful for embedding in PostScript files, since a full PS interpreter is required to render them.
(There may be some ΤεΧware in the wild which can handle the subset of type3 fonts which dvips will produce from mf bitmaps, but not vector-style type3s.)
As such, the file in question should be handled like any eps file — which is probably why it is declared as eps — rather than like a font.

(In reply to comment #5)
> But which apps on the system can handle type3 fonts?
That's not the point, libmagic should identify files accurately and then apps can decide it they want to process them or not. Pretending a Type3 font is an EPS file does not help.

> Pretending a Type3 font is an EPS file does not help
But that is not what it is doing. The file really *is* an encapsulated postscript file. That the eps contains a ps type3 font is secondary to what it is.
Also, there is no such thing as magic for a ps type3. It is just postscript code. It is really no different that a pattern dictionary.
I presume the bug report was essentially automated based on the file’s .pfa filename extension, but it is really an eps file with a funny name.
Of course, I can only debate.

This bug was not automated but is based on steps that are being automated right now.
If ps3 is really different and not identifiable via magic I suppose this particular bug is really enscript using the pfa extension for eps code.

(In reply to comment #9)
> If ps3 is really different and not identifiable via magic I suppose this
> particular bug is really enscript using the pfa extension for eps code.
I don't like approach like "File has XYZ extension thus it contains ABC content" but I will fix this issue to make your scripts happy.

(In reply to comment #10)
> (In reply to comment #9)
> > If ps3 is really different and not identifiable via magic I suppose this
> > particular bug is really enscript using the pfa extension for eps code.
>
> I don't like approach like "File has XYZ extension thus it contains ABC
> content" but I will fix this issue to make your scripts happy.
It is a matter of consistency with other packages. If many of them used pfa for eps code, I wouldn't bother you with it, but a2ps is pretty much one-of-a-kind here, so it's worth transforming "almost every pfa file in Fedora is a font" to "every pfa file in Fedora is a font" (makes scripts & rpm so much simpler)