Font dropdown not reading an SHX font

[honkinberry]

I use a hidden Font dropdown box to read a list of available SHX fonts installed.
Works pretty sweet, except for this attached bugger!  It will show up in the AutoCAD Text Styles dialog, but not in the OpenDCL Font dropdown.  Any idea why?

As always, thanks for such an incredible product.

--J

[honkinberry]

And here's another one.
Very odd in that just like the other one, it shows up for use in the AutoCAD Text Styles dialog, but the OpenDCL Font dropdown doesn't include it.

--J

[owenwengerd]

The reason is that the files are shape files, not font files. It looks like AutoCAD lists shape files if the shapes can be interpreted as characters like a regular font file. Not all shape files can work as character fonts (for example, genltshp.shx is *not* listed in the STYLE dropdown even though it is also a shape file.) Unfortunately I don't see any easy way to distinguish without at least decompiling the .shx file. You can always open the .shx file in Notepad and change AutoCAD-86 shapes 1.0 to AutoCAD-86 unifont 1.0, then it will work the same everywhere.

[honkinberry]

Ah I see, there you go, thank you for that!
I have not had any luck in just replacing the header.  In reading up on it, and trying to manually decompile and recompile there, it seems there is a bit of unicode conversion necessary (adjusting the byte count whenever a 7 code is used, whatever that means!).
And then I'm finding that a good number of these legacy SHX files sitting around are all these old shape files -- it's far more widespread than just these two isolated incidents.  Like these oft-used Architect style fonts (http://cadtrainerguy.com/how-i-work/downloads-for-autocad/), and on and on, it seems it's just far too likely that people have some crazy old SHX file that's been around since the firm's inception.
So... easier solution -- I'm just using vl-directory-files to manually grab the SHX files in the support folders, and manually add them.

Thanks again!

--J

[owenwengerd]

I'm glad that you've found a suitable workaround. Now that we've solved the mystery, please delete the attachments on your first two posts in this thread, as both appear to be posted without permission of the copyright holder.