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

Perfect Gentleman · 2015-11-30 10:47:29

with update there is no font rendering in Chromium.
what should i do to fix it ?

Last edited by Perfect Gentleman (2015-11-30 16:47:05)

bohoomil · 2015-12-01 04:25:53

Here is a little comparison of built-in rendering styles produced by freetype2-iu rev.2.6.2-3 w/ Infinality patch rev.2015.11.30.

@Perfect Gentleman What exactly do you mean by 'no font rendering'? I am not experiencing any problems with any Web browser I use for testing (Firefox, Chromium, Opera).

Perfect Gentleman · 2015-12-01 05:14:00

in several hours I'll post s-shots of Chromium and FireFox

Ropid · 2015-12-01 06:44:36

I think that 'INFINALITY_FT="custom"' does not work like described. Its description makes it sound like it would disable all features of infinality so that you can then set your own on top of "empty" settings, but this is not what happens for me.

I want this here:

#!/bin/sh
export INFINALITY_FT="custom"
export INFINALITY_FT_FILTER_PARAMS="10 25 37 25 10"
export INFINALITY_FT_FRINGE_FILTER_STRENGTH="25"
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH="25"
export INFINALITY_FT_USE_VARIOUS_TWEAKS="true"

This resulted in something that looked a bit like the "windowsxp" built-in style. It changed the shapes of characters and made vertical stems snap to and fill full pixels. It was especially noticeable for bold fonts.

To get what I really want, I have to set all possible variables to zero manually. I have to do this here:

#!/bin/sh
export INFINALITY_FT_FILTER_PARAMS="10 25 37 25 10"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH="0"
export INFINALITY_FT_FRINGE_FILTER_STRENGTH="25"
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH="0"
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH="0"
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH="25"
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH="0"
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH="0"
export INFINALITY_FT_STEM_FITTING_STRENGTH="0"
export INFINALITY_FT_GAMMA_CORRECTION="0 100"
export INFINALITY_FT_BRIGHTNESS="0"
export INFINALITY_FT_CONTRAST="0"
export INFINALITY_FT_USE_VARIOUS_TWEAKS="true"
export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS="false"
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT="0"
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE="0"
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS="false"

Last edited by Ropid (2015-12-01 06:48:10)

bohoomil · 2015-12-01 07:06:35

Ropid wrote:

I think that 'INFINALITY_FT="custom"' does not work like described.
[...]
To get what I really want, I have to set all possible variables to zero manually. I have to do this here:

infinality-settings.sh wrote:

### 3. Setting the rendering style to "custom" lets you create custom styles
### from scratch. Uncomment the variables below and enter the values
### of your choice.

What isn't clear here?

Ropid · 2015-12-01 08:06:07

bohoomil wrote:

infinality-settings.sh wrote:
### 3. Setting the rendering style to "custom" lets you create custom styles
### from scratch. Uncomment the variables below and enter the values
### of your choice.
What isn't clear here?

I was getting confused because there seems to be no reason for INFINALITY_FT="custom". It seems when you set every single variable, you can have INFINALITY_FT set to any of the styles. The other variables will override the internal settings of any of them. I felt that made no sense so then I thought the reason that the documentation suggests "custom" is because it's intended as some sort of clean slate with all variables set to zero.

Basically, the way it behaves, you can remove the "custom" style option and change the documentation in the file to this:

### 3. You can create custom styles from scratch. Uncomment the variables 
###    below and enter the values of your choice.

Last edited by Ropid (2015-12-01 08:06:31)

Perfect Gentleman · 2015-12-01 11:06:27

@bohoomil
Chromium
Firefox

Honestly, I use Gentoo, but have never had problems before.

 ~ $ grep -i infi <(env)
INFINALITY_FT_BRIGHTNESS=-25
INFINALITY_FT=ultimate5

Last edited by Perfect Gentleman (2015-12-01 11:15:41)

Ropid · 2015-12-01 11:33:37

When I had something similar (changed fonts in one browser but not the other), it was caused by certain fontconfig rules. For some reason, one of the browsers got confused by something in there but the other one did not. I don't remember what I did exactly so don't know what to look out for in the fontconfig files. The rule files that come with infinality-bundle work fine, I think, so it's perhaps one of the files that you wrote yourself or that came in a different package.

If you start Chromium from a terminal window, perhaps it'll print some error messages in there?

bohoomil · 2015-12-01 11:38:52

Ropid wrote:

"custom" is because it's intended as some sort of clean slate with all variables set to zero

This makes sense and actually should work this way. Would you mind filling a bug report with a feature request? I believe it shouldn't be too difficult to implement such a functionality.

Thanks a lot.

Perfect Gentleman · 2015-12-01 11:49:02

@Ropid

 ~ $ chromium
[3664:3683:1201/184435:ERROR:nss_util.cc(853)] After loading Root Certs, loaded==false: NSS error code: -8018
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/va/drivers/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_38
libva info: va_openDriver() returns 0
libpng warning: iCCP: known incorrect sRGB profile
...
libpng warning: iCCP: known incorrect sRGB profile

no errors concerning fonts

bohoomil · 2015-12-01 11:57:55

@Perfect Gentleman That's odd... freetype2 settings are active globally, applications simply use the font rendering engine just like any other subsystem. I wonder if anyone else has experienced this sort of issue?

Perfect Gentleman · 2015-12-01 12:15:17

@bohoomil, I'm rebuilding Chromium, hope that would help.
It didn't help.

Last edited by Perfect Gentleman (2015-12-01 17:14:30)

SpaceCadet · 2015-12-01 20:14:21

bohoomil wrote:

@Perfect Gentleman That's odd... freetype2 settings are active globally, applications simply use the font rendering engine just like any other subsystem. I wonder if anyone else has experienced this sort of issue?

I'm experiencing the same with Google Chrome. On web pages it seems to ignore my infinality settings completely. Strangely enough, the differences *are* visible in the Chrome UI itself (menus, bookmarks, tab titles).

I tested it first by trying out the various INFINALITY_FT presets, and later by setting the variables manually and explicitly setting INFINALITY_FT_BRIGHTNESS="-100" to make my fonts super bold [edited to add: just so I would notice whether it changes anything, not because I like my fonts that way], and none of it made any change to how the fonts were rendered on web pages in Chrome, while on Firefox it made a very noticeable difference.

This is how it looks in Chrome: the webpage text does not get any bolder.
This is how it looks in Firefox, with the same settings: the webpage text gets extremely bold, as expected.

EDIT: I did another test, I downgraded to freetype2-infinality-ultimate-2.6.1-3 and with this version, font rendering is working as expected in Chrome. So something in the change from 2.6.1 to 2.6.2 seems to have triggered this.

Last edited by SpaceCadet (2015-12-01 22:44:08)

bohoomil · 2015-12-02 01:22:25

@SpaceCadet & Perfect Gentleman Thanks for testing and reporting. I managed to reproduce the problem and after installation of the latest upstream freetype2 with the older version of the Infinality patch Chromium is responding properly. I'll file a bug report and once we have a solution, I'll upload the updated library.

Kaan · 2015-12-02 12:32:37

Todays chromium update fixed the font rendering problem for me.

Perfect Gentleman · 2015-12-02 13:26:03

i've updated Chromium too, but still the same problem

bohoomil · 2015-12-02 23:42:08

@Kaan It's a bug. See the relevant thread on GitHub for details.

txtsd · 2015-12-06 10:27:51

Every time there's an infinality update in the repos, powerpill throws invalid signature errors.

pacman -Syyu

is the only thing that fixes it. Is there an issue with timestamps on the sig files, perhaps?

bohoomil · 2015-12-06 11:03:21

@txtsd The signatures for db files are re-generated on every update; pacman pulls updates properly on my machine, and I presume on others' as well. Can anyone confirm similar issues with powerpill (I don't use it myself)?

txtsd · 2015-12-06 11:54:41

bohoomil wrote:

@txtsd The signatures for db files are re-generated on every update; pacman pulls updates properly on my machine, and I presume on others' as well. Can anyone confirm similar issues with powerpill (I don't use it myself)?

pacman says this

┌[txtsd@dungeon-of-data]─[~] [1]                                                                          [15-12-06 17:20:27]
└─▶ pacman -Syu                                                                                                               
error: infinality-bundle: signature from "bohoomil (dev key) <bohoomil@zoho.com>" is invalid
error: infinality-bundle-multilib: signature from "bohoomil (dev key) <bohoomil@zoho.com>" is invalid
:: Synchronizing package databases...
 core is up to date                                  0.0   B  0.00B/s 00:00 [-------------------------------------------]   0%
 extra is up to date                                 0.0   B  0.00B/s 00:00 [-------------------------------------------]   0%
 community is up to date                             0.0   B  0.00B/s 00:00 [-------------------------------------------]   0%
 multilib is up to date                              0.0   B  0.00B/s 00:00 [-------------------------------------------]   0%
 infinality-bundle is up to date
 infinality-bundle-multilib is up to date
 repo-ck is up to date
error: database 'infinality-bundle' is not valid (invalid or corrupted database (PGP signature))
error: database 'infinality-bundle-multilib' is not valid (invalid or corrupted database (PGP signature))

Running pacman -Syyu will download the new sig files, but I want to figure out why it isn't working normally for me, if it's working for you.

I've got these options set for the infinality repos. Same as the official repos.

[infinality-bundle]
SigLevel = PackageRequired DatabaseOptional
Server = http://bohoomil.com/repo/$arch

[infinality-bundle-multilib]
SigLevel = PackageRequired DatabaseOptional
Server = http://bohoomil.com/repo/multilib/$arch

This should be all it needs to fetch the sigs whenever they're updated, correct?

bohoomil · 2015-12-06 12:05:53

Try these:

SigLevel = Required DatabaseOptional TrustedOnly
LocalFileSigLevel = Optional

txtsd · 2015-12-06 12:31:11

bohoomil wrote:

Try these:

SigLevel = Required DatabaseOptional TrustedOnly
LocalFileSigLevel = Optional

warning: config file /etc/pacman.conf, line 102: directive 'LocalFileSigLevel' in section 'infinality-bundle' not recognized.

bohoomil · 2015-12-06 12:34:33

Use them globally.

txtsd · 2015-12-06 12:40:47

bohoomil wrote:

Use them globally.

That did the trick! Thanks!

madigens · 2015-12-06 14:02:57

Hi!
I'm the guy who might have broken your font rendering prior to the 2.6.2 release. I'm looking at the Infinality patches to salvage stuff for mainline integration since the original author vanished. I stumbled over this thread and wanted to clear up some misunderstandings: the sudden bold/thin fonts have nothing to do with the filter but with other things, please read my post on the 2.6.2 release on www.freetype.org :)

PS: Before anyone asks, I'm mainly interested in the autohinter changes and the TrueType interpreter v38 implementation. If anyone wants to help, please seek the nearest freetype-devel mailing list :)

Arch Linux

#1801 2015-11-30 10:47:29

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

#1802 2015-12-01 04:25:53

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

#1803 2015-12-01 05:14:00

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

#1804 2015-12-01 06:44:36

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

#1805 2015-12-01 07:06:35

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

#1806 2015-12-01 08:06:07

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

#1807 2015-12-01 11:06:27

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

#1808 2015-12-01 11:33:37

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

#1809 2015-12-01 11:38:52

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

#1810 2015-12-01 11:49:02

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

#1811 2015-12-01 11:57:55

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

#1812 2015-12-01 12:15:17

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

#1813 2015-12-01 20:14:21

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

#1814 2015-12-02 01:22:25

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

#1815 2015-12-02 12:32:37

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

#1816 2015-12-02 13:26:03

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

#1817 2015-12-02 23:42:08

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

#1818 2015-12-06 10:27:51

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

#1819 2015-12-06 11:03:21

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

#1820 2015-12-06 11:54:41

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

#1821 2015-12-06 12:05:53

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

#1822 2015-12-06 12:31:11

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

#1823 2015-12-06 12:34:33

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

#1824 2015-12-06 12:40:47

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

#1825 2015-12-06 14:02:57

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

Board footer