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: 126
Popularity: 1.54
First Submitted: 2015-08-21 07:39 (UTC)
Last Updated: 2021-10-18 14:15 (UTC)

Dependencies (0)

Required by (252)

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

1 2 3 4 5 6 .. 24 Next › Last »

Scimmia commented on 2021-10-20 16:57 (UTC)

For the last 4 people that commented, make sure to read the FAQ in the pinned comment.

Stane1983 commented on 2021-10-20 09:08 (UTC)

Inkfree.ttf checksum is wrong on latest Win10 install media.

8b89481f274ee1ad6fe49f539fc4435e114bc684beecb3fdafd6c7817bd05d85 checksum should be replaced with f23225869ceb58b78a836b84207d1726cc5d9c3f5fe2ae8a295ff62a98df09a0.

bakgwailo commented on 2021-10-19 04:00 (UTC)

I get a checksum error:

Inkfree.ttf ... FAILED

using the latest install media (Win10_21H1_English_x64.iso)

wszqkzqk commented on 2021-10-18 07:11 (UTC)

Deng.ttf, Dengl.ttf and Dengb.ttf may need to be added to package ttf-ms-win10-zh_cn

zeroconf commented on 2021-10-16 11:36 (UTC) (edited on 2021-10-16 11:37 (UTC) by zeroconf)

When trying to install:

==> Retrieving sources...

Unable to find file://*.ttf, please read the PKGBUILD

... will be announced in case of every font. I just replaced font name with asterisk to mention, that it happens in case of every font.

Same happens with checksums:

==> Validating source files with sha256sums... *.ttf ... NOT FOUND

Finally there will be announcement

==> ERROR: One or more files did not pass the validity check! -> error making: ttf-ms-win10

... and installation will be interrupted.

ttf-ms-win10-auto is outdated for now...

Zepman commented on 2021-02-24 16:52 (UTC) (edited on 2021-04-08 12:03 (UTC) by Zepman)

For anyone who wants to try an automated download, please try ttf-ms-win10-auto. It downloads the fonts from Microsoft, and it does not download an entire ISO unless it needs to.

barkley128 commented on 2021-02-23 16:30 (UTC)

I understand I can disable updating it, e.g. using /etc/pacman.conf, my helper reads it. I was more curious what do these updates add? Is it more/different fonts upon Windows updates?

neo2001 commented on 2021-02-23 11:15 (UTC)

Well, you don't need to update.

I'm no expert, but I guess if the checksums for the fonts would be in another file and then sourced, it would work. But then this file's checksum will change and needs to be ignored...

You could simply checkout the package from the AUR using git and then change the package name, so AUR helpers won't try to find updates for it. Then you can control when and if you want to update the font files.

barkley128 commented on 2021-02-23 08:14 (UTC)

Thank you, but why do packages like this one even update? It's a bit annoying to copy fonts again and again.

kode54 commented on 2021-02-23 01:56 (UTC)

Sorry, I should have looked at the script before I posted. I didn't realize the Enterprise Trial ISO that was linked in the posted PKGBUILD was on a permanent link. Certainly, that could save users (and Microsoft) a lot of bandwidth if it were dynamically mounted to access the Install.wim inside, and only extract specific files from it, rather than copying it entirely to the local filesystem.

Assuming, of course, that this particular permanent link allows random access. Worth a shot, though.

I do know I won't be using the download-ISO version for my own installs, since I keep a handy Windows 10 Pro for Workstations installation on my machine, and the fonts from it also match the PKGBUILD hashes. Doesn't mean it's not useful to actually become a stand-alone self-sufficient script that doesn't require manual intervention.