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: 123
Popularity: 1.14
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 .. 4 5 6 7 8 9 10 11 12 13 14 .. 24 Next › Last »

vS0uz4 commented on 2018-03-31 12:36 (UTC) (edited on 2018-03-31 12:38 (UTC) by vS0uz4)

Hi

Did anyone else encounter the following error when trying to create and install the package?

Is there a need to remove any old installation from the package, and do the reinstallation?

Log of errors

https://pastebin.com/3HTHTMcn

francoism90 commented on 2018-03-14 13:36 (UTC)

Could you please fix the readme? wimlib is available in the repo's. :)

Scimmia commented on 2018-02-28 22:46 (UTC)

And both are crap. The AUR uses git, if you want a different version, just check that version out.

severach commented on 2018-02-28 22:17 (UTC)

ttf-win7-fonts has done multiple SHA sums for many years now. ttf-ms-win8 has it too.

Bevan commented on 2018-02-28 13:52 (UTC)

Ataraxy: Multiple SHA sums for one file are not possible. We could only set it to "SKIP" to completely ignore them but I don't think that's a good idea. If you know what causes the different checksum (as in this case), you can simply run updpkgsums before makepkg as a workaround. Or run makepkg with the argument --skipchecksums.

Ataraxy commented on 2018-02-28 13:03 (UTC) (edited on 2018-02-28 13:08 (UTC) by Ataraxy)

I have a fully updated Win10 box, with cour.ttf saying it is File version 6.90.

d4557f9674de7c5ef58ad4c3651016944672c6bf1f5e9253abfeea9730939808 cour.ttf

Is it possible to allow more than one SHAsum for a file? What version does the PKGBUILD expect?

chraffx commented on 2018-02-16 12:21 (UTC)

Good to know, thanks for the quick help!

Bevan commented on 2018-02-16 11:57 (UTC)

@chraffx: The checksum of that file was changed in Januar's Windows update, so we updated it here as well. I guess you have some pending updates that haven't been installed after your recent installation yet.

chraffx commented on 2018-02-16 11:52 (UTC)

@Bevan ah, thx, I misinterpreted the skip as an error. The one that actually failed was cour.ttf, which was fixed by changing the checksum entry '8da71b5c11b17bade23095559fb0905741c15ee2f8800b1fa0ceb100e3fd6f45' to '4dc9a0be2df1d3872a3fae62be7c7aec1b6d6838a4a3302c6428a06635f4d2cb'. My windows install was pretty recent, are there two versions of that file? Or is that entry just outdated?

Bevan commented on 2018-02-16 11:25 (UTC)

@chraffx: The checksum of license.rtf differs for different languages and maybe also different versions of Windows. That's why we skip the checksum check for that file (last entry of sha256sums is 'SKIP').

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 24 Next › Last »