Package Details: ttf-ms-win10-thai 10.0.19043.1055-1

Git Clone URL: https://aur.archlinux.org/ttf-ms-win10.git (read-only, click to copy)
Package Base: ttf-ms-win10
Description: Microsoft Windows 10 Thai TrueType fonts
Upstream URL: http://www.microsoft.com/typography/fonts/product.aspx?PID=164
Licenses: custom
Conflicts: ttf-vista-fonts
Provides: ttf-font
Submitter: Bevan
Maintainer: Bevan (Scimmia)
Last Packager: Scimmia
Votes: 122
Popularity: 0.98
First Submitted: 2015-08-21 07:39 (UTC)
Last Updated: 2021-10-18 14:15 (UTC)

Dependencies (0)

Required by (256)

Sources (144)

Pinned Comments

Bevan commented on 2019-04-16 07:36 (UTC) (edited on 2019-07-11 18:01 (UTC) by Bevan)

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 (UTC)

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 9 10 11 .. 24 Next › Last »

gourdcaptain commented on 2019-04-15 21:50 (UTC) (edited on 2019-04-15 21:50 (UTC) by gourdcaptain)

There doesn't appear to be a new ISO available for a version this would be linked to. Is there a new feature update this is related to?

katt commented on 2019-04-15 20:42 (UTC)

Downloaded the latest Evaluation ISO (Enterprise Non-LTSC) and my msgothic.ttc has yet a different shasum, Microsoft must be high on some real strong shit. 0a6480c7df5382ee96670a5557719857916b63b023fcc84f8789c621 msgothic.ttc

Bevan commented on 2019-04-15 18:19 (UTC)

priito: I updated the checksum of msgothic.ttc to the one matching an up-to-date installation. Unfortunately, it seems like your image contains yet another version of it. However, you can always build with "makepkg --skipchecksums".

kode54 commented on 2019-04-14 23:43 (UTC)

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

priito commented on 2019-04-12 10:59 (UTC) (edited on 2019-04-12 11:04 (UTC) by priito)

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

SomeOwl commented on 2019-02-28 12:08 (UTC) (edited on 2019-02-28 12:16 (UTC) by SomeOwl)

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.

misc commented on 2019-02-14 00:56 (UTC) (edited on 2019-04-19 17:28 (UTC) by misc)

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

Scimmia commented on 2019-02-10 07:20 (UTC)

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

webarnes commented on 2019-02-10 03:41 (UTC) (edited on 2019-02-10 03:41 (UTC) by webarnes)

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

francoism90 commented on 2019-01-03 09:51 (UTC) (edited on 2019-01-03 09:57 (UTC) by francoism90)

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