Package Base Details: ttf-ms-win10

Git Clone URL: https://aur-dev.archlinux.org/ttf-ms-win10.git (read-only)
Submitter: Bevan
Maintainer: Bevan (Scimmia)
Last Packager: Scimmia
Votes: 40
Popularity: 2.380845
First Submitted: 2015-08-21 07:39
Last Updated: 2017-01-20 17:51

Pinned Comments

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 ... Next › Last »

gosella commented on 2016-11-04 13:52

From what version of Windows 10 are the new Calibri checksums?

The files in the ISO provided for evaluation (currently version 14393.0.160715-1616.RS1_RELEASE_CLIENTENTERPRISEEVAL_OEMRET_X64FRE_ES-ES.ISO) doesn't match.

tehabe commented on 2016-09-28 11:24

I took the fonts from my old Windows 10 installation, and the font marlett.ttf was missing.

It is a hidden font, only being used by the system anyway.

Hori commented on 2016-09-25 08:27

How can I install the fonts from Windows 10 Education Edition? I have that because I am a student and the university gave me a license.

Scimmia commented on 2016-08-28 20:24

@sl1pkn07, there are no font hooks yet.

Looks like you're correct, my mistake.

sl1pkn07 commented on 2016-08-28 19:51

EDIT: fuck :S

with the pacman hooks, the .install in this package is still needed?

and the MS Gothic is not a Japanese font?

https://www.microsoft.com/typography/fonts/family.aspx?FID=250
https://www.microsoft.com/typography/fonts/font.aspx?FMID=2145

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 2016-08-06 02:51

Still getting the error:
==> ERROR: fontsarial.ttf was not found in the build directory and is not a URL.

1. Source is the latest Win 10 Professional ISO 'burnt' to USB install drive
2. Extracted 'fonts' from 'USB drive>sources>install.esd' (332 files)
3. Copied all 332 extracted files to the same directory as the PKGBUILD
4. makepkg > error

Using gnome+nautilus, if that's any help. Not sure why it wants 'fontsarial.ttf' - it's not listed anywhere in the PKGBUILD.

UPDATE: Success! Again tried copying *in windows*, the system font folder to the win desktop, then across to Arch. Still wouldn't build unless I did "makepgk -c --skipinteg". Then errored as "MARLETT.TTF" wasn't found. Found a copy of that, renamed it to lower case ---- DONE! :)

Scimmia commented on 2016-08-05 12:55

I generally use cygwin when copying, hasn't let me down yet.

Nocifer commented on 2016-08-05 12:17

@sultanoswing, in case you still have problems:

As far as I can tell, with the Anniversary update MS changed the way font files are manipulated. Font families are no longer shown as separate font files in Explorer, instead they are shown as some kind of special container link (shortcut) that when clicked opens up in a Control Panel-like instance that lets you see the separate fonts. Long story short, this means that copying over the fonts while on Linux results in copying over a bunch of broken 25kB links instead of the fonts, because Linux doesn't know how to read those links and extract their contents.

So, two possible solutions: either you do as @freaxtux said and *while on Windows* copy over the fonts from the \Windows\Fonts folder to another one (this "magically" results in the proper fonts being pasted), and then use this new folder to use them from within Linux, or you forget about them altogether and extract the fonts anew from the Win10 install image (from the install.wim archive, as per PKGBUILD instructions).

sultanoswing commented on 2016-08-04 07:30

Won't build for me as it can't find any of the files, even though I've copied all of my Windows/Fonts folder to the same directory as the PKGBUILD (yes, I have the updated Anniversary Edition of Win 10 Professional).

EDIT: As per freaxtux's post below, I changed the file:// attribute in the PKGBUILD and it's now failing with:
==> ERROR: fontsarial.ttf was not found in the build directory and is not a URL

Tried copying /windows/fonts from my Win 10 Home edition too. Same result.

Hmmm - "fontsarial.ttf" isn't even referred to in the PKGBUILD!?

/confused.