Usually maps to Tahoma (on older systems) or Segoe UI (on modern systems). It was introduced to better support Unicode and a wider range of international characters. Where Does it Live?
This tells Windows to use the mapped physical font for the dialog. ms shell dlg 2
If you hardcode your application to use "Segoe UI" and run it on Windows XP (which does not have Segoe UI by default), the font will fail to load, and the system will fall back to something like Arial, looking unprofessional. If you use MS Shell Dlg 2 , Windows XP will automatically map it to Tahoma (the appropriate font for that era), while Windows 11 will map it to Segoe UI. The application automatically adapts to the OS environment. Usually maps to Tahoma (on older systems) or
| Logical Font | Mapped to (English Windows) | |--------------|-----------------------------| | MS Shell Dlg | Microsoft Sans Serif | | MS Shell Dlg 2 | Tahoma | This tells Windows to use the mapped physical
It remains a staple of backward compatibility and forward-looking design in the Windows ecosystem.
| Feature | MS Shell Dlg | MS Shell Dlg 2 | | :--- | :--- | :--- | | | Windows 95 / NT 4.0 | Windows XP | | Current Mapping (Win 10/11) | Microsoft Sans Serif (often treated as legacy) | Segoe UI | | Legacy Mapping (Win XP) | Tahoma | Tahoma | | Recommended Use | Legacy applications only. | Modern applications (WinForms, WPF, Win32). | | Visual Style | Slightly older, "classic" Windows look. | Sleek, modern, matches current Windows aesthetic. |