Japanese fonts updated
PKGBUILD lines 286-289 https://pastebin.com/RtC83BqZ
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: | 1.02 |
First Submitted: | 2015-08-21 07:39 (UTC) |
Last Updated: | 2021-10-18 14:15 (UTC) |
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 24 Next › Last »
Japanese fonts updated
PKGBUILD lines 286-289 https://pastebin.com/RtC83BqZ
iMalinowski: Thanks to git, there is already a changelog which we try to fill with meaningful comments. Just click "View Changes" under Package Actions.
seguiemj.ttf updated 28/05/2018, please update the package to the new checksum.
It is worth noting that the 32-bit Enterprise ISO is lighter than the 64-bit one (2.9 GB against 4.0 GB).
No
The problem with this package is that every few months when Microsoft releases new fonts and the build fails, preventing pacaur from upgrading doing a AUR system upgrade. Getting the latest versions of the fonts is annoying to say the least.
Could hashes of older fonts be allowed, with a warning that new versions exist?
is this package include mt extra? wps office needs mt extra to view some equation or something
vS0uz4: There is a forum entry which looks very related: https://bbs.archlinux.org/viewtopic.php?id=235643
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:
I get an error that the sources cannot be downloaded: Please read the instructions on the top of the PKGBUILD.
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".
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".
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.
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)