Package Details: fonts-meta-extended-lt 4-1

Git Clone URL: https://aur.archlinux.org/fonts-meta-extended-lt.git (read-only, click to copy)
Package Base: fonts-meta-extended-lt
Description: Extended font collection meta package, ported from Infinality (lite version).
Upstream URL: https://web.archive.org/web/20160703182257/http://bohoomil.com:80/doc/05-fonts/
Licenses: GPL
Conflicts: ibfonts-meta-extended-lt, xorg-fonts-type1
Provides: ibfonts-meta-extended-lt, xorg-fonts-type1
Replaces: xorg-fonts-type1
Submitter: jurf
Maintainer: CommodoreCrunch
Last Packager: CommodoreCrunch
Votes: 92
Popularity: 0.000014
First Submitted: 2017-01-08 15:58 (UTC)
Last Updated: 2022-05-28 19:51 (UTC)

Pinned Comments

jurf commented on 2017-01-28 09:28 (UTC)

Please do not report installation problems with AUR font packages here! I do not maintain them, if you want it fixed, report it to the respective maintainers.

Latest Comments

1 2 3 4 5 Next › Last »

nTia89 commented on 2024-03-27 06:22 (UTC) (edited on 2024-03-27 06:23 (UTC) by nTia89)

@MarsSeed this package no longer enable Infinality feature (that as you said, it has been deprecated!) but sets fonts substitution: as you can see, the 30-infinality-aliases.conf file contains "override" rules for family font, that is use font XYZ for serif font family. Thus, this package (as it's "father" fonts-meta-base) is still relevant.

PS: I agree for the fact it/they need to be updated...

MarsSeed commented on 2024-03-26 23:22 (UTC)

This 'kind-of' metapackage with Infinality related additional alias configs is no longer useful.

Because Infinality rendering modes are no longer supported by current version of freetype2.

Upstream removed the Infinality engine a year ago, after 10 years of no development and due to being buggy.

xiota commented on 2023-09-20 07:14 (UTC) (edited on 2023-10-15 03:29 (UTC) by xiota)

Please remove replaces directive. Not appropriate to attempt to override packages in official repositories.

nTia89 commented on 2020-10-28 10:10 (UTC)

I encountered a PDF issue described here [https://askubuntu.com/questions/1031235/wrong-letter-positioning-and-font-in-pdf-form/1286570] that I successfully fixed following the @Xiota answer; if other users loving former infinality config like me found this trick good, I suggest to add this font substitution here (since Nimbus is included in the GSfonts package that is a dependency here).

~/.config/fontconfig/conf.d/10-pdf-aliases.conf

  <?xml version="1.0"?>
  <!DOCTYPE fontconfig SYSTEM "/etc/fonts/conf.d/fonts.dtd">
  <fontconfig>

  <alias binding="same">
    <family>CourierStd</family>
    <accept>
    <family>Courier</family>
    </accept>
  </alias>

  <alias>
    <family>CourierStd</family>
    <default><family>monospace</family></default>
  </alias>

  </fontconfig>

Let keep this project alive!

andrewkoz commented on 2018-05-18 01:32 (UTC)

Before installing note that the link is down for the ttf-impallari-cantora zip file, however it is available here:

http://web.archive.org/web/20150719101220if_/http://www.impallari.com/media/uploads/prosources/update-67-source.zip

CommodoreCrunch commented on 2018-05-16 20:26 (UTC)

@jurf Hooray. Apparently he's going to add build instructions so I'll wait on that rather than making a mess of the PKGBUILD.

jurf commented on 2018-05-16 14:35 (UTC)

BTW, Gelasio is now (finally!) available on GitHub: https://github.com/EbenSorkin/Gelasio

nTia89 commented on 2017-12-24 18:04 (UTC)

should 'font-bh-ttf' be added as dep, since alias.conf file uses it?

rashkov commented on 2017-12-21 01:36 (UTC)

you are doing gods work. thank you! my eyes feel so much better.

I am surprised that Arch's general recommendations guide doesn't recommend this package. They just point you to the fontconfig wiki as if people are capable of curating a set of fonts and adding freetype configurations! It used to recommend people use infinality, but it should definitely recommend this instead.

Thank you again.

CommodoreCrunch commented on 2017-10-08 21:37 (UTC)

Mostly I haven't created packages for them because I haven't found a remote source that's trustworthy, includes a copy of the license, and is possible to pull from. But come to think of it, if they're licensed under the OFL anyway, I could just stick them on my GitHub.