Package Details: ttf-ms-win11-korean 10.0.26100.2314-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 Korean TrueType fonts
Upstream URL: http://www.microsoft.com/typography/fonts/product.aspx?PID=164
Licenses: custom
Conflicts: ttf-vista-fonts
Provides: ttf-font
Submitter: Vaporeon
Maintainer: Vaporeon (Scimmia)
Last Packager: Scimmia
Votes: 26
Popularity: 0.21
First Submitted: 2021-10-11 13:33 (UTC)
Last Updated: 2024-11-13 00:49 (UTC)

Dependencies (0)

Required by (256)

Sources (142)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6

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

I generally agree, however I would reasonably expect "ttf-ms-win11-japanese" to include the fonts that are shipped on-disc by default by Japanese Windows 11. I would expect at the very least for it to include the default Gothic and Mincho fonts. It wouldn't be very useful to only include only sans-serif fonts for English, don't you agree?

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

darkengine, see https://docs.microsoft.com/en-us/typography/fonts/windows_11_font_list

There's a whole lot of extra fonts included with supplemental FOD packages, there's no way to include them all, and picking and choosing makes little sense.

smcf commented on 2021-12-07 18:03 (UTC)

You actually do not have to run a live install or Windows Update to get the fonts I mentioned. They are included in the Japanese installation ISO, which you can download from the URL mentioned in the PKGBUILD (you just choose Japanese instead of English).

Vaporeon commented on 2021-12-07 17:15 (UTC)

darkengine: This package is intended to track the base fonts installed by all versions of the install media. The fact those fonts are considered "optional features" by MS is rather annoying. Including those fonts would mean a large scope change for this package as we would now hard depend on a running live install and having optional features installed, and it would break peoples use case of extracting the required fonts from any available install media.

One way around this would be to have a secondary package "ttf-ms-win11-full" on the AUR that assumes all optional fonts from windows update are installed.

umaxtu: You are right and that should be changed. I am considering changing the package to have the ability to take the path to the fonts as an environment variable, defaulting to ./Fonts. This way, you could also build the package by passing the path directly to a Windows 11 fonts directory if you have it mounted somewhere on your system, saving the need to copy them.

smcf commented on 2021-12-06 19:31 (UTC)

The ttf-ms-win11-japanese package is missing Meiryo and MS Mincho. They are included on the Japanese Windows 11 installation media, but not the English media. They are important as there is no Ming/Song/Mincho/serif style font in the package without MS Mincho.

The Japanese media includes even more Japanese fonts, but these two are the most important ones. SHA256 sums:

ad98d0f20b138d4bf1720ac4ff7ec7cc3e75154aa5fc3793f290730893e18536  meiryo.ttc
43a5d51a9aec83e3304cd7f0d697d9effe32131a61e85cb7e033451771f2d587  meiryob.ttc
9be3424e24837ef9f07a272e4aea7779b50eeb77a0a23a95bac8e6489624deb6  msmincho.ttc

umaxtu commented on 2021-10-31 16:02 (UTC)

It might be a good idea to make it a bit more clear that the PKGBUILD is intended to be in the same directory as all of the loose, extracted font files. The wimextract command that you provide in the PKGBUILD puts all of the extracted fonts into a fonts sub-directory. It didn't take me more then a minute to troubleshoot, but I doubt I'll be the only person to copy install.wim into the same directory as PKGBUILD and also runs winextract there too.

Scimmia commented on 2021-10-18 23:39 (UTC)

You're wasting your time, sauceorcus. They didn't bother to read it after the error told them to. They didn't bother to read it when the pinned comment in ttf-ms-win10 told them to (they made the same comment there). They aren't going to bother to read it now, either.

<deleted-account> commented on 2021-10-18 20:32 (UTC)

@zeroconf You have clearly not read the PKGBUILD and are just blindly installing AUR Packages. That can be dangerous!

In this case, download the ISO, extract the fonts, download the PKGBUILD and put the fonts in that folder, build and finally install the package.

zeroconf commented on 2021-10-16 11:34 (UTC) (edited on 2021-10-16 11:36 (UTC) by zeroconf)

When trying to install:

==> Retrieving sources...

Unable to find file://*.ttf, please read the PKGBUILD

... will be announced in case of every font. I just replaced font name with asterisk to mention, that it happens in case of every font.

Same happens with checksums:

==> Validating source files with sha256sums... *.ttf ... NOT FOUND

Finally there will be announcement

==> ERROR: One or more files did not pass the validity check! -> error making: ttf-ms-win11

... and installation will be interrupted.

« First ‹ Previous 1 2 3 4 5 6