Package Details: ttf-ms-fonts 2.0-12

Git Clone URL: https://aur.archlinux.org/ttf-ms-fonts.git (read-only, click to copy)
Package Base: ttf-ms-fonts
Description: Core TTF Fonts from Microsoft
Upstream URL: http://corefonts.sourceforge.net
Keywords: corefonts
Licenses: custom:microsoft
Provides: ttf-font
Submitter: None
Maintainer: alerque
Last Packager: alerque
Votes: 2122
Popularity: 6.48
First Submitted: 2010-12-01 11:17 (UTC)
Last Updated: 2020-05-25 15:35 (UTC)

Dependencies (0)

Required by (293)

Sources (11)

Latest Comments

1 2 3 4 5 6 .. 16 Next › Last »

jongeduard commented on 2023-05-30 00:29 (UTC) (edited on 2023-05-30 00:34 (UTC) by jongeduard)

Hi!

Just as a suggestion, isn't it a better idea to use https://www.freedesktop.org/software/fontconfig/webfonts/webfonts.tar.gz as a source URL and let the script unpack that? Seems more reliable to me, since it's the Freedesktop foundation. And contains the exact same thing if you ask me.

I came accross this link by browsing via https://www.freedesktop.org/wiki/Software/fontconfig/ and then towards https://www.freedesktop.org/wiki/Software/fontconfig/ after searching some information about fontconfig.

That last URL is also the place serving the license that they ask you to read first, https://www.freedesktop.org/software/fontconfig/webfonts/Licen.TXT

So they do it in the right way.

duzun commented on 2020-09-13 11:14 (UTC) (edited on 2020-09-13 11:15 (UTC) by duzun)

The issue is in that SourceForge has changed the behaviour of the download links and no longer redirect to the binaries on curl. I've inserted the following in the PKGBUILD after source=("${_files[@]/#/$_dlpath/}"):

idx=0
for i in "${source[@]}"; do 
    source[idx]="$i?ts=$(date +%s)&use_mirror=deac-ams"
    idx=$(( idx + 1))
done

And it worked!

The mirron "deac-ams" is from https://sourceforge.net/p/forge/documentation/Mirrors/

alerque commented on 2020-08-31 21:00 (UTC)

@micronetic That's proof that the package and its checksums are doing their job and flagging invalid downloads. The problem here is Source Forge's download mirror system. The issues are highly mirror (and hence region) dependent with some having more strict rate limiting and such than others. There isn't really anything this package can do about this.

micronetic commented on 2020-08-31 10:32 (UTC) (edited on 2020-08-31 10:37 (UTC) by micronetic)

@caleb I had the same problem as @ginkel yesterday but today it is working again.

alerque commented on 2020-08-31 07:19 (UTC)

@ginkel The upstream source files haven't changed since 2002. I suspect you had trouble downloading them all at once from some SourceForge mirror. Try downloading them one at a time using wget or even from a browser and placing them in the sources folder. The checksums should be right when you get valid files.

b3n10 commented on 2020-08-30 07:09 (UTC)

@ginkel my only failed download is webdin32.exe, but i changed the _dlpath to https://sourceforge.net/projects/corefonts/files/the%20fonts/final and afterwards it downloads that file for me and proceed installation

ginkel commented on 2020-08-29 11:19 (UTC) (edited on 2020-08-29 11:20 (UTC) by ginkel)

Since two days, installing the package fails with the following error:

-- 8< --

==> Validating source files with sha256sums...
    andale32.exe ... FAILED
    arial32.exe ... FAILED
    arialb32.exe ... FAILED
    comic32.exe ... FAILED
    courie32.exe ... FAILED
    georgi32.exe ... FAILED
    impact32.exe ... FAILED
    times32.exe ... FAILED
    trebuc32.exe ... FAILED
    verdan32.exe ... FAILED
    webdin32.exe ... FAILED
==> ERROR: One or more files did not pass the validity check!

-- 8< --

Did the upstream files change?

danisztls commented on 2020-08-02 13:20 (UTC)

I had the same problem as Stunkymonkey.

alerque commented on 2020-06-08 06:03 (UTC)

@Stunkymonkey That doesn't sound like a packaging issue, this package is just extracting and installing the upstream archive files. Incidentally while the download path changes the actual version of the files used hasn't changed in quite some time. It sounds like your issue is either with some font in the upstream project or ever your usage of them. Fonts don't declare characters you know, they just have a table of glyphs for them. It's up to you to specify which font you want your characters from.

Stunkymonkey commented on 2020-06-07 22:12 (UTC)

the latest updates added some strange characters 0xF015 was declared by font-awesome before is now a weird tilde. Is this expected? Because 0xF015-0xF01D and 0xF02D-0xF030 are nearly all the same character

1 2 3 4 5 6 .. 16 Next › Last »