Font rendering in certain GTK+ 3 applications

In some GTK+ 3 applications, fonts appear to have a slightly reddish fuzz and seem a bit unclear; this does not differ by font, so I'm assuming it's a font rendering issue. Is there any known solution to this? I searched around a bit and couldn't find anything.

Pse wrote:Hmm, looks like the wrong LCD filter is getting picked. What desktop environment are you on? I take it it is not Gnome, is it?
It's just the default one; I'm using GNOME 3.10.
genghizkhan91 wrote:Are you using the infinality packages?
No; just plain fontconfig/freetype2.
Regular font rendering settings are being used (fully antialiased, slight hinting, rgba, default lcd filter, etc.)
Edit: Also, note that this issue had been present in several other applications but disappeared recently after certain upgrades; for instance, fonts were similarly fuzzy in the "About" section of most GTK+ 3 applications and the "Notifications" section of GNOME Control Center.
Last edited by rainbowdashc (2014-03-30 14:16:07)

Similar Messages

Font rendering and legacy X applications

For some time, I have had problems keeping older applications working well as the X font system evolves. For example, I have many drawings created in Xfig, and the fonts stopped being rendered correctly some time ago. Converting all these files for a new drawing package like Inkscape would be a pain. The other main problem occurs with a commercial CAD package (Eagle), which is statically linked to Qt2, and does not play nicely when anti-aliasing is applied to Qt3/KDE apps.
Xfig and others
The problem here is that Xfig would render fonts with the letters too closely spaced, such that the on-screen representation no longer matches the printed or PDF output. I fixed this by forcing 75 x 75 DPI resolution, rather than using the resolution determined by the X server from probing the monitor. To do this, put a line in the Monitor section of XF86Config or xorg.conf:
DisplaySize 433 347
The above x and y values were calculated for a resolution of 1280 x 1024.
Another fix I have done for Xfig is to patch the sources to pick up the URW font names instead of the Adobe names for the standard Postscript fonts. If anyone is interested, I could make a proper Arch package for this.
Forcing the resolution is admittedly a kludge. I might look into font rendering in an Xlib application, to see if there is some extra code needed to handle the proper resolution correctly.
Gtk-2.0 UI fonts at 75DPI
An unfortunate side effect of forcing 75 x 75 DPI resolution is that the menu and other UI fonts in Gtk apps end up too small. This was noticed on Gvim and Gnumeric. KDE and Qt programmes appear to be unaffected. This can be fixed by creating a .gtkrc-2.0 file in your home directory with the following contents:
gtk-font-name = "Bitstream Vera Sans 12"
Put whatever font and size you like. I have no information on the format of the gtkrc file. The above was adapted from a page found on Google.
Mozilla (which uses Gtk) needs some individual tweaking, as the UI fonts end up far too big. In preferences->fonts, set the resoultion to 72 DPI.
The above measures should only be required if you have forced 75DPI. I had no problems with Gtk apps prior to doing that.
Eagle
The problem with Eagle appears to be related to the fact that it uses Qt2 (statically linked) in a Qt3 environment. This might also occur with other apps, but Eagle is the only one I know about. When antialising is turned on via KDE control center, this modifies .qt/qtrc, and so affects all Qt applications. If I have anti-aliasing turned on, the fonts in Eagle are very ragged and badly spaced.
I fixed this by modifying the font path in XF86Config, to remove the entry /usr/X11R6/lib/X11/fonts/TTF. The problem appears to be that Eagle is picking up one of the True Type fonts, instead of a Type 1 or bitmapped font. Turning on antialing in Qt appears to alter its font selection behaviour (fontconfig?) as well as font rendering.
An interesting outcome of experimenting with the font path is that removing entries only affects older applications. KDE and other modern apps work perfectly well with only the mandatory /usr/X11R6/lib/X11/fonts/misc entry present. As far as I know, this is because modern toolkits like Qt3 and Gtk2 use fontconfig to find fonts.

I now made two screenshots of Mail: The first one while the external display was disconnected, the second one when it was connected (and Mail moved to the external display). I opened both screenshots in Photoshop and there was a clear difference between the font renderings: On the screenshot of the internal display, the fonts are smoothed with black and grey pixels only, while on the screenshot from the external display they are smoothed with colored pixels. This is the reason why the text looks so bad on the external one. Therefore, it is definitely a problem of the font rendering. In Photoshop, the difference of font rendering is clearly visible!
See here:
http://img208.imageshack.us/img208/5389/fontt.jpg
The first line is internal display, the second line external display. That's unbelievable.
Another thing: I found out that it's not only Mail that has the problem - it is any application that was started after the external display had been connected. It seems that OS X applies the font rendering setting at the moment a application is starts. When I disconnect the display, start Finder, Mail, Safari and so on, and then connect the display, then all the applications look great even on the external display. When I quit the apps and then restart, the font rendering is broken again

Font rendering differences between Xfce and KDE

Hi,
I am using both KDE and Xfce (mostly Xfce with KDE apps) and I observed that there is a font rendering difference between Gtk (Xfce) and QT (KDE) apps.
In both desktop environments I use dejavu sans font, size 9 and I have set RGB subpixel rendering and hinting to full.
I created some screenshots of dolphin and thunar to illustrate the differences (right click and select view image to see the screenshots in full resolution)
Can somebody help me to make gtk app fonts to look the same as qt ones? Or at least tell me why there is this difference.
Thank you.

I cant tell you why there is a difference, but this page may help you. https://wiki.archlinux.org/index.php/Font_Configuration
I ended up installing the Ubuntu patched packages in the AUR, but there are different options.

Firefox/Thunderbird Font Rendering changed after upgrade of xulrunner

Hi guys,
I experienced a problem with font rendering in the mentioned applications after upgrading xulrunner from 1.9.2.10-1 to 1.9.2.10-2 today. It seems like font smoothing/subpixel rendering does not work as before. After downgrading to 1.9.2.10-1, it worked as expected again.
To make it more clearly, here is a comparison shot of the two different renderings. The top one is before, the bottom one after the upgrade. You can see that the font at the top is rendered more smoothly.
And here is a difference image:
Is anything known about changes which could cause this?
<edit>I have to correct this. The rendering in thunderbird was obviously not changed by the xulrunner upgrade, but by a separate thunderbird upgrade from 3.1.4-1 to 3.1.4-2.
<edit2>Additional information: I have the cleartype versions of freetype2, cairo and libxft installed, if that matters.
Last edited by Singul (2010-09-28 16:40:18)

Although I am empathetic to the hard (and really great) job the arch devs do, I want to voice my overall agreement with softtower on this issue. Fonts have been an off and on problem for me with arch since the beginning. I understand the devs are doing the best they can, especially when the actual problem is with the moz. devs. But fonts are the major way most users interact with the system, and I can tell you that almost nothing is more aggravating, to me at least, to suddenly "upgrade" and get presented with those really crappy fonts out of the blue. Just saying I understand the frustration, and I think he makes some good points about shipping broken packages and "blaming" it on upstream. If they're broken - don't use them! if possible. "Progress" that breaks stuff isn't really progress, imo.
hokasch wrote:
Don't quite get what the fuzz is all about, my fonts look as crisp as ever (on a laptop lcd), the update changed absolutely nothing for me. I never used "fixed" versions of anything, can't really remember how I set up the fonts when I did this installation though (font config advice on the wiki I guess).
It is not the repo's maintainers job to keep packages synced up with any "fixed" packages in AUR, that is your own responsibility, and bitching about it won't help you any.
Just pointing out that comments like these aren't really helpful, imho. So you didn't have the problem - that's good to know, but the "fuzz" is about the fact that some of us *DO* have the problem.
It typically doesn't show up on laptops, btw, only standalone LCDs for some reason (has always been the case for me, at least, with both LCDs and laptops, where the laptop never had the problem). So again, the fuss is that a major usability function got broken from an upgrade that shouldn't get broken, and imo it raises some good, if admittedly difficult to resolve, points, philosophical points, etc. about the packaging and upgrade process,

Font rendering in GTK

I am having sporadic font issues with GTK applications. Example:
http://i.imgur.com/wJa2839.jpg
There is no identifyable trigger, but it appears to be universal (e.g. pidgin is currently displaying the same types of black boxes). Additionally, in GTK lists, some items disappear (e.g. some of my folder names in Sylpheed go missing) until I move the cursor and trigger some sort of tooltip.
I'm running the Enlightenment desktop from the official packages and no other obvious potential patches / apps that I can investigate.
21:14:50(Fri!) an ~> locale
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
-- mod edit: converted oversized image to url. Trilby --
Last edited by Trilby (2014-11-01 02:14:20)

Hello, a few weeks ago I installed kde and when I open firefox- only occurs in firefox ( no google-chrome)- this happens to me in some characters::
At first I thought it was a matter of rendering fonts, I have installed infinality-bundle, I made a comment in the thread bohoomil:
https://bbs.archlinux.org/viewtopic.php?id=162098&p=57
..... this told me that he believed that this is issue drivers not rendering fonts ... I do not know exactly why this problem occurs , it may be a problem of firefox with drivers "mesa" (Open Source Drivers) .
My graphic card and drivers card is:
[hector@archkde ~]$ inxi -Gx
Graphics: Card: Advanced Micro Devices [AMD/ATI] Bonaire XTX [Radeon R7 260X]
bus-ID: 01:00.0
Display Server: X.Org 1.16.1 drivers: ati,radeon Resolution: [email protected]
GLX Renderer: Gallium 0.4 on AMD BONAIRE
GLX Version: 3.0 Mesa 10.3.2 Direct Rendering: Yes
I try dissabiling "Hardware Aceleration" in Firefox and customize the values to graphic card (20-radeon.conf).. but unfortunately this did not work ...
Note: I think most cases occurs :
https://bbs.archlinux.org/viewtopic.php?id=189180
Best Regards.
Last edited by colegui (2014-11-01 06:27:48)

[NEARLY SOLVED] font rendering in gtk apps problem after last upgrade

Im' using KDE, cairo-lcd, libxft-lcd... my fonts looked beautifully, but now they look horrible...
After last upgrade my gtk apps (firefox, thunderbird) render fonts in an ugly way...
I've tried to revert to pango 1.16.5 with no lucky result (the same problem)...
here is the log:
[2007-08-19 14:56] upgraded bind (9.4.1_P1-2 -> 9.4.1_P1-3)
[2007-08-19 14:56] upgraded glib2 (2.14.0-2 -> 2.14.0-3)
[2007-08-19 14:56] upgraded gnupg2 (2.0.5-1 -> 2.0.6-1)
[2007-08-19 14:57] upgraded gtk2 (2.10.14-2 -> 2.10.14-3)
[2007-08-19 14:57] upgraded kernel26ck (2.6.22.2.ck1-1 -> 2.6.22.3.ck1-1)
[2007-08-19 14:57] upgraded libdownload (1.1-1 -> 1.1-2)
[2007-08-19 14:57] upgraded libevent (1.3b-1 -> 1.3d-1)
[2007-08-19 14:57] upgraded libxtst (1.0.2-1 -> 1.0.3-1)
[2007-08-19 14:57] upgraded nvidia-ck (100.14.11-2 -> 100.14.11-3)
[2007-08-19 14:57] upgraded sip (4.6-1 -> 4.7-1)
[2007-08-19 14:57] upgraded pyqt (3.17.2-1 -> 3.17.3-1)
[2007-08-19 14:57] upgraded xf86-input-joystick (1.2.2-1 -> 1.2.3-1)
[2007-08-19 14:57] upgraded xorg-server-utils (1.0.4-1 -> 1.0.4-2)
[2007-08-19 14:57] upgraded xorg-utils (1.0.2-2 -> 1.0.2-4)
[2007-08-19 14:57] upgraded xorg-xdm (1.1.5-1 -> 1.1.6-1)
[2007-08-19 14:57] upgraded xterm (225-1 -> 229-1)
[2007-08-21 00:16] upgraded cpio (2.8-1 -> 2.9-1)
[2007-08-21 00:16] upgraded ed (0.5-3 -> 0.8-1)
[2007-08-21 00:16] upgraded initscripts (2007.08-1 -> 2007.08-2)
[2007-08-21 00:16] upgraded intltool (0.36.0-1 -> 0.36.1-1)
[2007-08-21 00:16] upgraded libarchive (2.2.5-1 -> 2.2.6-1)
[2007-08-21 00:16] upgraded man-pages (2.60-1 -> 2.64-1)
[2007-08-21 00:16] upgraded pciutils (2.2.4-2 -> 2.2.6-1)
[2007-08-21 00:16] upgraded readline (5.2-2 -> 5.2-3)
[2007-08-22 00:16] upgraded gdbm (1.8.3-3 -> 1.8.3-4)
[2007-08-22 00:17] upgraded kernel26 (2.6.22.3-1 -> 2.6.22.4-2)
[2007-08-22 00:17] upgraded lcms (1.16-1 -> 1.17-1)
[2007-08-22 00:17] upgraded libice (1.0.2-1 -> 1.0.4-1)
[2007-08-22 00:17] upgraded libxrender (0.9.2-1 -> 0.9.3-1)
[2007-08-22 00:17] upgraded procinfo (18-3 -> 19-1)
[2007-08-22 00:17] upgraded xorg-apps (1.0.2-4 -> 1.0.3-1)
[2007-08-22 23:49] upgraded kernel26 (2.6.22.4-2 -> 2.6.22.4-2.1)
[2007-08-22 23:49] upgraded librsvg (2.18.0-1 -> 2.18.1-1)
[2007-08-22 23:49] upgraded libxpm (3.5.6-1 -> 3.5.7-1)
[2007-08-22 23:49] upgraded libxaw (1.0.3-1 -> 1.0.4-1)
[2007-08-22 23:49] upgraded makedev (3.8.3-1 -> 3.23-1)
[2007-08-22 23:49] upgraded mcpp (2.6-1 -> 2.6.4-1)
[2007-08-22 23:49] upgraded naim (0.11.8.2.1-1 -> 0.11.8.3.1-1)
[2007-08-22 23:49] upgraded nfs-utils (1.0.12-2 -> 1.0.12-3)
[2007-08-22 23:49] upgraded pam (0.81-4 -> 0.99.8.1-3.1)
[2007-08-22 23:49] upgraded pango (1.16.5-1 -> 1.18.0-1)
[2007-08-22 23:49] upgraded sox (13.0.0-1 -> 13.0.0-2)
[2007-08-22 23:49] upgraded xorg-apps (1.0.3-1 -> 1.0.3-2)
[2007-08-22 23:49] upgraded xtrans (1.0.3-1 -> 1.0.4-1)
[2007-08-25 15:25] upgraded glibc (2.6.1-1 -> 2.6.1-2)
[2007-08-25 15:25] upgraded bftpd (1.9-1 -> 2.0-1)
[2007-08-25 15:25] upgraded gcc (4.2.1-3 -> 4.2.1-3.1)
[2007-08-25 15:25] upgraded gtk-doc (1.8-2 -> 1.8-3)
[2007-08-25 15:25] upgraded hal-info (0.20070618-1 -> 0.20070725-1)
[2007-08-25 15:25] upgraded perl-xml-simple (2.16-2 -> 2.18-1)
[2007-08-25 15:25] upgraded icon-naming-utils (0.8.2-2 -> 0.8.5-1)
[2007-08-25 15:26] upgraded kernel26 (2.6.22.4-2.1 -> 2.6.22.5-1)
[2007-08-25 15:27] upgraded kernel26ck (2.6.22.3.ck1-1 -> 2.6.22.5.ck1-1)
[2007-08-25 15:27] upgraded libgnomeprint (2.18.0-1 -> 2.18.1-1)
[2007-08-25 22:41] removed libgnomeprintui (2.18.0-1)
[2007-08-25 22:41] removed libgnomeprint (2.18.1-1)
i dunno what happened...
plz, someone help me
regards
Last edited by saneone (2007-08-30 18:11:32)

Bogart wrote:
I think the spacing now is correct, while before it was wrong. The only "problem" is that you got used to a bad font rendering, and now that it has changed for better you feel like it's different and don't like it.
Really, *most* of the problems that people find in Linux's fonts are just because they are used to the awful default fonts from Windows XP. Yes, people can even get used to those fonts and believe they're good!!! And when they see correct fonts in Linux they think they're bad...
What I would do is remove the MS TTF fonts. They work bad in Windows and worse in Linux. You should use Bitstream Vera or DejaVu if you want good quality fonts (especially in web pages).
But, then again, you might think that they look wrong just because you're not used to it... Oh, well...
What does correct font / correct spacing mean ?
IMO, that doesn't make any sense, because that's a totally subjective matter, like many other things in this world.
BTW, I love how fonts look in Windows, and I think that must be the only thing MS got right. Thus, I'm using ms fonts in linux, and a rendering as close as possible (no autohinting or antialiasing or subpixel rendering).
Similarly, I could find a woman beautiful that you would find ugly or just average. We are all different, and it's better that way

Not-latin font rendering is broken in Kf5 applications

Hello.
After upgrading of KDE4 applications to Kf5 ones, I have the font rendering problem in them.
It's looks like that:
As you can see, rendering of cyrillic fonts is broken. Absolutely wrong font family (should be Terminus) and font size.
In KDE4 apps font rendering works correctly.
Do someone have any suggestions how can I fix this?

I can see picture without any problems. May be it is regional-specific problem of image hosting.
Google drive link: https://drive.google.com/file/d/0B-ZoDS … sp=sharing
Last edited by Lampus (2015-02-03 13:27:56)

[SOLVED] Font rendering messed up after latest freetype2 upgrade.

I haven't touched my font configuration, but the appearance of most fonts has changed across the board (i.e. in every application) since I upgraded to freetype 2.4.6 yesterday. In particular, the fonts are less strong, and in LibreOffice Calc in particular the spacing is messed up at certain levels of magnification despite having hinting enabled. Here is my ~/.gtkrc-2.0:
gtk-icon-theme-name = "nuoveXT2"
gtk-theme-name = "Clearlooks"
gtk-font-name = "FreeSans 10"
gtk-xft-antialias = 1
gtk-xft-hinting = 1
gtk-xft-hintstyle = "hintfull"
gtk-xft-rgba = "rgb"
I have tried many combinations of AA and hinting, and nothing seems to work. Fonts do look slightly differently when I change the hinting settings (except in Calc), but they do not look as crisp as before the upgrade. Can anyone help me?
Last edited by nbtrap (2011-08-01 01:44:13)

It figures that I fix this right after giving up and posting to the forums. It seems that either (1) Xresources overrides gtk settings or (2) Libreoffice ignores gtk settings. I had not had any ~/.Xresources file, but after creating one:
Xft.dpi: 96
Xft.antialias: true
Xft.rgba: rgb
Xft.hinting: true
Xft.hintstyle: hintslight
and adding
xrdb -merge ~/.Xresources
to ~/.xinitrc,, the font rendering has returned to normal across all applications, The strange thing is that I didn't have an Xresources config file before when the rendering was working fine. It's also weird that fonts in GTK apps looks crisper with Xresources configured than they do with the same configuration in ~/.gtkrc-2.0. I can't figure out why, but at least it's now working.

Problem with firefox and gtk applications in KDE!

Hi there, i have my arch installed and it's great, i use kdemod that is quite perfect but i have a problem: all the gtk applications like firefox, eclipse, emesene and so on are terrible looking expecially the fonts. Here what I've done:
1) installed kdemod-gtk-qt-engine and configured to use qt theme and it's better
2) enabled fonts with antialiasing and hinting
3) installed fonts for lcd like cairo-lcd
4) installed microsoft fonts
But stille it's ugly and it's impossible to use the apps, here's a screenshot:
The point is that i can't use konqueror because i need some plugins like googlebrowsersync that doesn't exist for konqueror. And in other distros like n00buntu it works.
Thanks for your help!

pelle.k wrote:
I can relate to what borzo is saying, because i have exactly the same problem.
See, i have installed libxft-lcd and enabled antialiasing and sub-pixel hinting in kde font properties. All kde fonts look great. Now, i usually the exactly the same in gnome "Appearance" font settings (when i use gnome).
The thing is when you have KDE installed you can't set antialiasing and sub-pixel hinting for *GTK* apps, even if you can set a theme and font size with gtk-chtheme/.gtkrc
This has nothing to do with how firefox renders fonts, really, but how GTK fonts a drawn in KDE since gnome-settings-manager isn't running, and thus GTK apps get crappy fonts (including firefox html rendering).
So, how can i enable antialiasing and sub-pixel rendering specifically for GTK apps in KDE without running gnome-settings-manager?
I know this is an old thread, but I'm still having exactly the same problem. I've been fiddling with fonts for a whole week now. Fonts in KDE apps look great, but crappy in GTK-apps like Thunderbird and Firefox. Like Pelle asked: how can I set aintialiasing and sub-pixel redndering for GTK apps? When running Gnome the fonts in GTK-apps look so much better. I wanna use my shiny new KDE 4 desktop, though.

Font rendering in KDE 4

I recently installed Arch (switching from Ubuntu 8.10) and decided to give KDE a try. So far I'm mostly happy, but the font rendering isn't working so well. There are two problems: the first is that fonts all look too thin. The second is that most of them are way too big! (For some reason they render properly in some places, like some sites online [e.g. Gmail], but they're way off in most applications.)
I've tried the suggestions under "LCD" packages from the Arch fonts wiki, along with this guy's suggestions for setting up fontconfig. I've also tried (variously) changing my DPI settings for KDM and System Settings -> Appearance -> Fonts (with aliasing anti-aliasing enabled or with system settings, and forcing the DPI to 120 or disabled).
Oh, and I have a 15.4" widescreen 1680x1050 LCD monitor, which I think is (supposed to be) 129 DPI.
What can I do to get fonts to look the way they should?

hunterthomson wrote:
OK, you problem is not with KDE. This weirded me out when I moved to Archlinux from Ubuntu too. In Archlinux you have to install all the fonts you want to use. The default fonts suck. So, You just need to install better fonts. You want the TrueType Fonts "ttf". You can install them with pacman
Try this to list all the font packages available.
sudo pacman -Ss font
These are some ones that are good
ttf-dejavu
ttf-freefont
ttf-liberation
you instal them you just do...
sudo pacman -S ttf-liberation ttf-freefont ttf-dejavu
Then you will want to open up the Konfiguration thing that you change the KDE configurations settings in and then change the fonts in there.
Thanks for the tip! I installed those (and a few others), and I definitely like (for instance) FreeSans better than the default Sans that most everything was using. Most things look better; I think I'm going to have to tweak the hinting a bit still, but this is definitely an improvement. Many of the things I thought were rendering related were actually just bad fonts, like you said.
There are just a couple of problems remaining that I'm hoping will be just as easy to conquer... First, some websites are still rendering horribly. Take a look at this screenshot of this site, followed by this one:
At first I figured it was a problem with Firefox (I know GTK doesn't always play nicely with KDE), but it looks the same in Konqueror. A quick peek at the HTML for the first seems to say that it's asking for Verdana, Arial, or Helvetica...and I have Verdana and Arial installed. (The second one calls for a ridiculous font, Palatino Linotype, which I don't have.) Either way, though, the pages look totally wrong (the font is much too large) compared to any other machine I've seen it on (even my previous Ubuntu setup). Does anyone know what's going on?
One other example of font size weirdness: the digital clock plasmoid. Here's what it looks like:
The odd thing is that it looked like this for a while when I first installed Arch and KDE, and then played nicely for a few days...and now it's back to looking ugly.
And finally, here are my font settings in System Settings:
(And yes, I've rebooted since installing the new fonts and changing font settings, just in case.)
Any more ideas?

Qt5 font rendering

Is there a way to configure font rendering for Qt5 applications? After last update my Qt4 assistant and designer were removed, and I'm forced to use Qt5 versions, which have a very ugly look.

MadCat_X wrote:That is rather odd. My QtCreator window now looks like this. The menus and the vertical panel look fine as far as font rendering goes, but the central screen is rather ugly - and no, those are not compression artifacts:). Qt4 version of QtCreator was perfectly OK. Is Qt5 supposed to load "Application Appearance" settings from KDE correctly? If it is, then it certainly isn't happening on my machine. Is there anything I can do to track the problem down? Thank you.
Your QtCreator is fine. You cannot use a Qt4 theme (Oxygen) on a Qt5 application.

[SOLVED]A nice sharp font renderer (not as sharp as windows)

Is there another font renderer out there? I tried freetype the default and that gives me blurry edges. Infinality is not better in my opinion. Same blurry edges too many configurations. Are there any other renderers out there?
Last edited by tedbell (2012-08-07 20:06:21)

here's ..profile.d/infinality-settings.sh:
### INFINALITY ENVIRONMENT VARIABLES FOR EXTRA RUN-TIME OPTIONS ##
# These environment variables require that their respective patches
# from http://www.infinality.net have been applied to the Freetype
# installation you are using. They will do abolutely
# nothing otherwise!
# This file should be copied to /etc/profile.d/ for system-wide
# effects and/or included in ~/.bashrc or ~/.bash_profile for per-user
# effects:
# . ~/path/to/this/file/infinality-settings.sh
# Of course, the per-user settings will override the system-wide
# settings. Default values indicated below will be used when the
# environment variables below are not defined.
# When I say "Default:" below, I'm referring to the default if no
# environment variables are set. Generally this ends up being
# whatever Freetype's default is set to.
# EXAMPLES
# Please see 3/4 down in this file for examples of different settings.
################## EXPLANATION OF SETTINGS ######################
# SET_XFT_SETTINGS
# Should the below Xft settings be set globally by this script? (true/false)
SET_XFT_SETTINGS=true
# XFT settings are like a red-headed stepchild that should be beaten severely.
# These only affect legacy programs, and *parts* of some modern programs like
# google-chrome. We only deal with these settings because we have to, otherwise
# crap will slip by. I recommend using hintslight and autohint as the defaults
# normally in local.conf. The reason hintfull and autohint:0 is needed here
# because otherwise some programs will occassionally request slight hinting for
# a truetype font. When a program does this, Freetype automatically uses the
# autohinter, when you may actually want it to be rendered with the TT hinter,
# (if specified in local.conf). So setting this to hintfull guarantees that the
# TT font will be rendered with the TT hinter (assuming it is specified in
# /etc/fonts/local.conf to be rendered that way.) For TT fonts that you want
# rendered with autohint, specifiying that in the /etc/fonts/local.conf
# should be enough. But you might think that by setting this to hintfull
# that it's going to use Freetype's full autohinting (which we *completely*
# avoid) for fonts you want autohinted. This is where
# INFINALITY_FT_AUTOFIT_FORCE_SLIGHT_HINTING comes in. It tells freetype to
# use slight hinting on fonts set for autohinting, even if the program requests
# full autohinting. Freetype's full hinting only looks OK under certain
# circumstances. The goal of infinality is to make infinality hinting look
# good all the time.
XFT_SETTINGS="
Xft.antialias: 1
Xft.autohint: 0
Xft.dpi: 96
Xft.hinting: 1
Xft.hintstyle: hintfull
Xft.lcdfilter: lcddefault
Xft.rgba: rgb
if [ "$SET_XFT_SETTINGS" = "true" ]; then
echo "$XFT_SETTINGS" | xrdb -merge > /dev/null 2>&1
fi
# INFINALITY_FT_FILTER_PARAMS
# This is a modified version of the patch here:
# http://levelsofdetail.kendeeter.com/2008/12/dynamic_fir_filter_patch.html
# Allows you to adjust the FIR filter at runtime instead of at
# compile time. The idea is to have values add up to 100, and be
# symmetrical around the middle value. If the values add up to
# more than 100, the glyphs will appear darker. If less than 100,
# lighter. I recommend using this method to make glyphs darker
# or lighter globally as opposed to using the gamma option (see note in
# the gamma option).
# Here are some samples of various filter parameters:
# (this has been changed to use integers between 0 and 100 to
# avoid problems with regional differences like comma for decimal point)
# Strong Extra Smooth "15 20 30 20 15" (extra smooth, natural weight)
# Extra Smooth "20 20 30 20 20" (extra smooth, extra weight)
# Smooth "15 20 32 20 15" (smooth, natural weight)
# Stronger Gibson "11 22 38 22 11" (smooth, extra weight)
# Gibson "11 22 33 22 11" (smooth, natural weight)
# Freetype Light "00 33 34 33 00" (sharp, natural weight) # freetype's "light" LCD filter
# Freetype Default "06 25 44 25 06" (sharp, extra weight) # freetype's default
# Extra Sharp "00 35 35 35 00" (extra sharp, extra weight) # freetype's "light" LCD filter on acid
# Windows uses something more sharp, maybe along the lines of Freetype's default
# Default if no ENV_VARS present: [Freetype's default]
# Recommended: "11 22 38 22 11" (too dark / smooth for some)
# Example 1: export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
# INFINALITY_FT_STEM_ALIGNMENT_STRENGTH
# This performs analysis on each glyph and determines an amount
# to shift the glyph, left or right, so that it aligns better to
# pixel boundaries.
# This results in subtley cleaner looking stems, at the expense of
# proper distances between glyphs. This is only active for sizes
# 10 px or greater and does not apply to bold or italic fonts.
# There are also exceptions on a small number of fonts that I've
# not been able to render nicely with alignment enabled. In those
# cases, a forced translation is applied instead.
# Possible values:
# 0 through 100 - think of as percentage of strength
# 0 corresponds to no shifting whatsoever. In other words, OFF.
# 100 corresponds to a full move to a snap zone defined by
# the snapping algorithm, be it left or right. This
# is the full amount any glyph could be moved in order to make it
# align to the pixel.
# Values inbetween act as caps. If the algorithm determines that it
# wants to move the glyph .33 of a pixel to the left, but the value
# is set to 50 (i.e. 50%), then the maximum move that would be allowed
# is 50% of half a pixel, in other words .25. So instead of .33 the
# glyph is moved .25 of a pixel.
# For a subtle effect that doesn't dramatically affect the glyph, use
# 25 for this and 25 for INFINALITY_FT_STEM_FITTING_STRENGTH
# Default if no ENV_VARS present: 0
# Recommended if you want to use it: 100
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=25
# INFINALITY_FT_STEM_FITTING_STRENGTH
# This performs analysis on each glyph and determines an amount
# to horizontally scale the glyph, so that stems align better to
# pixel boundaries. An emboldening (or anti-emboldening) is
# performed afterward to account for stem width exaggeration.
# This results in subtley cleaner looking fonts, at the expense of
# proper distances between glyphs and slightly misshapen glyphs.
# This is only active for sizes 10 px or greater and does not
# apply to bold or italic fonts.
# There are also exceptions on a small number of fonts that I've
# not been able to render nicely with fitting enabled. In those
# cases, a forced translation is applied instead.
# Possible values:
# 0 through 100 - think of as percentage of strength
# 0 corresponds to no stretching whatsoever. In other words, OFF.
# 100 corresponds to a full pixel stretch, be outward or inward. This
# is the full amount any glyph could be stretched in order to make it
# align to a pixel boundary. Which direction is chosen is part
# of the art of what I'm trying to do in the code. ;)
# Values inbetween act as caps. If the algorithm determines that it
# wants to stretch the glyph .75 of a pixel outward, but the value
# is set to 50 (i.e. 50%), then the maximum move that would be allowed
# is 50% of a pixel, in other words .50. So instead of .75 the
# glyph is stretched .50 of a pixel.
# For a subtle effect that doesn't dramatically affect the glyph, use
# 25 for this and 25 for INFINALITY_FT_STEM_FITTING_STRENGTH
# Default if no ENV_VARS present: 0
# Recommended if you want to use it: 100
export INFINALITY_FT_STEM_FITTING_STRENGTH=25
# INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE
# This allows you to set a ppem at which alignment and fitting
# will reach 100%. As glyphs become larger, more dramatic
# snapping will not affect the glyph shape as much, so it makes
# sense to allow this.
# For fonts that are 10 ppem, the values set above for
# INFINALITY_FT_STEM_ALIGNMENT_STRENGTH and
# INFINALITY_FT_STEM_FITTING_STRENGTH will be used. As the ppem
# gradually becomes larger, so will the strength settings, and
# they will reach 100% at the ppem you specify here.
# This is a simple linear scale.
# Possible values:
# 0 means to not use this feature
# 11 and up will set the 100% level to that ppem value
# Anything else is officially undefined, but I still bound it internally.
# Default if no ENV_VARS present: 0
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=40
# INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS
# This applies largely to certain MS fonts, but some others as well.
# it will apply known good settings on a font-by-font basis, regardless
# of the other settings above or below.
# - Use known values for selected fonts & ppems that are known to look
# ok with 100:
# INFINALITY_FT_STEM_ALIGNMENT_STRENGTH
# INFINALITY_FT_STEM_FITTING_STRENGTH
# - Use various internal tweaks like compatible widths and other
# font-specific hacks.
# - Use gamma, brightness or contrast adjustments automatically
# on certain fonts. Global settings will still apply afterwards.
# - Enable various forced settings on selective fonts during
# rasterization and stem_alignment.
# If set to TRUE, this will use 100 regardless of the values you have
# specified above. It will not affect fonts that are not in this
# small list.
# Possible values:
# FALSE means to not use this feature
# TRUE will enable this feature
# Default if no ENV_VARS present: FALSE
# Recommended: TRUE
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
# INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH
# This enables an algorithm found in ChromeOS for sharpening the
# appearance of glyphs. It is based off this patch:
# http://codereview.chromium.org/3298011/diff/9001/media-libs/freetype/files/freetype-2.3.11-lcd-sharpen.patches
# It gives glyphs a more "grainy" look through some gamma
# correction. It does tend to thin out vertical stems, which
# may be a feature or a bug depending on your taste ;)
# Possible values:
# 0 through 100 - think of as percentage of strength
# 0 corresponds to no sharpening whatsoever. In other words, OFF.
# 25 is good for a subtle effect.
# 50 corresponds to the default ChromeOS value.
# 100 corresponds to maximum sharpening. This usually results in
# something undesirable looking.
# As you increase this amount, it is good to decrease the gamma (2nd value)
# of INFINALITY_FT_PSEUDO_GAMMA, and possibly increase
# INFINALITY_FT_STEM_FITTING_STRENGTH and
# INFINALITY_FT_STEM_ALIGNMENT_STRENGTH, as it seems like the algorithm
# lightens stems that aren't fully on-pixel.
# Default if no ENV_VARS present: 0
# Recommended: If you're going to use this filter - 50
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
# INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH
# This enables an algorithm developed with the intention to sharpen
# fonts to look similarly to Windows.
# It gives glyphs a more "grainy" look, like the ChromeOS filter
# except it does so more selectively. This prevents the thinning
# of vertical stems that is noticible when a blanket gamma filter
# like the ChromeOS filter is applied.
# I also get a "cleaner" impression from the fonts with this Windows
# style filter. This filter was done by 100% experimentation,
# and there things that could probably be improved.
# Some may argue that I shouldn't be trying to take the shortcomings
# of the MS approach and bring them here. I disagree, as part
# of freedom is having the right to make your fonts look as
# shitty as you'd like.
# Using this filter does somewhat lessen the need to use stem
# fitting and stem alignment, as glyphs appear sharper.
# This setting can be used at the same time as the previous chromeOS
# sharpening, and happens after it in the code.
# Possible values:
# 0 through 100 - think of as percentage of strength
# 0 corresponds to no sharpening whatsoever. In other words, OFF.
# 10-25 is good for a subtle effect while not completely decimating glyphs.
# 50-75 corresponds to probably something in the range that Windows uses.
# 100 corresponds to maximum sharpening.
# Using a high value for this variable along with enabling the
# fringe filter (below) almost eliminates the need
# for INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT to be set to 100,
# and can instead be set at 0. (Setting
# INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT to 0 prevents missing
# stems in the middle of s. The drawback is that many fonts just look
# way too sharp and grainy at this setting. Your call.)
# Default if no ENV_VARS present: 0
# Recommended if you want to use this filter: 65
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=10
# INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT
# When using autohinting, horizontal stems you'd find in E, f, T, -,
# etc. are normally not snapped to full integer pixel heights, meaning
# that you will get a semi-dark fringe on these stems, above or
# below the black line of pixels:
# (- represents the semi-dark pixels)
# Setting this to 100 will force integer pixel heights. Setting it to
# zero will do what Freetype does by default. Anything inbetween will
# act as a weighted average of the two.
# This is disabled when the standard width is found (via voodoo) to be
# less than 1 pixel, in order to prevent the vanishing stem issues on
# letters with diagonal stems like a and s.
# Under most circumstances, this should be set at 100. If you choose to
# not set it to 100, you may want to set INFINALITY_FT_FRINGE_FILTER_STRENGTH
# to a non-zero value in order to reduce fringing.
# Possible values:
# 0 - default Freetype value
# 100 - a full pixel
# Default if no ENV_VARS present: 0
# Recommended: 100
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
# INFINALITY_FT_USE_VARIOUS_TWEAKS
# - Force autohint when no TT instructions present.
# - Artificially embolden horizontally only.
# - When artificially emboldening, maintain the glyph width.
# - Embolden light and thin-stemmed glyphs automatically.
# - Don't sharpen italics.
# Some fonts look bad when stem aligned at certain ppems, no matter
# what. I've put exceptions in to deal with these, included in
# these tweaks. Georgia and Lucida Grande are examples.
# Possible values:
# true - enable tweaks
# false - do not enable tweaks (do Freetype default)
# Default if no ENV_VARS present: false
# Recommended: true
export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
# INFINALITY_FT_GAMMA_CORRECTION
# This does a weighted gamma correction at the LCD filter phase
# PRIOR to the LCD filter. Unfortunately it does not however
# take into account the color on which the glyph is being rendered
# (or for that matter the color of the glyph),
# which would need to happen in X rendering. It is actually
# using the gamma function in calculations though.
# The first value indicates a px value, the second indicates a
# "gamma" value. All sizes less than the px value will be corrected
# on a weighted scale based on the second value.
# The gamma value is commonly between 0.0 and 3.0. Due to localization
# issues, the gamma value should be specified as it's actual value
# multiplied by 100. So a gamma of 1.3 would be 130. In practice,
# I'd stay between 40 and 250.
# Values 1 through 100 will darken the glyph
# Values greater than 100 will lighten the glyph
# Example 1: Darken glyphs that are less than 10 px. With some fonts
# even 5 or 6px is readable!
# export INFINALITY_FT_GAMMA_CORRECTION="10 60"
# Example 2: Lighten all glyphs (below 100px)
# export INFINALITY_FT_GAMMA_CORRECTION="100 150"
# Example 3: Do nothing
# export INFINALITY_FT_GAMMA_CORRECTION="0 100"
# Default: [No gamma correction]
export INFINALITY_FT_GAMMA_CORRECTION="0 100"
# INFINALITY_FT_BRIGHTNESS
# This filter adjusts brightness, using the standard algorithm
# for brightness. It is applied AFTER the LCD filtering.
# For a Windows XP look, set brightness to something and contrast to 50
# This will also tend to increase its sharpness.
# These values are relative and don't really mean anything
# however they are satisfactory for a range of appearances.
# Another tip is to use a gamma setting of "1000 110" or something
# over 100 to lighten things before processing.
# Default if no ENV_VARS present: 0
# Dark XP Experience: -25
# Light XP Experience: 40
# Example: export INFINALITY_FT_BRIGHTNESS="-20"
export INFINALITY_FT_BRIGHTNESS="0"
# INFINALITY_FT_CONTRAST
# This filter adjusts contrast, using the standard algorithm
# for contrast. It is applied AFTER the LCD filtering.
# For a Windows XP look, set brightness to -25 and contrast to 50
# This will also tend to increase its sharpness.
# These values are relative and don't really mean anything
# however they are satisfactory for a range of appearances.
# Another tip is to use a gamma setting of "1000 110" or something
# over 100 to lighten things before processing.
# Default if no ENV_VARS present: 0
# Dark or Light XP Experience: 50
# Example: export INFINALITY_FT_CONTRAST="50"
export INFINALITY_FT_CONTRAST="0"
# INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH
# This filter adjusts subpixel-rendered glyphs toward grayscale.
# Sometimes this is useful in getting a rendering more like
# OSX.
# Range: Integers 0 through 100
# 0 represents no filtering
# 50 represents halfway between subpixel and grayscale
# 100 represents completely grayscale
# Default if no ENV_VARS present: 0
# Recommended, if you want to use it: 30
# Example: export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH="33"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH="0"
# INFINALITY_FT_FRINGE_FILTER_STRENGTH
# This filter tries to remove the horizontal fringing that is found on
# default autohinted glyphs (similar to OSX-rendered glyphs).
# For example, an E may be rendered so that the middle horizontal
# stem is 100% black, but also has a horizonal row of pixels above
# it that is at 50% intensity. This makes the glyph look dirty,
# however it is technically accurate.
# This would be useful in cases where you have
# INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT set to something less than 100
# but also can affect glyphs at 100, to some degree.
# Unless fonts are showing fringes in a way that annoys you, I recommend
# keeping it disabled, as it can slightly interfere with smooth appearance
# sometimes.
# Range: Integers 0 through 100
# 0 represents no filtering
# 50 represents a 50% reduction of detected fringes
# 100 represents completely removing detected fringes
# Default if no ENV_VARS present: 0
# Recommended, if you want to use it: 100
# Example: export INFINALITY_FT_FRINGE_FILTER_STRENGTH="100"
export INFINALITY_FT_FRINGE_FILTER_STRENGTH="0"
# INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH
# This post-filter darkens horizontal stems that autohint renders as semi-dark.
# Freetype will by default not force stems to render to pixel boundaries
# because it results in "vanishing stems". This happens on things like
# s S a and other glyphs with center diagonal stems.
# If you have INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT set to 100,
# you're telling it to force pixel boundaries, which can result in the
# vanishing stems. To get around this problem, I internally override the
# INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT setting if the stem width
# is less than a full pixel, regardless. This causes semi-dark stems, but
# at least there are stems there.
# This filter is intended to darken those semi-dark stems. I highly
# recommend using this, but setting to a low value like 10, because
# it is particularly sensitive right now, and can make thin fonts
# look weird otherwise.
# Range: Integers 0 through 100
# 0 represents no darkening
# 50 represents a 50% increase toward 1 pixel in height
# 100 represents a full pixel of height
# Default if no ENV_VARS present: 0
# Recommended, if you want to use it: 10
# Example: export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH="10"
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH="10"
# INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH
# This post-filter darkens vertical stems less than 1 pixel that autohint
# renders as semi-dark. This applies mostly to thin fonts like
# Courier New, Raleway, and fonts with the word "Light" in the title or
# style. Although what autohint is doing is technically correct, it
# results in a bad looking rendering because it's too light, at small
# ppems. This filter tries to correct that.
# There is an aspect of this that is automatic, so it's safer to use
# larger values for this than the above horizontal ENV_VAR. However
# setting this higher has more impact on thinner fonts. So, I still
# recommend lower values.
# Range: Integers 0 through 100
# 0 represents no darkening
# 50 represents a 50% increase (from current strength) toward 1 pixel
# 100 represents a full pixel of width
# Default if no ENV_VARS present: 0
# Recommended, if you want to use it: 25
# Example: export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH="25"
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH="25"
# INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS
# This will slightly stretch some glyphs vertically between 9px
# and 14px (inclusive). Some people may find this more
# aesthetically pleasing. This only applies to fonts that are
# using autohint. I used to recommend this to be set true, but
# it does mess with some (less popular) glyphs in a nasty way.
# The goal here is to increase the height of some fonts by 1 px
# but leave the x-height where it is. Arial is a good example
# of this working properly. Compare the heights of Arial, Times
# and Freesans with this on, vs. TT hinted versions of Arial and
# Times.
# Possible values:
# true - enable height adjustment
# false - do not enable height adjustment
# Default: false
export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=true
# Experimental emboldening values for OSX mode
export INFINALITY_FT_GLOBAL_EMBOLDEN_X_VALUE=0
export INFINALITY_FT_GLOBAL_EMBOLDEN_Y_VALUE=0
export INFINALITY_FT_BOLD_EMBOLDEN_X_VALUE=0
export INFINALITY_FT_BOLD_EMBOLDEN_Y_VALUE=0
########################### EXAMPLES ############################
# Set the USE_STYLE variable below to try each example.
# Make sure to set your style in /etc/fonts/local.conf too.
# Possible options:
# DEFAULT - Use above settings. A compromise that should please most people.
# OSX - Simulate OSX rendering
# UBUNTU - Simulate UBUNTU rendering
# LINUX - Generic "Linux" style - no snapping or certain other tweaks
# WINDOWS - Simulate Windows rendering
# WINDOWS7 - Simulate Windows rendering with normal glyphs
# WINDOWS7LIGHT- Simulate Windows 7 rendering with lighter glyphs
# WINDOWS - Simulate Windows rendering
# VANILLA - Just subpixel hinting
# CUSTOM - Your own choice. See below
# ----- Infinality styles -----
# CLASSIC - Infinality rendering circa 2010. No snapping.
# NUDGE - CLASSIC with lightly stem snapping and tweaks
# PUSH - CLASSIC with medium stem snapping and tweaks
# SHOVE - Full stem snapping and tweaks without sharpening
# SHARPENED - Full stem snapping, tweaks, and Windows-style sharpening
# INFINALITY - Settings I use
# DISABLED - Act as though running without the extra infinality enhancements (just subpixel hinting).
USE_STYLE="LINUX"
### NEEDS WORK ###
################# OSX STYLE #################
if [ "$USE_STYLE" = "OSX" ]; then
export INFINALITY_FT_FILTER_PARAMS="03 32 38 32 03"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=25
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
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="1000 80"
export INFINALITY_FT_BRIGHTNESS="10"
export INFINALITY_FT_CONTRAST="20"
export INFINALITY_FT_USE_VARIOUS_TWEAKS=false
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
export INFINALITY_FT_GLOBAL_EMBOLDEN_X_VALUE=0
export INFINALITY_FT_GLOBAL_EMBOLDEN_Y_VALUE=8
export INFINALITY_FT_BOLD_EMBOLDEN_X_VALUE=16
export INFINALITY_FT_BOLD_EMBOLDEN_Y_VALUE=0
fi
################# UBUNTU STYLE #################
if [ "$USE_STYLE" = "UBUNTU" ]; then
export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
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="1000 80"
export INFINALITY_FT_BRIGHTNESS="-10"
export INFINALITY_FT_CONTRAST="15"
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
fi
################# LINUX STYLE #################
if [ "$USE_STYLE" = "LINUX" ]; then
export INFINALITY_FT_FILTER_PARAMS="06 25 44 25 06"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
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=0
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=25
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="10"
export INFINALITY_FT_CONTRAST="50"
export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=false
fi
################# WINDOWS XP STYLE LIGHT #################
if [ "$USE_STYLE" = "WINDOWSXPLIGHT" ]; then
export INFINALITY_FT_FILTER_PARAMS="06 25 44 25 06"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=100
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=65
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=15
export INFINALITY_FT_STEM_FITTING_STRENGTH=15
export INFINALITY_FT_GAMMA_CORRECTION="1000 120"
export INFINALITY_FT_BRIGHTNESS="20"
export INFINALITY_FT_CONTRAST="30"
export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=30
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
fi
################# WINDOWS 7 STYLE LIGHT #################
if [ "$USE_STYLE" = "WINDOWS7LIGHT" ]; then
export INFINALITY_FT_FILTER_PARAMS="20 25 38 25 05"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=100
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=100
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="1000 160"
export INFINALITY_FT_BRIGHTNESS="0"
export INFINALITY_FT_CONTRAST="20"
export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=30
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
fi
################# WINDOWS XP STYLE #################
if [ "$USE_STYLE" = "WINDOWSXP" ]; then
export INFINALITY_FT_FILTER_PARAMS="06 25 44 25 06"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=100
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=65
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=15
export INFINALITY_FT_STEM_FITTING_STRENGTH=15
export INFINALITY_FT_GAMMA_CORRECTION="1000 120"
export INFINALITY_FT_BRIGHTNESS="10"
export INFINALITY_FT_CONTRAST="20"
export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=30
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
fi
################# WINDOWS 7 STYLE #################
if [ "$USE_STYLE" = "WINDOWS7" ]; then
export INFINALITY_FT_FILTER_PARAMS="20 25 42 25 06"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=100
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=65
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="1000 120"
export INFINALITY_FT_BRIGHTNESS="10"
export INFINALITY_FT_CONTRAST="20"
export INFINALITY_FT_USE_VARIOUS_TWEAKS=true
export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
fi
############### VANILLA STYLE ##############
if [ "$USE_STYLE" = "VANILLA" ]; then
export INFINALITY_FT_FILTER_PARAMS="06 25 38 25 06"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
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=0
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=false
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
fi
############### CLASSIC INFINALITY STYLE ##############
if [ "$USE_STYLE" = "CLASSIC" ]; then
export INFINALITY_FT_FILTER_PARAMS="06 25 38 25 06"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
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=0
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=true
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=false
fi
################# NUDGE STYLE #################
if [ "$USE_STYLE" = "NUDGE" ]; then
export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=25
export INFINALITY_FT_STEM_FITTING_STRENGTH=15
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=true
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=30
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=false
fi
################# PUSH STYLE #################
if [ "$USE_STYLE" = "PUSH" ]; then
export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=75
export INFINALITY_FT_STEM_FITTING_STRENGTH=50
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=true
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=30
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
fi
################# INFINALITY STYLE #################
if [ "$USE_STYLE" = "INFINALITY" ]; then
export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=5
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=25
export INFINALITY_FT_STEM_FITTING_STRENGTH=25
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=true
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=40
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
fi
################# SHOVE STYLE #################
if [ "$USE_STYLE" = "SHOVE" ]; then
export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=100
export INFINALITY_FT_STEM_FITTING_STRENGTH=100
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=true
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
fi
################# SHARPENED INFINALITY STYLE #################
if [ "$USE_STYLE" = "SHARPENED" ]; then
export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=65
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=25
export INFINALITY_FT_STEM_FITTING_STRENGTH=25
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=true
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=40
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
fi
################# DISABLED STYLE #################
if [ "$USE_STYLE" = "DISABLED" ]; then
export INFINALITY_FT_FILTER_PARAMS=
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=
export INFINALITY_FT_STEM_FITTING_STRENGTH=
export INFINALITY_FT_GAMMA_CORRECTION="0 100"
export INFINALITY_FT_BRIGHTNESS="0"
export INFINALITY_FT_CONTRAST="0"
export INFINALITY_FT_USE_VARIOUS_TWEAKS=false
export INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS=false
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=false
fi
################# CUSTOM STYLE #################
if [ "$USE_STYLE" = "CUSTOM" ]; then
export INFINALITY_FT_FILTER_PARAMS="11 22 38 22 11"
export INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH=0
export INFINALITY_FT_FRINGE_FILTER_STRENGTH=0
export INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH=10
export INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH=25
export INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH=0
export INFINALITY_FT_STEM_ALIGNMENT_STRENGTH=100
export INFINALITY_FT_STEM_FITTING_STRENGTH=100
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=true
export INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT=100
export INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE=0
export INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS=true
fi
And here is fonts.conf:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">

<fontconfig>


<dir>/usr/share/fonts</dir>
<dir>~/.fonts</dir>

<match target="pattern">
<test qual="any" name="family">
<string>mono</string>
</test>
<edit name="family" mode="assign">
<string>monospace</string>
</edit>
</match>

<match target="pattern">
<test qual="any" name="family">
<string>sans serif</string>
</test>
<edit name="family" mode="assign">
<string>sans-serif</string>
</edit>
</match>

<match target="pattern">
<test qual="any" name="family">
<string>sans</string>
</test>
<edit name="family" mode="assign">
<string>sans-serif</string>
</edit>
</match>

<include ignore_missing="yes">conf.d</include>

<cachedir>/var/cache/fontconfig</cachedir>
<cachedir>~/.fontconfig</cachedir>
<config>

<blank>
<int>0x0020</int> 
<int>0x00A0</int> 
<int>0x00AD</int> 
<int>0x034F</int> 
<int>0x0600</int> 
<int>0x0601</int> 
<int>0x0602</int> 
<int>0x0603</int> 
<int>0x06DD</int> 
<int>0x070F</int> 
<int>0x115F</int> 
<int>0x1160</int> 
<int>0x1680</int> 
<int>0x17B4</int> 
<int>0x17B5</int> 
<int>0x180E</int> 
<int>0x2000</int> 
<int>0x2001</int> 
<int>0x2002</int> 
<int>0x2003</int> 
<int>0x2004</int> 
<int>0x2005</int> 
<int>0x2006</int> 
<int>0x2007</int> 
<int>0x2008</int> 
<int>0x2009</int> 
<int>0x200A</int> 
<int>0x200B</int> 
<int>0x200C</int> 
<int>0x200D</int> 
<int>0x200E</int> 
<int>0x200F</int> 
<int>0x2028</int> 
<int>0x2029</int> 
<int>0x202A</int> 
<int>0x202B</int> 
<int>0x202C</int> 
<int>0x202D</int> 
<int>0x202E</int> 
<int>0x202F</int> 
<int>0x205F</int> 
<int>0x2060</int> 
<int>0x2061</int> 
<int>0x2062</int> 
<int>0x2063</int> 
<int>0x206A</int> 
<int>0x206B</int> 
<int>0x206C</int> 
<int>0x206D</int> 
<int>0x206E</int> 
<int>0x206F</int> 
<int>0x2800</int> 
<int>0x3000</int> 
<int>0x3164</int> 
<int>0xFEFF</int> 
<int>0xFFA0</int> 
<int>0xFFF9</int> 
<int>0xFFFA</int> 
<int>0xFFFB</int> 
</blank>

<rescan>
<int>30</int>
</rescan>
</config>
</fontconfig>
Infinality.conf:
<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>








<selectfont>
<rejectfont>
<pattern>
<patelt name="fontformat" >
<string>Type 1</string>
</patelt>
</pattern>
</rejectfont>
</selectfont>

<match target="font" >
<edit name="embeddedbitmap" mode="assign">
<bool>false</bool>
</edit>
</match>

<match target="pattern" >
<edit name="prefer_outline" mode="assign">
<bool>true</bool>
</edit>
</match>


<match target="pattern" >
<edit name="bitmap_monospace" mode="assign">
<bool>false</bool>
</edit>
</match>


<match target="font">
<edit name="force_autohint" mode="assign">
<bool>false</bool>
</edit>
</match>



<match target="pattern">
<edit name="dpi" mode="assign">
<double>96</double>
</edit>
</match>




<match target="pattern" >
<edit name="qt_use_subpixel_positioning" mode="assign">
<bool>false</bool>
</edit>
</match>

<include>infinality/conf.d</include>
</fontconfig>
I tried every conf.d symlink in the /etc/fonts/infinality/styles.conf.avail folder. I just can't get the fonts to be sharp with nice uniform smoothness. They look garbled.
I just tried the ubuntu freetype and it looks worse.

Windows OpenType CFF Font Rendering

We have a situation where our identity font is displaying terribly in MS Word 2010 on Windows 7. The font looks great in InDesign and Illustrator. The font family is OpenType with PostScript outlines, aka CFF. This behavior is consistent for any OpenType font from Adobe, such as Myriad Pro or Adobe Garamond.
I am nearly certain that the Windows font rendering engine is optimized for TrueType outlines and renders PostScript outlines poorly. I also think that Adobe is using a different rendering engine for the Creative Suite applications, perhaps their own. I have not been able to find any specific documentation of these statements.
Does this ring true? Does anyone know of specific documentation of poor font rendering in Windows applications, especially MS Office?

Argg! I knew it would be something stupid. I spent a lot of time recently trying to get all the exceptions worked out in font embedding and it is all starting to run together.
Yes, I use flate by default, but I used AsciiHex so I could examine the data easily. Now I'm wondering when this crept in and how much time I wasted. Maybe I don't want to know.
This fixes the display issue in Acrobat/Reader, but Apple Preview still won't display the font (it substitutions but gives no error). Does anyone know if Apple Preview even supports FontFile3/OpenType?
Confusingly, Acrobat's Preflight -> PDF Analysis -> "Report PDF syntax issues" still reports the "An unexpected value is associated with the key" error.
In this case, would extracting the CFF table as is from the OTF be a valid CFF font that could be used, thereby using FontFile3/Type1C and make it compatible with Apple Preview? Just thinking out loud.
I've updated the file http://www.pagestream.org/fonttest4.pdf to reflect the proper encoding for anyone who might have an inkling to take a look.
Thank you Leonard for your help!
Deron

Flex 4.5/FP10.2 web app: Font rendering problem

Heya,
Upped a web app from Flex 4.0/4.1 to Flex 4.5 & fonts started to render really badly (blurry & 'stronger').
They are embedded as CFF, no errors or warnings gives. Also upgraded to Flash Player 10.2, which apparently has 'enhanched' font rendering.
Haven't set applicationDPI on the s:Application tag, so DPI management should be disabled according to the docs.
(See http://help.adobe.com/en_US/flex/mobileapps/WS19f279b149e7481c682e5a9412cf5976c17-8000.htm l)
It's straight up @font-face embeds in a CSS file, nothing odd or wrong there.
Is the case that this is how it's supposed to look now? In that case, how do I revert back to sane rendering?
Do I need to configure 4.5 somehow to get it to do fonts right?

Also tested Franklin Gothic, same deal. Tested on Mac (10.2) & PC (10.2 & 10.3). Flex 4.5 for both platforms.
fonts.css:
@font-face
src: url("fonts/arial.ttf");
font-family: Arial;
font-weight: normal;
embedAsCFF: true;
FontTest.mxml:
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">
<fx:Style source="fonts.css"/>
<s:Label x="20" y="20"
fontFamily="Arial"
fontLookup="embeddedCFF"
fontSize="12"
cffHinting="horizontalStem"
text="TESTAR Testar testar" />
</s:Application>

[SOLVED] Text disappearing in GTK applications

Here's a screenshot of what I'm describing: http://i.imgur.com/chJ1V.png
Text disappears from labels, lists, textboxes and tooltips. I've noticed I can copy and paste text from GTK textboxes into Qt applications but if I copy text from one GTK textbox to another it still won't appear. When typing in a textbox I'll be able to see it (most of the time) but then one keystroke will make the whole text disappear, pressing backspace does not make it reappear.
Also, some text reappears when reducing the size of a list horizontally: http://imgur.com/a/LvBJ1 -- Increasing the width causes more text to disappear.
I can't seem to find any solution through google and I don't think it's a font issue since I'm having no problems with Qt applications.
Any ideas on what the problem could be? Thanks
Last edited by johan_m (2012-05-15 17:47:00)

This issue is also occurring in terminal emulators that use vte or vte3. This includes Lilyterm, Sakura, etc (you can see the list under VTE-Based Terminals in the list of Common Applications on the Arch Wiki.
I wanted to point this out because I don't use any GTK applications, hopefully this should be helpful for lilyterm users who are searching for this issue.
Also, updating to [testing] didn't work for me. Downgrading to xorg-server 1.12.1-1 works for now
Last edited by ElKatrina (2012-05-16 02:26:31)

Font rendering in certain GTK+ 3 applications

Similar Messages

Maybe you are looking for