Package Details: fontconfig-infinality 2.13.1+12+g5f5ec56-1

Git Clone URL: (read-only, click to copy)
Package Base: fontconfig-infinality
Description: A library for configuring and customizing font access, optimized for freetype2-infinality.
Upstream URL:
Licenses: custom, MIT
Conflicts: fontconfig, fontconfig-infinality, fontconfig-infinality-git, fontconfig-infinality-ultimate-git
Provides: fontconfig=$pkgver, fontconfig-infinality, fontconfig-infinality-ultimate
Replaces: fontconfig-iu-comp
Submitter: Shanto
Maintainer: SolarAquarion
Last Packager: SolarAquarion
Votes: 310
Popularity: 0.000003
First Submitted: 2011-12-24 23:30
Last Updated: 2019-05-30 01:59

Required by (1000)

Sources (8)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

ValdikSS commented on 2015-09-02 19:59

@ventieldopje, it seems that with the latest package I get proper rendering on github but still the fonts are ugly here and there. That old styles @iuseakeyboard mention are still actual, I don't see any point removing it for the sake of -ultimate. These are different projects and I have chosen non-ultimate version a long time ago mostly because I couldn't configure ultimate version to render fonts as good as I get even with stock non-ultimate configuration.

Just to be clear, this is only fontconfig issue and not freetype2. Right now I'm using "old" fontconfig-infinality and new freetype2-infinality.

I'd like this package to use original files.

Anonymous comment on 2015-09-02 19:32

All I know is, I has pretty fonts ;)

Anonymous comment on 2015-09-02 19:32

Well, fine but it would be appreciated if you put in some effort to supply me with the previously mentioned things so we can have a look at what is causing it. By the looks of it there are still residues of the old package on your system, hence you see the old presets (which are in as mentioned before). Can't help you this way I'm afraid.

iuseakeyboard commented on 2015-09-02 19:25

He got rid of the lowly "imitation" presets, added some other patches, in short changed the recipe. Anyway I'm tired of this. I'll use the official version until I get a rendering problem, block this update and have a copy of the files whenever I install arch.

Anonymous comment on 2015-09-02 19:17

@iuseakeyboard, those are the old styles and are probably leftovers on your system (or you're using the old package). This new package has three styles: free, ms, combi.

Anonymous comment on 2015-09-02 19:15

Define 'broken', people are telling me it 'broke' their font rendering but fail to respond to any questions regarding to what steps they have taken and what configuration they use.

If you read all info on that page and get to the point where he sums them up (point 1 till 3):

"It is a single software package which comes complete with both stock fontconfig libraries and Infinality related configuration files. As a drop-in replacement for fontconfig, fontconfig-infinality-ultimate offers exactly the same functionality and is 100% compatible with the original."

For this package specifically, no code changes have been made other than the inclusion of Infinality specific configuration files. The code is the original fontconfig, nothing has changed there. Freetype is the package that has code changes and has the infinality patch applied.

So please, before we continue this endless discussion. If something is broken I'm more than happy to have a look how to fix it. I can't do anything until you provide me with the proper information, at least: steps taken, custom configuration, fonts used, screenshots. None of this has been provided yet. Not to mention we're not even sure the apparent problems are related to fontconfig, freetype or cairo.

iuseakeyboard commented on 2015-09-02 19:10

@ventieldopje, do you have these presets?

Select a style:
1) debug 3) linux 5) osx2 7) win98
2) infinality 4) osx 6) win7 8) winxp

iuseakeyboard commented on 2015-09-02 18:58

@ventialdopje here is what bohoomil writes about the original package:

"Paradoxically, the excessive number of presets demonstrating the enormous adaptability of the patchset, led to overestimation of the models and marginalization of the patchset’s own superiority over many of them."

Dude has serious philosophical differences with the whole preset thing. He also mentions adding some other patches and stuff, which could explain why some people's setup got broken.

Anonymous comment on 2015-09-02 18:46

I think it's a matter of reading the README and using fc-presets to set a preset. I use it myself and it works flawlessly so I wouldn't say it's broken. Can't say really until more is known about the configuration and steps taken.

graysky commented on 2015-09-02 18:12

Is consensus that 2.11.94-2 still gives broken systems?