Package Details: ttf-ms-win10-sea 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 Southeast Asian 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: 123
Popularity: 1.08
First Submitted: 2015-08-21 07:39 (UTC)
Last Updated: 2021-10-18 14:15 (UTC)

Dependencies (0)

Required by (249)

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 .. 12 13 14 15 16 17 18 19 20 21 22 .. 24 Next › Last »

Scimmia commented on 2016-04-20 03:58 (UTC)

@hiddenhand, there's nothing to fix. I just checked it, all filenames and checksums are correct. MS has added msgothic.ttc, but that shouldn't affect anything as it will just be skipped. Likely we'll add it here next time the ISO is updated. If you're having problems, read the PKGBUILD again, it's likely you missed something.

hiddenhand commented on 2016-04-19 20:20 (UTC) (edited on 2016-04-19 20:26 (UTC) by hiddenhand)

@rev0ltz How did you fix it exactly? I'm kinda new to this and I'm still getting the validity check error. Thanks Edit: Nevermind that, I managed to install it by following @rehash comment. Thanks!

Scimmia commented on 2016-03-02 02:55 (UTC)

@Theredbaron1834, the PKGBUILD gives the location of license.rtf, and it's not in the Fonts folder.

Theredbaron1834 commented on 2016-03-02 02:43 (UTC)

I was using an installed Win10, and the Font folder did not include a "license.rtf". Is there any way to either ignore if not there, DL it from someplace else, or add a link to a place it is saved in the pkgbuild? As is I just touched license.rtf.

rehash commented on 2016-02-06 15:17 (UTC)

@rev0ltz or use 'updpkgsums' on the clonned directory before makepkg

eduncan911 commented on 2016-02-02 16:32 (UTC)

Just FYI with all the comments, the package works fine with an update to date Windows 10 Pro machine as of Feb 2nd. View the PKGBUILD (just like you should be doing for each AUR package you install) for instructions that worked flawlessly.

Scimmia commented on 2016-01-10 22:34 (UTC)

Either they aren't the right files or you put them in the wrong location. Not a lot to go wrong there.

gurevitch commented on 2016-01-10 21:48 (UTC)

It literally doesn't detect a single file I've copied into the folder, I copy everything into the folder with the PKGBUILD and it won't detect a single one of the files, not sure what to do :P

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 24 Next › Last »