5 ms·

> That way I can see actual fonts, font sizes and layout to confirm how the document should have looked. Or you would if you had the original fonts. Word 4.0 w

> That way I can see actual fonts, font sizes and layout to confirm how the document should have looked. Or you would if you had the original fonts. Word 4.0 was released for System 6 with support as far back as System 3.2. Fonts at that time had separate screen and printer files for the different output resolutions. If you're missing the printer font it'll print a scaled (using nearest-neighbor) rendering of the screen font. If you're missing the screen font it'll substitute the system font. (Geneva by default, as seen in the screenshot.) In this case, only the well-known Palatino and Courier typefaces are needed. But LibreOffice substituted Times New Roman even though I have Palatino Linotype installed.

jgrahamc 3y ago
That may go some way to explaining some of the differences I see, but the main thing I was looking for in the emulation was the font sizes.
- aidenn0 3y ago
  Doesn't the font matter almost as much as the font-size setting for font sizes, given that different font families can have wildly different metrics at the same font size?
  - jgrahamc 3y ago
    I bet it does. I should redo the final part after installing the required fonts.
jasomill 3y ago
This is probably because the (internal) name of Palatino Linotype is "PalatinoLinotype" (for the version shipped with Windows) or "PalatinoLTStd" (for the Adobe OpenType version). In the absence of a hard-coded special case, font matching based on common prefixes could easily match something inappropriate, such as — taking the first example I see on my machine — mapping "Lucida" to "LucidaConsole", when almost any proportional sans-serif font would arguably be a better match for the document author's design intent. Then again, even exact name matches provide no guarantees. For example, Apple has shipped two fonts (internally) named NewYork: the TrueType conversion of Susan Kare's 1983 bitmap design for the original Macintosh, and an unrelated design released in 2019.
- whoopdedo 3y ago
  It's more that I half-expected well-known mappings to be baked in. Like "Times" -> "Times New Roman". Didn't they also name one of their new fonts "SanFrancisco" much to the ire of Susan Kare fans.
  - jasomill 3y ago
    Yes, but the current OpenType San Francisco fonts use "SF" in their (display and internal) names, so no naming conflict exists with the original "ransom note" bitmap font. Also, as far as I know, of the original Mac fonts, Apple only ever shipped TrueType versions of Chicago, Geneva, Monaco, and New York. And I'm not aware of any OS with native support for both OpenType and classic Mac bitmap fonts (conversions are always possible, of course).

jgrahamc 3y ago

That may go some way to explaining some of the differences I see, but the main thing I was looking for in the emulation was the font sizes.

aidenn0 3y ago
Doesn't the font matter almost as much as the font-size setting for font sizes, given that different font families can have wildly different metrics at the same font size?
- jgrahamc 3y ago
  I bet it does. I should redo the final part after installing the required fonts.

jasomill 3y ago

This is probably because the (internal) name of Palatino Linotype is "PalatinoLinotype" (for the version shipped with Windows) or "PalatinoLTStd" (for the Adobe OpenType version). In the absence of a hard-coded special case, font matching based on common prefixes could easily match something inappropriate, such as — taking the first example I see on my machine — mapping "Lucida" to "LucidaConsole", when almost any proportional sans-serif font would arguably be a better match for the document author's design intent. Then again, even exact name matches provide no guarantees. For example, Apple has shipped two fonts (internally) named NewYork: the TrueType conversion of Susan Kare's 1983 bitmap design for the original Macintosh, and an unrelated design released in 2019.

whoopdedo 3y ago
It's more that I half-expected well-known mappings to be baked in. Like "Times" -> "Times New Roman". Didn't they also name one of their new fonts "SanFrancisco" much to the ire of Susan Kare fans.
- jasomill 3y ago
  Yes, but the current OpenType San Francisco fonts use "SF" in their (display and internal) names, so no naming conflict exists with the original "ransom note" bitmap font. Also, as far as I know, of the original Mac fonts, Apple only ever shipped TrueType versions of Chicago, Geneva, Monaco, and New York. And I'm not aware of any OS with native support for both OpenType and classic Mac bitmap fonts (conversions are always possible, of course).