infinality-bundle: good looking fonts made (even) easier

cfr · 2013-12-30 01:17:34

Thanks. I posted that link as a comment in case it is helpful.

logos88 · 2014-01-01 18:08:18

It looks Fira Sans it's available now, maybe it could be added in the future in the bundle since it's a great font!

http://www.webdesignerdepot.com/2014/01 … -for-free/

Happy new year!

WonderWoofy · 2014-01-01 21:00:38

logos88 wrote:

It looks Fira Sans it's available now, maybe it could be added in the future in the bundle since it's a great font!

Did you actually look through all the available fonts in the infinality-bundle-fonts? It is actually in the infinality-bundle-fonts-extra group, but it is there.

Also, I think that this post would have been better suited in the infinality-bundle-fonts thread.

cdrjameson · 2014-01-03 10:18:59

I've not been able to pacman -Syu for months now. Whenever I try to I get...

(184/184) checking for file conflicts              [######################] 100%
error: failed to commit transaction (conflicting files)
fontconfig-infinality-ultimate: /etc/fonts/conf.d/10-scale-bitmap-fonts.conf exists in filesystem
fontconfig-infinality-ultimate: /etc/fonts/conf.d/30-metric-aliases.conf exists in filesystem
Errors occurred, no packages were upgraded.

I tried removing the packages from /var/lib/pacman/sync as the infinality wiki advises but no luck.

I installed the infinality-ultimate, cairo, and fontconfig packages and added the repos to my pacman.conf, signed the key etc as the OP advised but now I want to completely remove it from my system. When I try

sudo pacman -R freetype2-infinality-ultimate fontconfig-infinality-ultimate cairo-infinality-ultimate

I get a huge list of dependencies.

Please help me update my system.

progandy · 2014-01-03 10:52:54

@cdrjameson: Please remove 10-scale-bitmap-fonts.conf, 30-metric-aliases.conf manually (e.g. with sudo rm), then continue your upgrade.

cdrjameson · 2014-01-03 11:48:17

Edit: I am an idiot, I didn't read you response properly. sudo rm worked a charm.

Thanks for the tip, unfortunately it didn't work. Still not able to upgrade my system.

$ sudo pacman -R 10-scale-bitmap-fonts.conf 30-metric-aliases.conf
[sudo] password for mark: 
error: target not found: 10-scale-bitmap-fonts.conf
error: target not found: 30-metric-aliases.conf

Last edited by cdrjameson (2014-01-03 12:38:01)

mrunion · 2014-01-03 15:28:40

I should have read the previous post closer...

No, remove the files, not the packages:

sudo rm /etc/fonts/conf.d/10-scale-bitmap-fonts.conf
...etc...

To be safe if you're cautious, you may just want to move them somewhere else in case you need them back (for whatever reason).

sudo mv /etc/fonts/conf.d/10-scale-bitmap-fonts.conf /some/safe/place/10-scale-bitmap-fonts.conf.backup
...etc...

Last edited by mrunion (2014-01-03 18:25:51)

bohoomil · 2014-01-04 21:16:37

@cfr: no, I have neither read about nor experienced myself any issues with ghostscript and patched freetype2. However, I am aware of the fact that it is impossible to rule out possible problems with non-standard freetype2 builds: Gimp was the first (?) app reported to malfunction with Infinality patches. I think that in case of problems with Arch libraries in the future, we may always add a custom one to the ib repository (of course, as long as there is a a working fix available like the one mentioned by brebs) in order to make it compatible with the bundle.

progandy · 2014-01-04 21:42:26

bohoomil wrote:

Gimp was the first (?) app reported to malfunction with Infinality patches.

For GIMP, there is always the solution to manually disable subpixel rendering in ~/.gimp-2.8/fonts.conf ( http://pagebin.com/sy1Jgxoo ) or you might want to include this patch in your cairo build: http://lists.cairographics.org/archives … 24240.html
I guess the problem with gimp is not your patchset, but a strange implementation detail in the default cairo, which should also occur with the vanilla versions and subpixel rendering enabled. The linked patch explains this a bit more.

bohoomil · 2014-01-04 23:04:08

progandy wrote:

you might want to include this patch in your cairo build: http://lists.cairographics.org/archives … 24240.html

Thank you very much -- I will take a closer look at it. Right now, cairo-ib comes with 'respect-fontconfig.patch', so I am not sure if the two will not collide. I will prepare a testing package and check it out on my own, though.

Edit: Here are cairo packages with the patch mentioned in progandy's post:

Check them out on your own and if nothing goes wrong, I will make them available via the repo.

Thanks.

Last edited by bohoomil (2014-01-06 20:25:09)

mrunion · 2014-01-05 00:10:01

Is the Drop Box mentioned in post #1 still active? I hit the link and it said nothing was there.

bohoomil · 2014-01-05 00:28:36

mrunion, thanks for reporting -- the link is correct now: Dropbox.

mrunion · 2014-01-05 15:18:06

Ooooh! Thanks! (Now off to enjoy some ultimate fontinality goodness!)

mrunion · 2014-01-06 00:26:56

Downloaded the DropBox repo, set it up locally and installed infinality ultimate. Aahhhh! Thanks, bogoomil!

bohoomil · 2014-01-06 17:12:27

It seems like someone has made good use of Dropbox. Brilliant.

ctarwater · 2014-01-06 18:11:10

bohoomil - I updated to the dropbox packages and am still seeing the same issues with antialiasing in Gimp. Thanks for adding the patch in but for me at least it doesn't seem to make a difference.

bohoomil · 2014-01-06 19:55:53

ctarwater, thanks a lot for your feedback. I noticed something else: the patch seems to decrease sharpness / increase blurriness, so even if it were able to improve Gimp's visual performance, the side effects would come out elsewhere… We are simply going to stick with cairo we have been using: the content of the repository will not change, so you can easily reinstall the library.

Thank you once more for testing.

ctarwater · 2014-01-06 19:56:51

More than happy to test when I can - thanks for looking into it!

progandy · 2014-01-06 21:24:09

ctarwater wrote:

bohoomil - I updated to the dropbox packages and am still seeing the same issues with antialiasing in Gimp. Thanks for adding the patch in but for me at least it doesn't seem to make a difference.

It didn't work for me, either. Maybe I'll create a request to ship gimp with an /etc/gimp/2.0/fonts.conf that disables subpixel rendering for gimp only.

Last edited by progandy (2014-01-06 21:24:36)

doggone · 2014-01-07 19:29:18

Hey bohoomil,

I'm using Noto Sans 10 as my system font. However, it looks wider than when I use it in Firefox, size 12px. If I change the size from 10 to 9, it looks smaller than in Firefox. Is there a way to get the in between?

Here's 12px, the way I want it:

Here's 10 (pt?):

Here's 9:

Last edited by doggone (2014-08-23 22:14:01)

bohoomil · 2014-01-08 00:22:34

progandy, it seems to be the safest solution. We can also add a note to the Wiki so that ib users can easily deal with the problem.

doggone, believe it or not, but Noto Sans is used 'as is', so you can assume that this is the expected default behaviour of the font. (I only needed to modify rendering of the bold weight because otherwise it would be shorter than the regular.) I guess you can try using Noto Sans UI as your system font instead. Currently, there is only one additional instruction in 92-selective-rendering.conf:

<match target="font">
    <test name="family">
      <string>Noto Sans UI</string>
    </test>
    <test name="pixelsize" compare="less">
      <double>10</double>
    </test>
    <edit name="autohint" mode="assign">
      <bool>true</bool>
    </edit>
    <edit name="hintstyle" mode="assign">
      <const>hintfull</const>
    </edit>
  </match>

If the result you get with it is still not what you want, you can simply create one more selective instruction set, say, 93-selective-rendering-noto-ui.conf, and change rendering methods for particular sizes in a similar manner, e.g.:

<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>

<match target="font">
    <test name="family">
      <string>Noto Sans UI</string>
    </test>
    <test name="weight" compare="less_eq">
      <const>regular</const>
    </test>
    <test name="pixelsize" compare="less">
      <double>9</double>
    </test>
    <edit name="autohint" mode="assign">
      <bool>true</bool>
    </edit>
    <edit name="hintstyle" mode="assign">
      <const>hintfull</const>
    </edit>
  </match>

<match target="font">
    <test name="family">
      <string>Noto Sans UI</string>
    </test>
    <test name="weight" compare="less_eq">
      <const>regular</const>
    </test>
    <test name="pixelsize" compare="less">
      <double>10</double>
    </test>
    <edit name="autohint" mode="assign">
      <bool>true</bool>
    </edit>
    <edit name="hintstyle" mode="assign">
      <const>hintfull</const>
    </edit>
  </match>

</fontconfig>

-- switching "hintstyle" to either "hintfull" or "hintslight" and "autohint" to "true" or "false". Default instructions for TrueType fonts are the following:

    <edit name="hintstyle" mode="assign">
      <const>hintfull</const>
    </edit>
    <edit name="autohint" mode="assign">
      <bool>false</bool>
    </edit>

However, bear in mind that modifying default instructions may and probably will affect things like sharpness of particular glyphs, among other things. There is nothing to worry, though: you can always get rid of either the entire file or any of the instructions.

If this is too much pain, you can check out another typeface instead: I have been using Source Sans Pro Regular 9 for quite a long time and I like it very much.

Last but not least: I am currently testing the new infinality-settings.sh (available in the Git repo in freetype subdir). You can grab it and replace the current one in '/etc/profile.d' (back it up first). Maybe it 'cleans' the picture a bit, too.

Last edited by bohoomil (2014-01-08 00:29:11)

demian · 2014-01-08 14:04:51

Hey, just installed infinality for the first time. i feel like the fonts are slightly less sharp now, though.
I mainly use Dejavu Sans <10. And compared to before, font appearance has a hint of blurriness now (a lot of things have improved though so i'd prefer to keep infinality).
Any idea what might cause that and what options i can try to influence that?

Cheers

Last edited by demian (2014-01-08 14:11:39)

bohoomil · 2014-01-08 15:21:01

demian wrote:

fonts are slightly less sharp now

Freetype2 settings had to be changed in order to improve kerning-related stuff… As I am aware of this extra noise,

bohoomil wrote:

I am currently testing the new infinality-settings.sh (available in the Git repo in freetype subdir). You can grab it and replace the current one in '/etc/profile.d' (back it up first).

hamelg · 2014-01-09 19:27:02

Hello bohoomil,

Thank you a lot for your amazing work. I use your repository since 2 days and my eyes enjoy it !

I have some trouble with konsole and some fonts. When viewing manpages, line spacing is sometimes incorrect.

With Terminus font

With Courier font

The rendering is correct with others fonts, like Liberation Mono or inconsolata.

Any suggestion to solve this issue ?

bohoomil · 2014-01-09 20:46:39

Thank you for the feedback. Actually, it seems that the last shot is not correct, too (there is not enough distance between the 2nd and 3rd line). I am not using Konsole by default, but I installed it to check if I could reproduce the issue and the answer was positive. However, nothing like this happens with VTE-based term emulators (I checked lilyterm), URxvt or xterm, so I believe it may be a Konsole exclusive problem. Did you experience anything similar with stock freetype2 and fontconfig?

Arch Linux

#826 2013-12-30 01:17:34

Re: infinality-bundle: good looking fonts made (even) easier

#827 2014-01-01 18:08:18

Re: infinality-bundle: good looking fonts made (even) easier

#828 2014-01-01 21:00:38

Re: infinality-bundle: good looking fonts made (even) easier

#829 2014-01-03 10:18:59

Re: infinality-bundle: good looking fonts made (even) easier

#830 2014-01-03 10:52:54

Re: infinality-bundle: good looking fonts made (even) easier

#831 2014-01-03 11:48:17

Re: infinality-bundle: good looking fonts made (even) easier

#832 2014-01-03 15:28:40

Re: infinality-bundle: good looking fonts made (even) easier

#833 2014-01-04 21:16:37

Re: infinality-bundle: good looking fonts made (even) easier

#834 2014-01-04 21:42:26

Re: infinality-bundle: good looking fonts made (even) easier

#835 2014-01-04 23:04:08

Re: infinality-bundle: good looking fonts made (even) easier

#836 2014-01-05 00:10:01

Re: infinality-bundle: good looking fonts made (even) easier

#837 2014-01-05 00:28:36

Re: infinality-bundle: good looking fonts made (even) easier

#838 2014-01-05 15:18:06

Re: infinality-bundle: good looking fonts made (even) easier

#839 2014-01-06 00:26:56

Re: infinality-bundle: good looking fonts made (even) easier

#840 2014-01-06 17:12:27

Re: infinality-bundle: good looking fonts made (even) easier

#841 2014-01-06 18:11:10

Re: infinality-bundle: good looking fonts made (even) easier

#842 2014-01-06 19:55:53

Re: infinality-bundle: good looking fonts made (even) easier

#843 2014-01-06 19:56:51

Re: infinality-bundle: good looking fonts made (even) easier

#844 2014-01-06 21:24:09

Re: infinality-bundle: good looking fonts made (even) easier

#845 2014-01-07 19:29:18

Re: infinality-bundle: good looking fonts made (even) easier

#846 2014-01-08 00:22:34

Re: infinality-bundle: good looking fonts made (even) easier

#847 2014-01-08 14:04:51

Re: infinality-bundle: good looking fonts made (even) easier

#848 2014-01-08 15:21:01

Re: infinality-bundle: good looking fonts made (even) easier

#849 2014-01-09 19:27:02

Re: infinality-bundle: good looking fonts made (even) easier

#850 2014-01-09 20:46:39

Re: infinality-bundle: good looking fonts made (even) easier

Board footer