Windows 10 converges the Windows platform for use across multiple device categories. The description above of previous releases applies to Windows Client (desktop) and Server editions. This section on Windows 10 covers all Windows 10 editions, including Desktop, Server and Mobile.
All Windows 10 editions support the same set of scripts. In addition to the scripts supported in earlier Windows releases, Windows 10 adds support for several additional, historic scripts. These are supported using the new Segoe UI Historic font:
New scripts Region where script is from Fonts Comments on language usage
Brahmi Indian subcontinent Segoe UI Historic Historic
Carian Europe Segoe UI Historic Historic
Cypriot Europe Segoe UI Historic Historic
Egyptian Hieroglyphs Middle East Segoe UI Historic Historic
Imperial Aramaic Middle East Segoe UI Historic Historic
Inscriptional Pahlavi Middle East Segoe UI Historic Historic
Inscriptional Parthian Middle East Segoe UI Historic Historic
Kharoshthi Indian subcontinent Segoe UI Historic Historic
Lycian Europe Segoe UI Historic Historic
Lydian Europie Segoe UI Historic Historic
Phoenician Middle East Segoe UI Historic Historic
Old Persian Cuneiform Middle East Segoe UI Historic Historic
Old South Arabian Middle East Segoe UI Historic Historic
Shavian Europe Segoe UI Historic English phonetic writing
Sumero-Akkadian Cuneiform Middle East Segoe UI Historic Historic
Ugaritic Cuneiform Middle East Segoe UI Historic Historic
Certain other historic scripts were supported in earlier versions in the Segoe UI Symbol font. In order to avoid duplication, the following scripts have been removed from Segoe UI Symbol and included in Segoe UI Historic:
In Windows 8.1, the Meiryo UI font family was used for Japanese text in the Windows user interface. On Windows Phone 8.1, the popular Yu Gothic font was used for Japanese. In Windows 10, the user interface font family for Japanese has changed to Yu Gothic UI for all editions. In order to make Yu Gothic UI perform as intended in Windows UI, Yu Gothic UI is adapted from Yu Gothic with certain metric and character width modifications as well as alternate glyphs for Latin characters. For non-UI content, the Yu Gothic fonts are still included. For optimal readability, the OpenType “palt” feature (proportional alternate widths) should be enabled for text formatted with Yu Gothic.
Another change pertaining to user interface fonts is that a semilight weight has been added to the Malgun Gothic family. Otherwise, user interface fonts for other languages are the same as in Windows 8.1.
In Windows 8 and Windows 8.1, private-use-characters in the Segoe UI Symbol font were used for user interface iconography. In Windows 10, the Segoe MDL2 Assets font has been added to provide newer iconography.
An important development in Windows 10 is the Universal Windows Platform (UWP): a converged app platform allowing a developer to create a single app that can run on all Windows devices. Windows fonts are one aspect of this convergence: Windows 10 introduces a recommended UWP font set that is common across all editions that support UWP, including Desktop, Server, Mobile and Xbox.
For information regarding which fonts are included in the recommended UWP font set, complete details are provided in Guidelines for fonts. One important point to note is that the recommended font set does not include all of the weights for certain font families. In particular, due to the large size of East Asian fonts, only the regular weight of East Asian font families are included in the recommended font set.
A number of additional fonts are available for Desktop and Server, including all other fonts from previous releases. However, not all of these are pre-installed by default in all images. In order to make disk usage and font choices more relevant to users according the languages that they use, a number of fonts have been moved into optional on-demand packages. These packages are designed around the different scripts that fonts are primarily intended to support, and most are installed automatically by Windows Update when the associated languages are enabled in language settings (for example, by enabling a keyboard).
Any of these optional font packages can also be installed manually by any user in Settings. One package is not triggered automatically but can be added by enabling it in Settings. To add font packages manually, go to Settings > System > Installed apps > Manage optional features.
The following are the optional font packages that are automatically installed based on changes to language settings:
Arabic Script Supplemental Fonts
Bangla Script Supplemental Fonts
Canadian Aboriginal Syllabics Supplemental Fonts
Cherokee Supplemental Fonts
Chinese (Simplified) Supplemental Fonts
Chinese (Traditional) Supplemental Fonts
Devanagari Supplemental Fonts
Ethiopic Supplemental Fonts
Gujarati Supplemental Fonts
Gurmukhi Supplemental Fonts
Hebrew Supplemental Fonts
Japanese Supplemental Fonts
Khmer Supplemental Fonts
Kannada Supplemental Fonts
Korean Supplemental Fonts
Lao Supplemental Fonts
Malayalam Supplemental Fonts
Odia Supplemental Fonts
Sinhala Supplemental Fonts
Syriac Supplemental Fonts
Tamil Supplemental Fonts
Telugu Supplemental Fonts
Thai Supplemental Fonts
The following optional font package must be installed manually:
Pan-European Supplemental Fonts
Note: These optional packages are for Desktop and Server editions only.
Moving these fonts into optional packages provides over 220 MB of disk savings for users who don’t require these fonts.
Another significant development in Windows 10 from an international perspective is the introduction of a new complex-script shaping engine — the Universal Shaping Engine — that allows any complex script in Unicode 7.0 to be shaped correctly even if the script is not yet supported by a system-provided font. Users have the option to install a suitable OpenType font to get correct shaping behavior for any script in Unicode 7.0.
Note: While the Windows platform is able to support display of additional Unicode 7.0 scripts using non-system fonts, this doesn’t not guarantee that this will work in all apps. In particular, apps that do their own low-level text-display processing may not display a script correctly unless they were explicitly designed to support that script, even though they call platform APIs that use the universal shaping engine. Also note that platform frameworks will not provide font fallback behavior using non-system fonts.
The following complex scripts in Unicode 7.0 are supported in the Universal Shaping Engine.
Balinese, Batak, Brahmi, Buginese, Buhid, Chakma, Cham, Duployan, Egyptian Hieroglyphs, Grantha, Hanunoo, Javanese, Kaithi, Kayah Li, Kharoshthi, Khojki, Khudawadi, Lepcha, Limbu, Mahajani, Mandaic, Manichaean, Meitei Mayek, Modi, Mongolian, N’Ko, Pahawh Hmong, Phags-pa, Psalter Pahlavi, Rejang, Saurashtra, Sharada, Siddham, Sinhala, Sundanese, Syloti Nagri, Tagalog, Tagbanwa, Tai Le, Tai Tham, Tai Viet, Takri, Tibetan, Tifinagh, Tirhuta
Other scripts in Unicode 7.0 either are supported in other shaping engines or do not require complex script handling.
For more background on the Universal Shaping Engine, see Windows shapes the world’s languages.
Edited by Drew1903, 08 May 2015 - 06:06 PM.