Identify the shell font for the relevant language
Microsoft’s logical-font documentation identifies MS Sans Serif for the English United States Windows 98 shell, MS Sans Serif Greek for the Greek edition and MS UI Gothic for Japanese. These examples show why a single English screenshot cannot identify every localized installation. Record the edition and the actual object—menu, dialog or document—before choosing a comparison. Do not silently replace MS Sans Serif with a similarly named family.
Understand a logical name before treating it as a file
The same Microsoft account explains MS Shell Dlg as a logical mapping to an appropriate shell font. MS Shell Dlg 2 was introduced for the Windows 2000 look. A logical face name therefore should not be mistaken for one fixed font file shared across all operating-system versions. For a historical reference sheet, keep the requested logical name, resolved family and system context in separate fields. An application can select its own document font independently of a dialog’s mapped interface text.
Compose a retro interface with real labels
For an original retro-interface illustration, prepare a title bar, two buttons, a short menu and a message containing numbers. Match each text role to its reference rather than using one decorative pixel alphabet everywhere. Keep a clean text source and compare the label lengths at the intended output size before drawing the surrounding controls. The Tahoma guide is a separate UI-family study, not proof that every Windows 98 shell used it. The homepage’s text-style generator makes Unicode substitutions; it does not change a system font, resolve logical mappings or reproduce a historical renderer.
Your questions, answered.
Did every language edition of Windows 98 use the same shell font?
Microsoft documents different examples for English, Greek and Japanese editions.
Is MS Shell Dlg always the name of one physical font file?
No. It is a logical mapping used to select the appropriate family in its system context.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.