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: 0.98
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 .. 9 10 11 12 13 14 15 16 17 18 19 .. 24 Next › Last »

Bevan commented on 2017-04-07 08:14 (UTC)

For people still wanting to use files obtained from the Anniversary Update (1607): You can obtain an older version of this PKGBUILD from https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ttf-ms-win10&id=4436ac9c49b9ced5d2f73927876913fa7c22f54b

vasily commented on 2017-03-18 10:40 (UTC)

The Win10 evaluation iso is with version string '14393.0.160715-1616' and ships the Calibri fonts not compatible with this PKGBUILD. Windows 10 iso with version string '14393.953' does contain compatible Calibri fonts. The "Insider Previewer" '15019.1000.170121-1513' version has yet different (updated?) fonts.

haqins commented on 2017-02-08 23:49 (UTC)

I figure out something so i share :) In Windows 10 build 15019 (Windows Insider) you can't just simple copy fonts using explorer, same in Linux (make symlinks only) but using 3th software e.g TotalCommander, or 7zip, you can compress files and get them on linux. checksum are diffrent, but still can use SKIP option hope i help anybody!

zilti commented on 2017-02-05 11:53 (UTC)

How do the "file://" things in the PKGBUILD file work? When I change them, I get "ERROR: file could not be found inside the build directory and is not an URL".

<deleted-account> commented on 2017-01-21 00:11 (UTC)

voting for the checksum to revert to the older version. Not everyone has the resource to install win and let it update.

dobyrch commented on 2017-01-18 18:29 (UTC)

My installation of Windows 10 Home was also missing marlett.ttf in the Fonts directory, but I found a copy in C:\Windows\WinSxS.

holunder commented on 2017-01-01 20:59 (UTC) (edited on 2017-01-01 21:00 (UTC) by holunder)

My up-to-date Windows 10 Pro installation doesn't has a marlett.ttf.

mgd commented on 2016-12-18 18:47 (UTC)

From what had been posted already the reason should be quite obvious. The fonts you get from the Windows 10 Enterprise 90-day evaluation are not the current versions of the Windows 10 fonts for all 6 calibri*.ttf. What do you guys expect this package should do? Cater for the current version of the fonts or cater for some older version of the fonts that come with a time limited evaluation licence? [I will will refrain from commenting on possible legal issues with using fonts from an evaluation version as I'm sure you guys are already aware of them...]

Krieger commented on 2016-12-18 00:34 (UTC)

I had the same problem as cbrnr. I downloaded the Windows 10 Enterprise 90-day evaluation from the link in the PKGBUILD, extracted the fonts, and attempted to build the package. Every font checksum passed except for the 6 Calibri fonts. I edited the checksums in the PKGBUILD to the ones cbrnr posted and it worked.

Scimmia commented on 2016-12-12 14:34 (UTC)

cbrnr, you assume you're up to date, but you're not.

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 24 Next › Last »