Arch linux шрифты microsoft

Arch Linux User Repository

Please refrain from posting links to the font files required to build this package. Microsoft fonts are protected by copyright and neither we nor you are allowed to distribute them. This package only provides an approach to cleanly integrate the fonts into an Arch Linux system provided that you have a licensed copy of Windows 10. Otherwise you can use the ttf-ms-fonts package to install publicly available fonts. If you post comments intending to distribute the fonts via this page we need to contact administrators in order to remove your comment.

Latest Comments

Scimmia commented on 2021-10-20 16:57 (UTC)

For the last 4 people that commented, make sure to read the FAQ in the pinned comment.

Stane1983 commented on 2021-10-20 09:08 (UTC)

Inkfree.ttf checksum is wrong on latest Win10 install media.

8b89481f274ee1ad6fe49f539fc4435e114bc684beecb3fdafd6c7817bd05d85 checksum should be replaced with f23225869ceb58b78a836b84207d1726cc5d9c3f5fe2ae8a295ff62a98df09a0 .

bakgwailo commented on 2021-10-19 04:00 (UTC)

using the latest install media (Win10_21H1_English_x64.iso)

wszqkzqk commented on 2021-10-18 07:11 (UTC)

Deng.ttf , Dengl.ttf and Dengb.ttf may need to be added to package ttf-ms-win10-zh_cn

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

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-win10

. and installation will be interrupted.

ttf-ms-win10-auto is outdated for now.

Zepman commented on 2021-02-24 16:52 (UTC) (edited on 2021-04-08 12:03 (UTC) by Zepman)

For anyone who wants to try an automated download, please try ttf-ms-win10-auto. It downloads the fonts from Microsoft, and it does not download an entire ISO unless it needs to.

barkley128 commented on 2021-02-23 16:30 (UTC)

I understand I can disable updating it, e.g. using /etc/pacman.conf, my helper reads it. I was more curious what do these updates add? Is it more/different fonts upon Windows updates?

neo2001 commented on 2021-02-23 11:15 (UTC)

Well, you don’t need to update.

I’m no expert, but I guess if the checksums for the fonts would be in another file and then sourced, it would work. But then this file’s checksum will change and needs to be ignored.

You could simply checkout the package from the AUR using git and then change the package name, so AUR helpers won’t try to find updates for it. Then you can control when and if you want to update the font files.

barkley128 commented on 2021-02-23 08:14 (UTC)

Thank you, but why do packages like this one even update? It’s a bit annoying to copy fonts again and again.

kode54 commented on 2021-02-23 01:56 (UTC)

Sorry, I should have looked at the script before I posted. I didn’t realize the Enterprise Trial ISO that was linked in the posted PKGBUILD was on a permanent link. Certainly, that could save users (and Microsoft) a lot of bandwidth if it were dynamically mounted to access the Install.wim inside, and only extract specific files from it, rather than copying it entirely to the local filesystem.

Assuming, of course, that this particular permanent link allows random access. Worth a shot, though.

I do know I won’t be using the download-ISO version for my own installs, since I keep a handy Windows 10 Pro for Workstations installation on my machine, and the fonts from it also match the PKGBUILD hashes. Doesn’t mean it’s not useful to actually become a stand-alone self-sufficient script that doesn’t require manual intervention.

Copyright © 2004-2023 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник

Arch Linux User Repository

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=(«$») :

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

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:

==> 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! 

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

Copyright © 2004-2023 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник

Microsoft fonts

This article explains how to install TrueType Microsoft fonts and emulate Windows’ font rendering.

Installation

Automatic Installation

Note: These automatically fetch the Windows Enterprise 90-day evaluation edition and extracts the required fonts from it.

The easiest way to install the fonts is by installing one of the following:

Using fonts from a Windows partition

If there is a Windows partition mounted, its fonts can be used by linking to them. It may be necessary to apply a workaround for system compressed files in order to read the font files.

For example, if the Windows C:\ partition is mounted at /windows :

# ln -s /windows/Windows/Fonts /usr/local/share/fonts/WindowsFonts

Then regenerate the fontconfig cache:

Alternatively, copy the Windows fonts to /usr/local/share/fonts/ :

# mkdir /usr/local/share/fonts # mkdir /usr/local/share/fonts/WindowsFonts # cp /windows/Windows/Fonts/* /usr/local/share/fonts/WindowsFonts/ # chmod 644 /usr/local/share/fonts/WindowsFonts/*

Then regenerate the fontconfig cache:

# fc-cache --force # fc-cache-32 --force

Extracting fonts from a Windows ISO

The fonts can also be found in a Windows ISO file. The format of the image file containing the fonts in the ISO is either WIM (Windows Imaging Format) if the ISO is downloaded online or ESD (Windows Electronic Software Download) if it is built with Windows’ Media Creation Tool. Extract the sources/install.esd or the sources/install.wim file from the .iso and look for a Windows/Fonts directory within this file. It can be extracted using 7z (in p7zip) or wimextract (in wimlib ). See an example below using 7z:

$ 7z e WinXY_YYMM_English_x64.iso sources/install.wim $ 7z e install.wim 1/Windows/,System32/Licenses/neutral/"*"/"*"/license.rtf> -ofonts/

The fonts and the license will be located in the fonts directory.

Current packages

Note: These packages do require access to a Windows and/or Office 2007 setup or installation media. Consult the corresponding PKGBUILDs for details.

• ttf-office-2007-fontsAUR — Office 2007 fonts
• ttf-win7-fontsAUR — Windows 7 fonts
• ttf-ms-win8AUR — Windows 8.1 fonts
• ttf-ms-win10AUR — Windows 10 fonts
• ttf-ms-win11AUR — Windows 11 fonts

Legacy packages

Note: The fonts provided by these packages are out-of-date and are missing modern hinting instructions and the full character sets. It is recommended to use the above packages.

Warning: According to original Microsoft’s End User License Agreement, there are some legal limitations when using the above fonts.

You can also obtain ttf-tahoma AUR which, as you might expect, contains Tahoma.

Fontconfig rules useful for MS Fonts

Rule mapping for similar fonts

Often websites specify the fonts using generic names (helvetica, courier, times or times new roman) and a rule in fontconfig maps these names to free fonts (Liberation, Google CrOS, GUST TeX Gyre. ). The substitutions are defined in /etc/fonts/conf.d/30-metric-aliases.conf .

To make full use of the Ms Windows fonts it is necessary to create a rule mapping those generic names to the Ms Windows specific fonts contained in the various packages above:

    Helvetica Arial   Times Times New Roman   Courier Courier New    

It is also useful to associate serif,sans-serif,monospace fonts in your favourite browser to MS fonts.

Disable embedded bitmap fonts

Some Microsoft TTF fonts such as Calibri and Cambria contain embedded bitmap fonts for specific font sizes, which are not anti-aliased. If embedded bitmaps are enabled, the fonts are not anti-aliased at those specific sizes. Embedded bitmap fonts can be disabled in the Font configuration:

Known issues

Symbols not displaying properly with Poppler-based PDF readers

The TrueType Microsoft font for Symbol (Wikipedia:Symbol (typeface)) are buggy with Poppler, math symbols may not display correctly in Poppler-based PDF readers.

Источник