Package Base Details: ttf-ms-win10

Git Clone URL: (read-only, click to copy)
Submitter: Bevan
Maintainer: Bevan (Scimmia)
Last Packager: Bevan
Votes: 106
Popularity: 1.21
First Submitted: 2015-08-21 07:39
Last Updated: 2021-02-06 21:55

Pinned Comments

Bevan commented on 2019-04-16 07:36

FAQ, please read before posting:

  1. I get an error that the sources cannot be downloaded: Please read the instructions on the top of the PKGBUILD.

  2. Some fonts are missing in my copy of Windows (e.g., holomdl2, corbel, chandra, ...): It seems that Microsoft distributes some fonts only with some Windows versions. You can just comment out the corresponding line in the PKGBUILD and then build with "makepkg --skipchecksums".

  3. Some fonts have different checksums: We keep the checksums synchronized with our own Windows installations that are regularly updated. Different Windows versions, different ISOs etc. may contain fonts in different versions/variants. Just build the package using "makepkg --skipchecksums".

  4. Why does the version not correspond to the latest Windows 10 build: If fonts have not changes between builds, there is no reason to change the version number of this package.

  5. Why are some fonts (e.g., traditional chinese, japanese etc.) not included here, not even in the corresponding split packages: We currently only include fonts that are installed on a standard Windows installation, without additional feature-on-demand packages (see:

Bevan commented on 2016-08-08 18:05

Please refrain from posting links to the font files required to build this package. Microsoft fonts are protected by copyright and neither we nor you are allowed to distribute them. This package only provides an approach to cleanly integrate the fonts into an Arch Linux system provided that you have a licensed copy of Windows 10. Otherwise you can use the ttf-ms-fonts package to install publicly available fonts.

If you post comments intending to distribute the fonts via this page we need to contact administrators in order to remove your comment.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

smrqdt commented on 2020-07-18 05:03

I had the problem that the fonts looked horrible, and it turns out the reason is they have terrible embedded bitmaps. To get proper rendering there’s a fontconfig option to fix that:

Maybe it would be reasonable to ship a proper fontconfig file (in /etc/fonts/conf.{avail,d}/) including that fix with this PKGBUILD.

Galaxy3056 commented on 2020-06-21 20:26

sha256sums are either outdated or incorrect

leaveye commented on 2020-05-04 07:30

@new2001 I prefer no auto download too, but edit URL, DLAGENTS and build package is a little tricky and not so friendly. I think if we can directly use my own .iso/.wim/windows-path or just provide some helper function, it would be better.

neo2001 commented on 2020-05-01 14:08

@baderas: You don't need to update the package, you can even make your own local copy and download and extract as you prefer. Most of the changes are very minor anyway. Automatically downloading a whole OS setup, just for some font files, is too much as a default solution, in my opinion, especially for people with limited internet access. I also understand the maintainer doesn't want to risk any "trouble" just for the sake of more convenience.

baderas commented on 2020-05-01 10:27

Why can't you just download the Windows 10 Enterprise 90-day evaluation automatically and extract the fonts? You would not distribute any copyrighted material in this way. This package needs manual steps for every update when updating it with yay (for example).

Bevan commented on 2020-04-30 17:30

kizar: Strange, for me it is still part of my Windows installation. It is also still listed under But we have the same issue with other fonts such as holomdl2.ttf. I recommend that you just remove the corresponding line from the PKGBUILD and run makepkg with --skipchecksums.

kizar commented on 2020-04-27 18:02

marlett.ttf is not included in the latest release of Windows 10

Bevan commented on 2020-04-09 09:09

To me this sounds reasonable. My plan was to wait for the outcome of the corresponding discussion on arch-dev-public:

This discussion has stalled though. If there are no new arguments within the next week or so I guess we can go forward and just remove the dependencies.

ChrisLane commented on 2020-04-09 09:03

Came to ask the same as @jakebailey regarding removing unnecessary dependencies. Hoping to get rid of some xorg packages but can't while they're depended on.

jakebailey commented on 2020-03-30 04:34

Per and, font packages don't need to depend on anything. Any chance this package's dependencies can be dropped? It seems like there's a push to fix all of Arch's existing packages to no longer depend on these (and it'd be nice to no longer need it for my AUR packages as well).