Package Details: ttf-ms-win11 10.0.22621.608-1

Git Clone URL: (read-only, click to copy)
Package Base: ttf-ms-win11
Description: Microsoft Windows 11 TrueType fonts
Upstream URL:
Licenses: custom
Conflicts: ttf-ms-fonts, ttf-tahoma, ttf-vista-fonts
Provides: emoji-font, ttf-font, ttf-ms-fonts, ttf-tahoma
Submitter: Vaporeon
Maintainer: Vaporeon
Last Packager: Vaporeon
Votes: 19
Popularity: 1.23
First Submitted: 2021-10-11 13:33 (UTC)
Last Updated: 2022-10-11 15:19 (UTC)

Dependencies (0)

Required by (289)

Sources (144)

Pinned Comments

Vaporeon commented on 2021-12-08 12:35 (UTC) (edited on 2021-12-08 12:43 (UTC) by Vaporeon)

If you wish to build the package using fonts from the ISO, run git checkout 5ba5194a795c71999d16510aeb4a24ecbc8d1782 after cloning the AUR package repo.

This will revert the PKGBUILD to match the font versions used in the release ISO.

The master branch HEAD tracks the font versions installed in an up-to-date live install and requires those fonts to be used as the source.

Latest Comments

1 2 3 Next › Last »

Scimmia commented on 2022-09-21 12:49 (UTC)

You could make an argument for splitting almost anything. If you start splitting individual fonts, it'll never end.

Vaporeon commented on 2022-09-20 23:09 (UTC)

If it is really desired that I split it I can.

Vaporeon commented on 2022-09-20 23:07 (UTC)

Instead of splitting it I made the base package provide emoji-font.

gbr commented on 2022-09-18 06:28 (UTC)

May I suggest something? Create a sub-package just for Segoe UI Emoji and name it ttf-ms-win11-emoji. Also, on the provides=() array, add emoji-font. This will prevent having to install yet another emoji font (e.g. noto-fonts-emoji or ttf-joypixels) when installing programs like gnome-characters. Thank you!

Un1Gfn commented on 2022-05-08 09:39 (UTC) (edited on 2022-05-08 09:40 (UTC) by Un1Gfn)

I have the following installed (ttf-ms-win11-zh_cn)


Why do I get SimSun (substitution with Noto Sans CJK SC) in okular>File>Properties>Fonts and ugly text?

Vaporeon commented on 2022-03-15 18:49 (UTC) (edited on 2022-03-15 18:49 (UTC) by Vaporeon)

Un1Gfn: See the pinned comment in regards to building using the ISO fonts. The current package version always assumes an up to date live install.

When using other font versions you have two options. 1: check out the package at a version that matches the fonts you currently have. doing this means pkgver will properly match the versions of the fonts you have. -or- 2: skip checksum verification to force the current version to build with your current font files (as you have done).

Un1Gfn commented on 2022-03-14 05:28 (UTC) (edited on 2022-03-18 07:37 (UTC) by Un1Gfn)

build failure

==> Validating source files with sha256sums...
    seguibli.ttf ... Passed
    seguiemj.ttf ... FAILED
    seguihis.ttf ... Passed

ttf-ms-win11 10.0.22000.348-1

Win11_English_x64v1.iso sha256=4bc6c7e7c61af4b5d1b086c5d279947357cff45c2f82021bb58628c2503eb64e

I changed the sha256sum of seguiemj.ttf from edd76b88c44432ba1818992259c31d45abd28fbcfbb3eeebad3f6af27636213c to SKIP, and got a successful build.

Edit: Sorry I didn't read the pinned comment carefully. Got it now. Thanks.

Vaporeon commented on 2021-12-08 13:25 (UTC)

As said already this package tracks the fonts that are commonly installed across ALL versions of Windows 11. See [1] for the font list. Fonts that acquired using FOD (Feature On Demand) or that are only present on some installation media are excluded. The reason for this is that it is considered unreasonable to expect everyone obtain all of these font files in order to be able to build this package.

If you consider one or more of these optional fonts to be "essential", then that it is an issue to be taken with Microsoft. They made the distinction, not us.