Package Base Details: ttf-ms-win10

Git Clone URL: https://aur.archlinux.org/ttf-ms-win10.git (read-only, click to copy)
Submitter: Bevan
Maintainer: Bevan (Scimmia)
Last Packager: Scimmia
Votes: 93
Popularity: 2.91
First Submitted: 2015-08-21 07:39
Last Updated: 2019-05-22 07:25

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: https://docs.microsoft.com/en-us/typography/fonts/windows_10_font_list).

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.

sultanoswing commented on 2015-11-12 22:33

Since the update today, a whole bunch of the integrity checks fail.

olejon commented on 2015-11-08 07:58

Great stuff. Just remember to read the PKGBUILD!

sultanoswing commented on 2015-11-06 20:36

@Scimmia - no, upgrade from Win 7. Same thing on two different machines oddly enough, but luckliy not on a third, which does have the full 400MB+ font folder in the specified location (I have no idea where they are on the other two machines, as there is only ~300k in the Windows/Fonts folder, with most of the files being links instead. Weird, but not a problem with this delightful package!

Scimmia commented on 2015-11-06 16:37

@sultanoswing, OEM installation? OEMs can screw with a lot of things.

sultanoswing commented on 2015-11-06 11:32

Cheers - figured that out, and it was a problem with my Win 10 Fonts directory not having all the files for some reason. Now sorted thanks!

Bevan commented on 2015-11-06 11:25

@sultanoswing: This error will be shown if one of the expected files are missing. Unfortunately makepkg's output is not very helpful at that point.

Please have a look at the lines above the error. They show which files were found. Comparing that with the file list here in AUR (or in the .SRCINFO file) you will be able to see which file would come next and so which one is causing the error.

sultanoswing commented on 2015-11-06 11:16

Get error on "makepkg":
ERROR: Unknown download protocol: file
Aborting...

Not sure what I'm doing wrong, I've copied all the fonts from my Win 10 /Fonts directory and the licence.rtf file to the same directory as PKGBUILD.

A.J commented on 2015-11-06 07:10

@Scimmia: no biggie , that's what ignorepkg is for .

Scimmia commented on 2015-11-06 07:04

@step-2, at this point, I think we'll just have to say "you can't please everyone" and leave it at that.

Scimmia commented on 2015-11-06 02:28

@zikaeroh, sorry about that, my fault. Fixed now.

@step-2, yes, the old package would be the same as installing all of the new packages.