Package Details: ttf-ms-win11 10.0.26100.2605-1

Git Clone URL: https://aur.archlinux.org/ttf-ms-win11.git (read-only, click to copy)
Package Base: ttf-ms-win11
Description: Microsoft Windows 11 TrueType fonts
Upstream URL: http://www.microsoft.com/typography/fonts/product.aspx?PID=164
Licenses: custom
Conflicts: ttf-ms-fonts, ttf-tahoma, ttf-vista-fonts
Provides: emoji-font, ttf-font, ttf-ms-fonts, ttf-tahoma
Submitter: Vaporeon
Maintainer: Vaporeon (Scimmia)
Last Packager: Scimmia
Votes: 26
Popularity: 0.125482
First Submitted: 2021-10-11 13:33 (UTC)
Last Updated: 2024-12-11 00:26 (UTC)

Dependencies (0)

Required by (305)

Sources (142)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Vaporeon commented on 2022-03-15 18:49 (UTC) (edited on 2022-03-15 18:49 (UTC) by Vaporeon)

Un1Gfn: See the pinned comment in regards to building using the ISO fonts. The current package version always assumes an up to date live install.

When using other font versions you have two options. 1: check out the package at a version that matches the fonts you currently have. doing this means pkgver will properly match the versions of the fonts you have. -or- 2: skip checksum verification to force the current version to build with your current font files (as you have done).

zkm2fw commented on 2022-03-14 05:28 (UTC) (edited on 2022-03-18 07:37 (UTC) by zkm2fw)

build failure

==> Validating source files with sha256sums...
    ...
    seguibli.ttf ... Passed
    seguiemj.ttf ... FAILED
    seguihis.ttf ... Passed
    ...

ttf-ms-win11 10.0.22000.348-1

Win11_English_x64v1.iso sha256=4bc6c7e7c61af4b5d1b086c5d279947357cff45c2f82021bb58628c2503eb64e

I changed the sha256sum of seguiemj.ttf from edd76b88c44432ba1818992259c31d45abd28fbcfbb3eeebad3f6af27636213c to SKIP, and got a successful build.

Edit: Sorry I didn't read the pinned comment carefully. Got it now. Thanks.

Vaporeon commented on 2021-12-08 13:25 (UTC)

As said already this package tracks the fonts that are commonly installed across ALL versions of Windows 11. See [1] for the font list. Fonts that acquired using FOD (Feature On Demand) or that are only present on some installation media are excluded. The reason for this is that it is considered unreasonable to expect everyone obtain all of these font files in order to be able to build this package.

If you consider one or more of these optional fonts to be "essential", then that it is an issue to be taken with Microsoft. They made the distinction, not us.

[1] https://docs.microsoft.com/en-us/typography/fonts/windows_11_font_list

Vaporeon commented on 2021-12-08 12:35 (UTC) (edited on 2021-12-08 12:43 (UTC) by Vaporeon)

If you wish to build the package using fonts from the ISO, run git checkout 5ba5194a795c71999d16510aeb4a24ecbc8d1782 after cloning the AUR package repo.

This will revert the PKGBUILD to match the font versions used in the release ISO.

The master branch HEAD tracks the font versions installed in an up-to-date live install and requires those fonts to be used as the source.

bbx0 commented on 2021-12-07 20:37 (UTC)

I had the same issue as @kogasa today - no ISO seems yet to contain the new seguiemj.ttf in version 1.33. You need an updated Win11 install to get it or maybe check on reddit, if someone just has found the new version.

kogasa commented on 2021-12-07 20:13 (UTC) (edited on 2021-12-07 20:17 (UTC) by kogasa)

As of today, seguiemj.ttf fails the validity check. I see the SHA256 hash for this font was updated today, but I'm not sure why. I downloaded the latest Win11 ISO (SHA256 4bc6c7e7c61af4b5d1b086c5d279947357cff45c2f82021bb58628c2503eb64e) and re-extracted the fonts, and the included copy has the old SHA256 hash.

smcf commented on 2021-12-07 19:41 (UTC) (edited on 2021-12-07 19:42 (UTC) by smcf)

Well, maybe we are talking past each other a little bit. MS Gothic, MS Mincho, and Meiryo are the default fonts on Japanese Windows 11. Extract Win11_Japanese_x64v1.iso and you can see this pretty clearly. The fonts in the document, in contrast, are the fonts that Microsoft guarantees will be available on all Windows locales.

I actually think including the fonts shipped by default in their respective locales actually makes the package more usable by the rest of the world. Shipping only a Gothic font isn't really useful for Japanese users. I'm sure the same applies to users in the other locales.

I'd rather just get this working than argue in the comments. If the maintainer of this packages only wants to include the UWP fonts, I'm happy to make a package that includes the fonts shipped by default in the various locales.

Scimmia commented on 2021-12-07 19:26 (UTC)

Look at the list again, they are NOT the default Japanese fonts on Windows. You seem determined on making this PKGBUILD unusable by the rest of the world, so le me be more blunt. What you expect does not matter. This is how Microsoft ships things, end of story.

And don't point to completely insane PKGBUILDs as an example; if anything, those PKGBUILDs are a prime example of what NOT to do.

smcf commented on 2021-12-07 19:21 (UTC)

I would once again like to stress that the fonts I mentioned are the default Japanese fonts on Windows. They are not part of a FOD package. They are shipped by default on all CJK Windows 11 ISOs.

At any rate, take a look at eg ttf-ms-win8 or ttf-win7-fonts. Both include MS Mincho and MS Gothic. Shipping MS Gothic but not MS Mincho is like shipping Arial but not Times New Roman.

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ttf-win7-fonts https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ttf-ms-win8

« First ‹ Previous 1 2 3 4 5 6 Next › Last »