Package Details: ttf-ms-win10-japanese 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 Japanese 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: 1.02
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 .. 24 Next › Last »

FredBezies commented on 2021-02-07 12:20 (UTC)

You can also use Windows 10 2020H2 ISO to grab all the needed fonts.

tdy commented on 2021-02-07 07:30 (UTC) (edited on 2021-02-07 07:32 (UTC) by tdy)

FWIW I do have holomdl2 and on my ThinkPad's OEM Win 10 Pro.

chuangzhu commented on 2020-12-21 06:42 (UTC)

@kode54 I think they are TrueType fonts.

<img alt="KaiTi and SimHei" src="https://fars.ee/LBg4.png" />

kode54 commented on 2020-12-20 07:29 (UTC)

@genelocated aren't those bitmapped fonts?

chuangzhu commented on 2020-12-20 07:04 (UTC) (edited on 2021-01-03 07:07 (UTC) by chuangzhu)

Include SimSun and SimKai for zh_CN fonts.

https://pastebin.com/WhnMLTZD

mladoux commented on 2020-09-15 20:46 (UTC) (edited on 2020-11-27 17:16 (UTC) by mladoux)

sha256 sums for Windows 10, build 2004:

https://pastebin.com/qa5h0tGG

Bevan commented on 2020-09-09 11:53 (UTC)

@kode54: I unflagged it again. This happens all the time because people often do not read the FAQ.

kode54 commented on 2020-09-09 03:12 (UTC)

Why is this flagged out of date? There hasn't been a new feature release of Windows since April.

smrqdt commented on 2020-07-18 05:03 (UTC)

I had the problem that the fonts looked horrible, and it turns out the reason is they have terrible embedded bitmaps. To get proper rendering there’s a fontconfig option to fix that: https://stefan.angrick.me/fix-rendering-of-microsoft-calibri-and-cambria-fonts-on-linux

Maybe it would be reasonable to ship a proper fontconfig file (in /etc/fonts/conf.{avail,d}/) including that fix with this PKGBUILD.

Galaxy3056 commented on 2020-06-21 20:26 (UTC)

sha256sums are either outdated or incorrect