[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.

Similar Messages

  • [solved] laggy X Core Font rendering after today's updates

    I've got an interesting issue after applying today's updates of kernel, X server, and nouveau, and I'd like some of you to try reproducing it, in the hope that it will help me figure out which component is causing it. Rendering of X Core Fonts, AKA XLFD (non-Freetype fonts) is laggy. When some text in such a font should be drawn, space is made to display it, but the text doesn't appear until I push a key or wiggle the mouse.
    Please try this experiment: Open a terminal (urxvt or plain xterm will do) using an old-school "fixed" font. I used 7x14 for my testing. Run "sleep 1" in this terminal and don't touch anything after hitting enter. If you find that most of the time, the prompt doesn't come back when sleep exits until you use the keyboard or mouse, you've duplicated the issue. It's also fairly easy to notice just by typing normally in such a terminal as the input echoes back rather slowly. It feels as it server-side font rendering is hung up by the server waiting on an event that really shouldn't be involved with fonts.
    I'm running nouveau on a GT9400, and applied these updates tonight:
    [2011-01-30 18:59] upgraded kernel26 (2.6.36.3-2 -> 2.6.37-5)
    [2011-01-30 18:59] upgraded libdrm (2.4.22-3 -> 2.4.23-1)
    [2011-01-30 18:59] upgraded libgl (7.9.0.git20101207-2 -> 7.10-1)
    [2011-01-30 18:59] upgraded libva (1.0.6-1 -> 1.0.8-1)
    [2011-01-30 18:59] upgraded mesa (7.9.0.git20101207-2 -> 7.10-1)
    [2011-01-30 18:59] upgraded xf86-video-nouveau (0.0.16_git20100819-2 -> 0.0.16_git20101217-1)
    [2011-01-30 18:59] upgraded xorg-server-common (1.9.2-2 -> 1.9.3.901-1)
    [2011-01-30 18:59] upgraded xorg-server (1.9.2-2 -> 1.9.3.901-1)
    I'd be especially interested if it's broken for anyone not running nouveau, or who didn't update all of these components. Once I narrow it down a bit, I'll open a bug (either here, or upstream somewhere). It's easy to work around, by just using a TrueType font in my terminals instead, but still worth a bit of investigation.
    Last edited by ataraxia (2011-02-07 04:55:32)

    I had this trouble when I upgraded to
    xf86-video-nouveau-git (20110206-1)
    and had to upgrade to
    libdrm (2.4.23-1)
    Fixed by rolling back to
    xf86-video-nouveau (0.0.16_git20100819-1)
    libdrm (2.4.21-1)
    I'm running the very latest Nouveau git kernel modules, but going back several versions made no difference.
    [edit: bug filed upstream]
    Last edited by jhl (2011-02-07 03:32:49)

  • Poor Font Rendering - Not very smooth!

    My fonts are rendering poorly in Indesign even when viewing at 100% viewed as High Quality Display.
    Am working on an iMac - Indesign CC. Trying to put a Resume together. Macs own program "Pages" actually seems to be rendering smoother fonts.
    Would appreciate any advice

    Thanks Jeffrey much appreciated. Had already got AA ticked in preferences...although it is better than when turned off Fonts and dotted lines still look somewhat pixelated compared to say text in "Pages" - Macs version of Word.
    Cheers
    Rob

  • [SOLVED] Font rendering doesn't work as expected on github

    Hey!
    I have a problem with the font rendering on github. On Windows it looks normal, but on Arch it looks a bit bold.
    Here a comparison picture how it looks on my arch desktop and on my windows desktop:
    So, how can I solve this problem?
    Thanks in advance!
    Last edited by sh4nks (2014-01-10 15:33:39)

    As per bohoomil's recommendation, I created and installed the ttf-ms-win8 font package.  At some point, I had an issue with libreoffice actually not actually showing any fonts at all.  After much browsing, I found others who reported the same thing and that the removal of the ms fonts solved the issue (it turned out to be segoe I think).  In the mean time, I tried using the google fonts (ttf-google-fonts-git) and was quite pleased with them… until I navigated to the github page, which was awful.  So in the end, I resintalled the ttf-ms-win8 font package, as the free fonts were apparently insufficient.
    So the point of this story is that although I think you can "fix" things to a degree by modifying the font configurations, this is actually a simple case of not having the available font on one's system (and github defaulting to something crappy, as mentioned by nfisher.sr above). 
    Take this story/post with a pinch of salt though, as I simply put my font configuration needs in the hands of the amazingly capable bohoomil and his infinality-bundle.  I just do what he tells me to do, and my fonts look amazing.

  • Font rendering issue & multimedia keys not working

    Hi, yesterday i switched to KDEmod 4.1 and I have two major problems...
    One is font rendering issue... I did not change anything in my font-related packages (cairo, freetype, fontconfig, libxft) and i have to add that this setup worked perfectly in KDEmod 3.5.9, but now it looks like this:
    This bug occurs only in qt apps and mostly in kmenu... i.e firefox renders my fonts flawlessly...
    Second problem are multimedia keys on my keyboard...
    They worked in KDE 3.5.9, but now I cannot set them up properly... Sometimes they work, sometimes they don't...
    KDE recognizes the pressed key, but when I assign specific action and press the key, just nothing happens...

    You might be able to solve your font issue by going to System Settings -> Appearance -> Fonts.  I enable ant-aliasing.  I also clicked on configure and select "Use sub-pixel rendering" to RGB and the hinting style to Full.  I also use the Force fonts DPI to 96 DPI.  This makes the fonts pleasing to my eyes.
    This is how I got my multimedia keys to work in KDE4.1:
    Go to System Settings -> Regional and Language and make sure to set the County or region to your location.
    khotkeys needs to be running.  I added it to the autostarted progam list. System Settings -> Advanced tab -> Autostart
    When I got the multimedia keys working, I was really tring to get the keyboard shortcuts to work.  In addition to the above steps, I also deleted
    ~/.kde4/share/config/kglobalshortcutsrc.  I do not know if deleting this file is needed to get the multimedia keys working, but it was to get the keyboard shortcuts woring.
    Restart X
    Go to  System Settings -> Keyboard and Mouse -> Keyboard Shortcuts
    I set the volume control in the KMix component section.
    To get the keyboard shortcuts to work, go to the menu editor and select the program you want to create a shortcuts for.  Click on the advanced tab and create the shortcut in the shortcut field.  Save.
    Then go to  System Settings -> Keyboard and Mouse -> Keyboard Shortcuts. Change the component to KHotkeys.  Select the Program and then select the default shortcut that you just created.  (This works for the multimedia keys aswell).
    Hope this helps,
    pudge

  • Some web fonts are not rendered

    When I visit some sites that use web fonts, the web fonts are not rendered. It does not render with the wrong font - the text is completely invisible.
    On other sites, web fonts work just fine, and I cannot understand why some web fonts work and some don't.
    Examples of non-working sites:
    http://blog.mailchimp.com/ (headers shown, article text missing)
    https://www.sbab.se/ (huge top header missing)
    http://onlinepizza.se/ (headers and button texts missing)
    Examples of working sites:
    http://www.google.com/fonts
    http://www.typetester.org/
    On the Network -> Fonts tab in the inspector, no downloads are shown on the broken sites. Is there a font cache that I can delete?
    I have tried uninstalling firefox, deleting all profiles and installing it again. Nothing changes.

    Works fine here on Linux.
    Right-click > "Inspect Element" > Font shows:
    *http://blog.mailchimp.com/ Copyright (C) H&FJ | typography.com (Whitney SSm B) & Copyright (C) H&FJ | typography.com (Whitney SSm A)
    *https://www.sbab.se/ SBABSansStencilBeta-Bold
    *http://onlinepizza.se/Stockholm/ MuseoSans-700
    Start Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
    *Do NOT click the Reset button on the Safe Mode start window.
    *https://support.mozilla.org/kb/Safe+Mode
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
    Reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.
    *Hold down the Shift key and left-click the Reload button
    *Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
    *Press "Command + Shift + R" (Mac)

  • Font rendering is not always accurate, and bullets are sometimes just pinpoints. Is there a way to fix this?

    for instance, in the website I created, www.menletter.org, the fonts are not the ones I created and the bullets are pinpoints. Seems to do fine in MS IE.

    With all due respect, that isn't a real web page. It's a Word document with html tags, which is only going to be rendered completely in IE and other browsers that play loose with the standards. Right-click that page in Firefox and select View Page Source, everything in green is code that isn't valid and code that Firefox ignores. You need a better "tool" to create web pages that work correctly in all browsers that follow W3C standards.
    http://kompozer.net/

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

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

  • [SOLVED] Bad font rendering after last update (pango issue?)

    I am getting very strange font rendering problem. Look at the screen below. It only affects gtk windows (as you can see below HTML text is currently displayed, but url bar and context menu is not). I belive it appeared after upgrading pango package to 1.32, but downgrading it as instructed here (https://bbs.archlinux.org/viewtopic.php?id=151886), didn't help. Does anybody know what can it be? Any hints where to look for the solution?
    Maciej
    Last edited by mamciek (2012-11-20 22:01:45)

    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)

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

  • [solved]Wine font rendering + libmpg123 question

    Not sure how to describe the problem, so please refer to screenshot below. I have the MS font package installed. I've modified the registry according to the wine wiki article. I tried symlinking my ttf fonts directory to the .wine/drive_c/windows/Fonts directory. I have even tried copying the entire ttf directly into the .wine/drive_c/windows/Fonts directory. I still cannot read anything. As you can see from the screenshot, the Tahoma font example shows up clearly, but nothing else is legible. What can I do to get to the bottom of this?
    Additionally, I get this error when I invoke wine.
    err:module:load_builtin_dll failed to load .so lib for builtin L"winemp3.acm": libmpg123.so.0: cannot open shared object file: No such file or directory
    Is this related to my issue? I thought libmpg123 only affected mp3 support. Is it necessary to have libmpg123? I assumed it wasn't since it's not in any of the repos.
    Last edited by drtoki (2009-09-09 20:04:22)

    i get the same 'winemp3' stuff.
    Wine now uses external 'libmpg123' for mp3 decoding. (patent issues)
    maybe the arch devs need to add '--without-libmpg123' in the build, to fix this.
    http://forum.winehq.org/viewtopic.php?t … =libmpg123
    regarding the fonts, try;
    Installing 'ttf-ms-fonts' and 'ttf-tahoma'
    link the installed Truetype fonts to wine;
    # ln -s /usr/share/fonts/TTF /usr/share/wine/fonts
    btw Wine is starting to use alot of external native nix packages now, which is a good thing. (i.e. ms fonts, decoders ect..)
    Last edited by gav616 (2009-09-07 14:06:02)

  • [SOLVED]where I can specify where are my font if not using xorg.conf

    where I can specify where are my font if not using xorg.conf
    thanks
    Last edited by jccl1706 (2010-04-01 18:06:45)

    You can try to this in ~/.xinitrc :
    xset +fp /usr/share/fonts/local
    or any other path.

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

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

Maybe you are looking for

  • Itunes wont open, error messages instead

    Upon opening itunes i get: iTunes.exe - Bad image C:\Program Files (x86)\ Common Files\Apple\Apple Aplication Support\libxml2.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original in

  • Keynote: Some images are missing

    Ever since I upgraded to Keynote 6.2 and Mac OS 10.9.3 my images are deleted somewhere between me saving the file, and retrieving the file again later. Last night I was working on a brand new presenation I created (not upgraded or imported). Everythi

  • Won't load application/vnd.wap.xhtml+xml

    Used to view 511NY.org (Road conditions) on FF 3.X. Upgraded to FF 4 and now asks me what to do with 511NY.org because it's an application/vnd.wap.xhtml+xml. Asks do I want to Save it or Open it? I say Open it with FF, then instead FF4 downloads a pa

  • EM and OEM on linux

    Hi guys I did a clean install 10gr2 on linux over ASM the problem is.: in the first days EM was reachable by the url machine.mydomain.org:1158/em after a week (no changes overall) i just can reach via IP 192.168.xxx.xxx:1158/em now is unreachable...

  • Malfunction with playing demo.

    Hey, in the itunes store when I'm playing a song as a demo it will cut off randomly. It's supposed to play for a minute thirty, but wil cut off after ten or twenty seconds. What's the problem? It's never happened before and just started today.