[dvipdfmx] Invalid font: -1 (0) error message is opaque

[Karl Berry]

I suggest that it would be nice if the error message
  xdvipdfmx:fatal: Invalid font: -1 (0)

could be improved to describe the actual error, like (I guess?)
  "Type 1 font (/where/ever/foo.pfb) found when OTF/TTF expected"

For the whole thread, see
https://tug.org/pipermail/texhax/2021-September/025322.html

Thanks,
Karl

-------------------------------------------------------------------------
On Tue, Sep 21, 2021 at 7:17 PM David Carlisle <d.p.carlisle at gmail.com>
wrote:

> what do you get without the grep opentype?  the xdvipdfmx error (I
> think) is telling you that it picked up a non opentype font that;s why
> I recommend not including the type1 line that is in the fontconfig
> file distributed with texlive
>
> On Tue, 21 Sept 2021 at 23:49, Bob Tennent <rdtennent at gmail.com> wrote:
> >
> > I did this and now
> >    %  fc-list | grep 'CMU Concrete' | grep opentype
> > lists the four otf fonts,
> > but I'm still getting
> >
> >    xdvipdfmx:fatal: Invalid font: -1 (0)
> >
> > using xelatex.