Font rendering too thick

It seems that Firefox is rendering fonts a bit too thick. font-weight is set to the right values, the problem is partially solved when decreasing the weight 100 (from 300 to 200) but is then displayed too thin on the other browsers.
This image shows Safari 6, Chrome 25 and Firefox 19
http://palacz.at/exchange/comparison.png
You also can see clearly that the Font Awesome Icons I used are too thick and don't look good at all. Also the font-weight is set correctly and is displayed correctly in the Inspector of Firefox.

Hi dreerr, at first I got the same results you got, but then I noticed that the font download was being blocked by NoScript, so another font was being substituted. After I allowed the font download, Firefox lined up with IE9 and Chrome (on Windows 7 Pro 64-bit).

Similar Messages

  • Font Rendering to thick

    It seems that Firefox is rendering fonts a bit too thick. font-weight is set to the right values, the problem is partially solved when decreasing the weight 100 (from 300 to 200) but is then displayed too thin on the other browsers.
    This image shows from left to right Safari 6, Chrome 25 and Firefox 19
    http://palacz.at/exchange/comparison.png
    You also can see clearly that the Font Awesome Icons I used are too thick and don't look good at all. Also the font-weight is set correctly and is displayed correctly in the Inspector of Firefox.

    Hi dreerr, at first I got the same results you got, but then I noticed that the font download was being blocked by NoScript, so another font was being substituted. After I allowed the font download, Firefox lined up with IE9 and Chrome (on Windows 7 Pro 64-bit).

  • Font rendering change after upgrade

    After upgrading freetype from current to the latest version I noticed that my fonts changed. The rendering was thicker, as in most other linux distributions. Not that it was bad, but I prefer the thin ones Arch had up to now.To solve it I just downgraded freetype to the previous version and everything is fine, but I wonder if the change is due to the way both versions are configured/compiled or is it an internal change in freetype?
    I ask because I'd like to keep this thinner fonts, so I want to know if I should just stop upgrading freetype forever or could I recompile the latest version to get this kind of fonts?

    Bogart wrote:
    slackhack wrote:btw, do you have TFT or CRT? i have a TFT and have tried autohinting both on and off, but it looks like total crap with it off.
    I have a CRT, since TFT screens hurt my eyes with their crispness. I prefer the smooth CRT image. I use the defult hinting (medium), though I've found that if I turn it to full hinting I get the thinner fonts too with this latest freetype, so now I can choose without the need to downgrade.
    that must be the reason, because i have a TFT and just upgraded to the latest freetype2/fontconfig, and the fonts look worse than ever. changing hintfull to hintmedium in ~/.fonts.conf has no effect whatsoever. i moved the /etc/fonts/conf.d directory, no effect, removed local.conf, no effect. nothing seems to fix them, it's really annoying.  and worst of all, the old freetype2 isn't installing because it requires an older fontconfig, and when i try to install an older fontconfig, i get some libexpat library error and everything crashes when i try to launch it.
    >>update: i just checked in gnome, and the fonts look really good there. XFCE4 must use some different method of hinting the fonts than gnome, which i thought uses the freetype2 autohinter. i changed hinting to medium in the xfce4 UI settings, and that improved things a little, even though i have hintmedium set in ~/.fonts.conf. maybe xfce4 uses the BCI hinter and bypasses the freetype hinter?

  • Bold font is too wide in browsers

    I actually have Linux Mint installed, but searching google indicates that the Archlinux forum has far and away the most expertise with the gnome font system, including a very informative wiki page that I have read and tried to apply, unfortunately to no avail.
    The reason I'm asking this question is that I feel like I'm so close to having a gorgeous desktop, but what looks like a rendering error looks like it may frustrate me every time I surf the web.
    I've used advanced settings (which I installed following a tutorial) to set my system font to Sawasdee, which looks very good. In fact, I would call Sawasdee the best looking screen font, by my personal preference, that I've ever used.My problem is that bold text is too thick, but pretty much only in browsers, chrome and firefox.
    The Sawasdee font family has a great bold but for one reason or another that is not what is rendering, instead it looks like the browsers are taking the regular, elegant Sawasdee font and making it two or three times as wide.
    Is there a setting just to tell the system how to handle bold text?
    Below is a link to an image of the linux mint forum where I think the text that is not bold looks close to perfect, but the text that is bold looks almost unreadable:
    http://imgur.com/owffN.png
    Below is how the fonts look in the system and how firefox renders them:
    http://i.imgur.com/MXbuM.png
    It seems to me that the problem is that the applications are making their own bold font instead of using the one available. I wonder if I could rename a file or alter a config line somewhere to correct that.
    So far, I've added this to an /etc/fonts/local.conf file that I made using the header from font.conf but it did not help
    <match target="font">
        <test name="weight" compare="more">
            <const>medium</const>
        </test>
        <edit name="autohint" mode="assign">
            <bool>false</bool>
        </edit>
    </match>
    I really appreciate any help I can get.  If there is more information that might be helpful, I am eager to provide it.
    Last edited by ra1110laptop (2011-12-06 07:32:17)

    Sorry but we can give assistance for original Arch Linux only. Please ask on a Linux Mint forum for detailed help.
    But there is quite some information about your issue in the Arch forums and the wiki. Some quick search should help.
    Closing.

  • 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?

  • Font rendering issue / Mountain Lion / non Apple LCD display

    Hello
    This font rendering issue or problem is probably well know by Apple crew too but nobody has solved it yet. Only poor solution are available such as try to adjust manually font rendering by writin some scripts concerning anti alias levels...they really dont solve the problem.
    Could Apple bring us solution to this by developing or updating Mountain Lion?
    So what is the problem: font rendering is very poor in Mountain Lion when using non Apple LCD. For example Fujitsu SL27T-1 LED (LCD displa) shows fonts very nice way in Windows but in Mac OS ML does not. Somebody told me that its about software vs. hardware rendering. Dont know about that but could you bring me the solution which is not advising me to buy Apple display (which is five times more expensive than other manufactures displays).
    Br
    M. Leino

    just want to add that overall fonts look blurry and they are not very sharp.

  • 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 is poor after a hard reset

    After a crash, I had to power off my MBP. Since it rebooted the font rendering has been poor. I have posted an image here to show you the difference. It is slight, but the font rendering used to be much more crisp. Now they appear too soft and blurred around the edges.
    http://img.skitch.com/20100508-xmrup6hx2q3eqqqkj6rekhg6hc.png
    Can anyone tell me what might have happened and how to fix it?
    Thanks!
    Mason

    Looking at the image, it seems that your computer has changed its font smoothing setting.
    You can alter this by going to System Preferences->Appearance and ticking the "Use LCD font smoothing when available" box.
    It doesn't apply to running applications, so you need to quit and restart Safari to see the change.

  • [Solved] Powerline font 1px too high, using fontconfig w/ infinality

    Hey guys,
    I'm using the Termite terminal emulator which uses fontconfig for font rendering options. I'm also using vim powerline.
    I use the Monaco font and have installed the otf-powerline-symbols-git package.
    This is what my powerline looks like up close. As you can see the symbols appear to be 1px too high.
    Here's my font config
    <?xml version="1.0"?>
    <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
    <fontconfig>
    <!-- Use Monaco for everything monospace -->
    <match target="pattern">
    <test qual="any" name="family"><string>Consolas</string></test>
    <edit name="family" mode="assign" binding="same">
    <string>Monaco</string>
    </edit>
    </match>
    <match target="pattern">
    <test qual="any" name="family"><string>Courier</string></test>
    <edit name="family" mode="assign" binding="same">
    <string>Monaco</string>
    </edit>
    </match>
    <match target="pattern">
    <test qual="any" name="family"><string>Courier New</string></test>
    <edit name="family" mode="assign" binding="same">
    <string>Monaco</string>
    </edit>
    </match>
    <alias>
    <family>monospace</family>
    <prefer>
    <family>Monaco</family>
    <family>Consolas</family>
    </prefer>
    </alias>
    <!-- Monaco is a little bit to large, making fallback fonts look small -->
    <match target="font">
    <test name="family"><string>Monaco</string></test>
    <edit name="pixelsize" mode="assign">
    <times><name>pixelsize</name>, <double>0.9</double></times>
    </edit>
    </match>
    </fontconfig>
    It doesn't seem like there's a fontconfig option to move the font's baseline down. Any ideas?
    Last edited by EvanPurkhiser (2013-08-10 02:45:35)

    Thanks bohoomil, I tried changing this setting (it was already set to true since I'm using your infinality bundle!) but it didn't seem to have an effect.
    It looks like I can fix this alignment issue by actually editing the OTF symbols font with fontforge. But it would be much nicer if there was some kind of setting I could change so I could use the upstream font.
    Edit: Reading through the issues, it looks like it's common practice to just accept that the font needs to be edited on a per-system basis.
    Last edited by EvanPurkhiser (2013-08-10 01:21:06)

  • [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">
    <!-- /etc/fonts/fonts.conf file to configure system font access -->
    <fontconfig>
    <!--
    DO NOT EDIT THIS FILE.
    IT WILL BE REPLACED WHEN FONTCONFIG IS UPDATED.
    LOCAL CHANGES BELONG IN 'local.conf'.
    The intent of this standard configuration file is to be adequate for
    most environments. If you have a reasonably normal environment and
    have found problems with this configuration, they are probably
    things that others will also want fixed. Please submit any
    problems to the fontconfig bugzilla system located at fontconfig.org
    Note that the normal 'make install' procedure for fontconfig is to
    replace any existing fonts.conf file with the new version. Place
    any local customizations in local.conf which this file references.
    Keith Packard
    -->
    <!-- Font directory list -->
    <dir>/usr/share/fonts</dir>
    <dir>~/.fonts</dir>
    <!--
    Accept deprecated 'mono' alias, replacing it with 'monospace'
    -->
    <match target="pattern">
    <test qual="any" name="family">
    <string>mono</string>
    </test>
    <edit name="family" mode="assign">
    <string>monospace</string>
    </edit>
    </match>
    <!--
    Accept alternate 'sans serif' spelling, replacing it with 'sans-serif'
    -->
    <match target="pattern">
    <test qual="any" name="family">
    <string>sans serif</string>
    </test>
    <edit name="family" mode="assign">
    <string>sans-serif</string>
    </edit>
    </match>
    <!--
    Accept deprecated 'sans' alias, replacing it with 'sans-serif'
    -->
    <match target="pattern">
    <test qual="any" name="family">
    <string>sans</string>
    </test>
    <edit name="family" mode="assign">
    <string>sans-serif</string>
    </edit>
    </match>
    <!--
    Load local system customization file
    -->
    <include ignore_missing="yes">conf.d</include>
    <!-- Font cache directory list -->
    <cachedir>/var/cache/fontconfig</cachedir>
    <cachedir>~/.fontconfig</cachedir>
    <config>
    <!--
    These are the default Unicode chars that are expected to be blank
    in fonts. All other blank chars are assumed to be broken and
    won't appear in the resulting charsets
    -->
    <blank>
    <int>0x0020</int> <!-- SPACE -->
    <int>0x00A0</int> <!-- NO-BREAK SPACE -->
    <int>0x00AD</int> <!-- SOFT HYPHEN -->
    <int>0x034F</int> <!-- COMBINING GRAPHEME JOINER -->
    <int>0x0600</int> <!-- ARABIC NUMBER SIGN -->
    <int>0x0601</int> <!-- ARABIC SIGN SANAH -->
    <int>0x0602</int> <!-- ARABIC FOOTNOTE MARKER -->
    <int>0x0603</int> <!-- ARABIC SIGN SAFHA -->
    <int>0x06DD</int> <!-- ARABIC END OF AYAH -->
    <int>0x070F</int> <!-- SYRIAC ABBREVIATION MARK -->
    <int>0x115F</int> <!-- HANGUL CHOSEONG FILLER -->
    <int>0x1160</int> <!-- HANGUL JUNGSEONG FILLER -->
    <int>0x1680</int> <!-- OGHAM SPACE MARK -->
    <int>0x17B4</int> <!-- KHMER VOWEL INHERENT AQ -->
    <int>0x17B5</int> <!-- KHMER VOWEL INHERENT AA -->
    <int>0x180E</int> <!-- MONGOLIAN VOWEL SEPARATOR -->
    <int>0x2000</int> <!-- EN QUAD -->
    <int>0x2001</int> <!-- EM QUAD -->
    <int>0x2002</int> <!-- EN SPACE -->
    <int>0x2003</int> <!-- EM SPACE -->
    <int>0x2004</int> <!-- THREE-PER-EM SPACE -->
    <int>0x2005</int> <!-- FOUR-PER-EM SPACE -->
    <int>0x2006</int> <!-- SIX-PER-EM SPACE -->
    <int>0x2007</int> <!-- FIGURE SPACE -->
    <int>0x2008</int> <!-- PUNCTUATION SPACE -->
    <int>0x2009</int> <!-- THIN SPACE -->
    <int>0x200A</int> <!-- HAIR SPACE -->
    <int>0x200B</int> <!-- ZERO WIDTH SPACE -->
    <int>0x200C</int> <!-- ZERO WIDTH NON-JOINER -->
    <int>0x200D</int> <!-- ZERO WIDTH JOINER -->
    <int>0x200E</int> <!-- LEFT-TO-RIGHT MARK -->
    <int>0x200F</int> <!-- RIGHT-TO-LEFT MARK -->
    <int>0x2028</int> <!-- LINE SEPARATOR -->
    <int>0x2029</int> <!-- PARAGRAPH SEPARATOR -->
    <int>0x202A</int> <!-- LEFT-TO-RIGHT EMBEDDING -->
    <int>0x202B</int> <!-- RIGHT-TO-LEFT EMBEDDING -->
    <int>0x202C</int> <!-- POP DIRECTIONAL FORMATTING -->
    <int>0x202D</int> <!-- LEFT-TO-RIGHT OVERRIDE -->
    <int>0x202E</int> <!-- RIGHT-TO-LEFT OVERRIDE -->
    <int>0x202F</int> <!-- NARROW NO-BREAK SPACE -->
    <int>0x205F</int> <!-- MEDIUM MATHEMATICAL SPACE -->
    <int>0x2060</int> <!-- WORD JOINER -->
    <int>0x2061</int> <!-- FUNCTION APPLICATION -->
    <int>0x2062</int> <!-- INVISIBLE TIMES -->
    <int>0x2063</int> <!-- INVISIBLE SEPARATOR -->
    <int>0x206A</int> <!-- INHIBIT SYMMETRIC SWAPPING -->
    <int>0x206B</int> <!-- ACTIVATE SYMMETRIC SWAPPING -->
    <int>0x206C</int> <!-- INHIBIT ARABIC FORM SHAPING -->
    <int>0x206D</int> <!-- ACTIVATE ARABIC FORM SHAPING -->
    <int>0x206E</int> <!-- NATIONAL DIGIT SHAPES -->
    <int>0x206F</int> <!-- NOMINAL DIGIT SHAPES -->
    <int>0x2800</int> <!-- BRAILLE PATTERN BLANK -->
    <int>0x3000</int> <!-- IDEOGRAPHIC SPACE -->
    <int>0x3164</int> <!-- HANGUL FILLER -->
    <int>0xFEFF</int> <!-- ZERO WIDTH NO-BREAK SPACE -->
    <int>0xFFA0</int> <!-- HALFWIDTH HANGUL FILLER -->
    <int>0xFFF9</int> <!-- INTERLINEAR ANNOTATION ANCHOR -->
    <int>0xFFFA</int> <!-- INTERLINEAR ANNOTATION SEPARATOR -->
    <int>0xFFFB</int> <!-- INTERLINEAR ANNOTATION TERMINATOR -->
    </blank>
    <!--
    Rescan configuration every 30 seconds when FcFontSetList is called
    -->
    <rescan>
    <int>30</int>
    </rescan>
    </config>
    </fontconfig>
    Infinality.conf:
    <?xml version='1.0'?>
    <!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
    <fontconfig>
    <!-- Choose an OS Rendering Style. This will determine B/W, grayscale,
    or subpixel antialising and slight, full or no hinting and replacements (if set in next option) -->
    <!-- Style should also be set in the infinality-settings.sh file, ususally in /etc/profile.d/ -->
    <!-- Choose one of these options:
    Infinality - subpixel AA, minimal replacements/tweaks, sans=Arial
    Windows 7 - subpixel AA, sans=Arial
    Windows XP - subpixel AA, sans=Arial
    Windows 98 - B/W full hinting on TT fonts, grayscale AA for others, sans=Arial
    OSX - Slight hinting, subpixel AA, sans=Helvetica Neue
    OSX2 - No hinting, subpixel AA, sans=Helvetica Neue
    Linux - subpixel AA, sans=DejaVu Sans
    === Recommended Setup ===
    Run ./infctl.sh script located in the current directory to set the style.
    # ./infctl.sh setstyle
    === Manual Setup ===
    See the infinality/styles.conf.avail/ directory for all options. To enable
    a different style, remove the symlink "conf.d" and link to another style:
    # rm conf.d
    # ln -s styles.conf.avail/win7 conf.d
    -->
    <!-- Uncomment this to reject all bitmap fonts -->
    <!-- Make sure to run this as root if having problems: fc-cache -f -->
    <!--
    <selectfont>
    <rejectfont>
    <pattern>
    <patelt name="scalable" >
    <bool>false</bool>
    </patelt>
    </pattern>
    </rejectfont>
    </selectfont>
    -->
    <!-- Ban Type-1 fonts because they render poorly -->
    <!-- Comment this out to allow all Type 1 fonts -->
    <selectfont>
    <rejectfont>
    <pattern>
    <patelt name="fontformat" >
    <string>Type 1</string>
    </patelt>
    </pattern>
    </rejectfont>
    </selectfont>
    <!-- Globally use embedded bitmaps in fonts like Calibri? -->
    <match target="font" >
    <edit name="embeddedbitmap" mode="assign">
    <bool>false</bool>
    </edit>
    </match>
    <!-- Substitute truetype fonts in place of bitmap ones? -->
    <match target="pattern" >
    <edit name="prefer_outline" mode="assign">
    <bool>true</bool>
    </edit>
    </match>
    <!-- Make (some) monospace/coding TTF fonts render as bitmaps? -->
    <!-- courier new, andale mono, monaco, etc. -->
    <match target="pattern" >
    <edit name="bitmap_monospace" mode="assign">
    <bool>false</bool>
    </edit>
    </match>
    <!-- Force autohint always -->
    <!-- Useful for debugging and for free software purists -->
    <match target="font">
    <edit name="force_autohint" mode="assign">
    <bool>false</bool>
    </edit>
    </match>
    <!-- Set DPI. dpi should be set in ~/.Xresources to 96 -->
    <!-- Setting to 72 here makes the px to pt conversions work better (Chrome) -->
    <!-- Some may need to set this to 96 though -->
    <match target="pattern">
    <edit name="dpi" mode="assign">
    <double>96</double>
    </edit>
    </match>
    <!-- Use Qt subpixel positioning on autohinted fonts? -->
    <!-- This only applies to Qt and autohinted fonts. Qt determines subpixel positioning based on hintslight vs. hintfull, -->
    <!-- however infinality patches force slight hinting inside freetype, so this essentially just fakes out Qt. -->
    <!-- Should only be set to true if you are not doing any stem alignment or fitting in environment variables -->
    <match target="pattern" >
    <edit name="qt_use_subpixel_positioning" mode="assign">
    <bool>false</bool>
    </edit>
    </match>
    <!-- Run infctl.sh or change the symlink in current directory instead of modifying this -->
    <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.

  • Ugly font rendering in chromium 5.0.375.

    Hi!,
    The last update to  chromim 5.0.375,  the rendering fonts is too ugly, so I have to down to the previus version of package 5.0.342.
    I probe settins de .Xdefaults system, but ignore me.  Is anyone occur this issue ?.
    I've a X64 System.
    thanks in advance !!

    alexk wrote:
    edtler wrote:The last update to  chromim 5.0.375,  the rendering fonts is too ugly, so I have to down to the previus version of package 5.0.342.
    I probe settins de .Xdefaults system, but ignore me.  Is anyone occur this issue ?.
    I have the same problem. Rolling back to 5.0.342 fixes it.
    fsckd wrote:Maybe: http://bbs.archlinux.org/viewtopic.php?id=98189
    It looks like a different issue.
    Could u please provide old package v5.0.342?

  • [SOLVED] Bad font rendering and overlapping since last update

    Hi all! Since the last updates I'm getting font rendering problems. I'm seeing something like this in lots of applications:
    See the "ce" in Facebook, those letters are kinda overlapped! This happens in Nautilus too, for example in the word "devel". I'm using the Ubuntu patches for font rendering, but actually I have problems even with the stock packages.
    I'm on a fresh install right now (I really needed to clean the old one, too much experimenting xD) and I keep having this problem.
    Can anyone help me?
    SOLVED I downgraded pango from 1.32.1-1 to 1.30.1-1 and everything went back to normality
    Last edited by Gianfrix (2012-11-06 14:09:00)

    brebs wrote:https://bugs.archlinux.org/task/32612?project=1
    That seems to be an issue. Downgrading to  xorg-server 1.13.0-3 resolved problem. Watching ticket for future updates. Thanks a lot
    Last edited by mamciek (2012-11-20 22:02:58)

  • UGLY font rendering in Firefox

    Hello, my font rendering in Firefox is very ugly. I don't know what to do
    I installed ttf-google-fonts-git and also put 70-no-bitmaps.conf in my /etc/fonts/conf.d/ directory but this doesn't change anything. I reinstalled ttf-google-fonts-git and firefox but nothing.
    Here is what I got : http://f.too.gy/font-rendering.png

    (/etc/fonts/conf.d) Stewie $ ls
    10-powerline-symbols.conf           57-dejavu-sans.conf
    10-scale-bitmap-fonts.conf           57-dejavu-sans-mono.conf
    20-unhint-small-dejavu-sans.conf       57-dejavu-serif.conf
    20-unhint-small-dejavu-sans-mono.conf  60-latin.conf
    20-unhint-small-dejavu-serif.conf      65-fonts-persian.conf
    20-unhint-small-vera.conf           65-nonlatin.conf
    30-metric-aliases.conf               69-unifont.conf
    30-urw-aliases.conf               70-no-bitmaps.conf
    40-nonlatin.conf               75-yes-terminus.conf
    42-luxi-mono.conf               80-delicious.conf
    45-latin.conf                   90-synthetic.conf
    49-sansserif.conf               99pdftoopvp.conf
    50-user.conf                   README
    51-local.conf

  • Font Rendering Got Bad After 32.0 Update

    After the recent update, the font started to get badly rendered. Kind of blurry with jagged edges and transparent parts. It used to be okay D:
    Sometimes it becomes okay for a moment as I scroll down on pages, and sometimes when I stop scrolling, the font stays as it is; as if there are specific positions for the text to render properly. However, not all of the fonts are affected. Only the ones inside the scroll area.
    On times that the font renders properly, the bookmarks font, title bar, and tab names are unaffected and still appear not-smooth. Same thing does not happen on other browsers. All my other system fonts look okay; it's really just Firefox.
    Restarting Firefox = didn't work
    Restarting Computer = didn't work
    Tried setting up Clear Type = didn't work
    Tried enabling and disabling Hardware Acceleration on Firefox = didn't work
    Tried enabling and disabling the Graphics card itself = didn't work
    Tried just about all of the suggestions I found on Google = none worked
    Tried complete uninstall and re-install of Firefox 32.0 = didn't work
    Graphics Driver are updated ~
    Windows is updated ~
    I'm using Windows 7 Ultimate 32 bit
    Graphics AMD Radeon HD 6800
    I fixed it by downgrading to Firefox 31 which makes me sure that 32.0 is the culprit. As I was about to send the message on top; I tried downgrading as my last resort and it worked. Now I'm only sending this as a report. I am hoping you'll figure out what caused it because I am quite strict (OC) that everything in my PC must remain updated >_<; thus I want to use Firefox 32.0 as much as possible.

    No one to help on this ??????

  • 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>

Maybe you are looking for