Package Details: ttf-ms-win8-japanese 6.3.9600.17238-1

Git Clone URL: https://aur.archlinux.org/ttf-ms-win8.git (read-only, click to copy)
Package Base: ttf-ms-win8
Description: Microsoft Windows 8.1 Latin and International TrueType fonts
Upstream URL: http://www.microsoft.com/typography/fonts/product.aspx?PID=161
Licenses: custom
Conflicts: ttf-ms-fonts, ttf-tahoma, ttf-vista-fonts, ttf-win7-fonts, ttf-win7-fonts-autodownload
Provides: ttf-font, ttf-ms-fonts, ttf-tahoma, ttf-vista-fonts, ttf-win7-fonts
Submitter: reflexing
Maintainer: severach
Last Packager: severach
Votes: 62
Popularity: 0.000000
First Submitted: 2012-06-08 06:11 (UTC)
Last Updated: 2017-07-13 07:10 (UTC)

Required by (290)

Sources (8)

Pinned Comments

severach commented on 2018-03-01 20:05 (UTC)

Package is not broken. You can't build this with yaourt or pamac. It must be built with makepkg after obtaining the fonts manually.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 34 Next › Last »

reflexing commented on 2015-04-21 04:41 (UTC)

@matthias.lisin I don't have this problem with Infinality's fontconfig rules: https://wiki.archlinux.org/index.php/Infinality

matthias.lisin commented on 2015-04-20 17:39 (UTC)

If somebody is having issues with ugly-bold Arial font in Qt applications: It's caused by 'ariblk.ttf'. You can delete this font to solve this problem or find a solution using fontconfig conf.d files.

radioxoma commented on 2015-04-05 19:48 (UTC)

It's possible to skip checksums verification. Just: $ makepkg -s --skipchecksums

JuHwon commented on 2015-03-26 21:30 (UTC)

==> ERROR: arial.ttf was not found in the build directory and is not a URL.

boogerlad commented on 2015-02-20 22:57 (UTC)

I got Windows 10 fonts working with this package by changing the PKGBUILD like so: https://www.diffchecker.com/3bic358t

<deleted-account> commented on 2015-02-10 23:36 (UTC)

@reflexing At least update your comments / instructions in the pkgbuild to note the actual requirements. The statements about this working with "any edition of Windows 8.1 RTM build 6.3.9600.17050" are false. The information on how to retrieve is good, but after spending the time to register with Microsoft, download an ISO, and extract the fonts it is frustrating to find out that you have to then manually modify the pkgbuild if you want it to work. Your use of arrays to store the file list doesn't make it simple to generate the md5sums in the correct order.

reflexing commented on 2015-02-10 16:05 (UTC)

@aitrus I wanted to create an ArchWiki page with all around ways to install package and leave a link to it in the PKGBUILD, but "Arch wiki warriors" cleaned it up: https://wiki.archlinux.org/index.php?title=Ttf-ms-win8&oldid=337682 > Perhaps it would be better if the build asked whether you are using the ISO or an install as the source of the fonts. I think this kind of automation is against the Arch Way. I won't implement it.

<deleted-account> commented on 2015-02-10 15:54 (UTC)

@reflexing Understood, but that is confusing. The pkgbuild specifically calls out using the ISO and even gives download / extraction instructions. Perhaps it would be better if the build asked whether you are using the ISO or an install as the source of the fonts.

reflexing commented on 2015-02-08 12:21 (UTC)

@eunonimo you can use it as a base. Win 10 has slightly different font list, and some of the olf fonts have their version bumped. I hasn't finished ttf-ms-win10 yet.

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 34 Next › Last »