Arch Linux User Repository

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).

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.

May as well wait for the next feature update by this point.

msgothic.ttc appears to be failing its checksum verification. Font source: Win10_1809Oct_v2_English_x64.iso from MS's download page (sha256: 009eca8401938643801e74ddfcd65d3e600b27db93e4615368fa83c4964d1e7c).

Extracting Fonts from your own dual-boot installation is a real chore if you assume that you can simply copy files. If you mount your Windows 10 partition while running Arch, you will miss some files. They are not there. If you run Windows 10 and navigate to C:\Windows\Fonts in explorer.exe, you will not see all files either.

You need to run Windows 10 and copy your fonts in your shell (cmd or powershell, doesn't matter). Then, you might still encounter "missing fonts" errors, because MS isn't consistent in their file name letter cases. In my case, I had to rename NirmalaB.ttf and NirmalaS.ttf to match the PKGBUILD letter cases.

I think this misses Yu Mincho for the Japanese subpackage? yumin.ttf – yuminl.ttf – yumindb.ttf

edit: Still missing in the update. In fact, there's a whole array of missing Japanese fonts: https://docs.microsoft.com/en-us/typography/fonts/windows_10_font_list

Then your system isn't up to date. Check the version info.

I downloaded something called the October update on my Windows machine but it didn't bring me up to date with this package. The previous commit ([8517c04e62fd](https://aur.archlinux.org/cgit/aur.git/commit/?h=ttf-ms-win10&id=8517c04e62fd)) worked with fonts copied from a completely up to date system (updated this afternoon).

@Bevan Please add the following stuff to the PKGBUILD :)

When on (Arch) Linux, the Windows 10 ISO can be downloaded using the following URL: https://www.microsoft.com/nl-nl/software-download/windows10ISO

License location may differ: C:\Windows\System32\Licenses\neutral\_Default\Core\license.rtf -> Core may be Professional.

Mounting the ISO requires loop, e.g.: $ sudo mount -o loop Win10_1809Oct_EnglishInternational_x64.iso /mnt/cdrom

Extracting the fonts: $ wimextract /mnt/cdrom/sources/install.wim 1 /Windows/{Fonts/"*".{ttf,ttc},System32/Licenses/neutral/"*"/"*"/license.rtf} --dest-dir ~/Downloads/fonts

Thanks.

@iboyperson Are you sure your iso is windows 10 1809? Microsoft has pulled off all 1809 upgrade methods due to a data loss bug and haven't yet released 1809 back to the general public as of this writing (18 11 05). As you can see here https://www.microsoft.com/en-us/software-download/windows10 the update assistant page is still referring to the 1803 update.

Read the previous comments

I would appear that Candara Light and Corbel Light are not present in a freshly extracted iso.