It works the other way around. In a Word document, some basic information
about the fonts used by that document is stored (panose1, pitch,
font-family, ...). Based on that information it is (theoretically) possible
to decide if a missing font was a font with serifs or not.
I do not know if Word has its own font substitution logic, but normally
that's the task of the OS. In Windows, the substitution rules are stored
inside the registry. For example, there is the mapping of each font-family
onto a 'basic' font (Arial, TNR, Courier New, ...).
The Garamond font belongs to the "roman" family, which uses TNR as its
fallback font.
Yves
How would it know serif from sans serif? It would have to have a list
of all possible font names to know that!
When I installed Adobe CS4 Design Standard, it crammed my fonts folder
with fonts I don't need -- six ACaslons, four AGaramondPros, and who
knows how many farther down the alphabet -- without, AFAICT, any
option to not install the fonts in a Custom installation.