On Mac Classic, if you wanted to ship a custom font with your application, you&#x27;d put it in the Resource fork in a resource of &quot;FONT&quot; type.<p>So why wouldn&#x27;t a stand-alone font file consist of a Resource fork with a single resource of &quot;FONT&quot; type? Otherwise, the OS engineers have to develop two entirely different ways of reading in font data. Why duplicate the effort?<p>The system made perfect sense, both then and now. It bothers me that so few people know anything about Mac Classic, it really was an amazingly well-designed OS for its time.