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.12
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 .. 5 6 7 8 9 10 11 12 13 14 15 .. 24 Next › Last »

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

Hello, I've copied the fonts from my windows partition but I'm having trouble finding the license.rtf file. Where can I locate it? It isn't in the fonts directory and the one in System32 doesn't have the right checksum.

Shatur commented on 2018-01-11 12:41 (UTC)

@Beva, thank you!

Bevan commented on 2018-01-10 21:04 (UTC) (edited on 2018-01-10 21:06 (UTC) by Bevan)

Shatur: I don't think that Microsoft releases new ISOs for every OS build. So if you are relying on the ISOs you probably have to stick with the last version of this package.

Note that you can always download old versions of the PKGBUILD from AUR. For the Fall Creators Update ISO this would be the following link:

https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h=ttf-ms-win10&id=6c560852abeb

Shatur commented on 2018-01-10 20:56 (UTC) (edited on 2018-01-10 20:57 (UTC) by Shatur)

Where I can download windows image with latest fonts?

cbrnr commented on 2018-01-09 11:37 (UTC)

@smg3d same here, the sha256sum of cour.ttf does not match. However, you pasted the wrong file.

The old hash was: 4dc9a0be2df1d3872a3fae62be7c7aec1b6d6838a4a3302c6428a06635f4d2cb And the new one is: 8da71b5c11b17bade23095559fb0905741c15ee2f8800b1fa0ceb100e3fd6f45

smg3d commented on 2018-01-05 04:40 (UTC)

Looks like cour.ttf was updated Dec.5, and current sha256sum does not match.

0160b83ba3024ea2a1d6024cabb4eb6a1f6503beb7938181e4f2a22272e7ead1 courbd.ttf

my Win10 was updated yesterday. cour.ttf is v 6.92, whereas the other cour* are v 6.91.

-r-xr-xr-x 1 smg smg 797316 Sep 29 09:41 courbd.ttf -r-xr-xr-x 1 smg smg 577524 Sep 29 09:41 courbi.ttf -r-xr-xr-x 1 smg smg 667472 Sep 29 09:41 couri.ttf -r-xr-xr-x 1 smg smg 818480 Dec 5 02:26 cour.ttf -r-xr-xr-x 1 smg smg 879640 Sep 29 09:41 ebrimabd.ttf -r-xr-xr-x 1 smg smg 876784 Sep 29 09:41 ebrima.ttf

cswl commented on 2017-11-21 13:47 (UTC)

Seems like it's an issue with my installation/reinstalltion of Windows. I get I/O errors. https://superuser.com/questions/1270456/how-can-i-properly-delete-my-messed-up-windows-old-folder/

neo2001 commented on 2017-11-20 19:24 (UTC)

I wrote a Python script to copy the font files on Windows (obviously you need Python installed for this): https://gist.github.com/fiechr/8218ae9c9f6abfedbfc283ac3b35a3d8 You need the current PKGBUILD from this AUR package - put it in the same directory as the script above (or provide a path to it). Example: python.exe copy-font-files.py c:\temp This will copy all fonts found in the PKGBUILD to c:\temp. Show all options: python.exe copy-font-files.py -h The script will also check the SHA256 hashes which it also gets from the PKGBUILD. I wrote this initially for myself. I'm not a programmer, so don't be to hard on me. There are certainly ways to make this simpler or better. But it worked perfectly fine for me - but use it at your own risk! (You can run it from a *nix system, but you need to provide a working path to a Windows Font directory.)

Scimmia commented on 2017-11-20 18:28 (UTC)

Which has nothing to do with his question. cswl, how do they not match?

abouvier commented on 2017-11-20 17:44 (UTC)

Use `makepkg --skipchecksums` :p