Chromium weird font rendering

Hey,
i was wondering if anyone else has the same problem with chromium font rendering,
i already tried setting the .Xresources as stated on wiki, but it didnt seem to take
effect.
I also tried the fonts.conf from this thread: https://bbs.archlinux.org/viewtopic.php?id=130572
but with no results, what i get is this:
http://imagebin.org/209104 (left is firefox, right is chromium) in sharelatex website.
Even the tabs text look weird.
Anyone knows how to solve this?
Thanks!
EDIT: In Epiphany and chrome (in windows), look like the firefox screenie.
Last edited by Micah89 (2012-04-21 20:00:29)

There are some tips in here: https://bbs.archlinux.org/viewtopic.php?id=139543

Similar Messages

Weird font rendering glitch in firefox

Hi all,
When I look at this webpage in Firefox this is what I get:
Notice how every occurrence of "ff" and "ft" look weird.
This is Mozilla Firefox 13.0.1.
System & Xorg info:
knarf ~ > Xorg -version
X.Org X Server 1.12.3
Release Date: 2012-07-09
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.4.4-3-ARCH x86_64
Current Operating System: Linux paf 3.4.4-3-ARCH #1 SMP PREEMPT Tue Jul 3 14:36:44 UTC 2012 x86_64
Kernel command line: root=/dev/sda3 ro
Build Date: 09 July 2012 03:59:39PM
Current version of pixman: 0.26.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Font-related installed packages:
knarf ~ > pacman -Qs ttf
local/ttf-dejavu 2.33-3
Font family based on the Bitstream Vera Fonts with a wider range of characters
local/ttf-freefont 20120503-1
Set of free outline fonts covering the Unicode character set
knarf ~ > pacman -Qs font
local/fontconfig 2.8.0-2
A library for configuring and customizing font access
local/fontforge 20120119-1
Outline and bitmap font editor
local/fontsproto 2.1.2-1
X11 font extension wire protocol
local/freetype2 2.4.10-1
TrueType font rendering library
local/libfontenc 1.1.1-1
X11 font encoding library
local/libxfont 1.4.5-1
X11 font rasterisation library
local/libxft 2.3.1-1
FreeType-based font drawing library for X
local/ttf-dejavu 2.33-3
Font family based on the Bitstream Vera Fonts with a wider range of characters
local/ttf-freefont 20120503-1
Set of free outline fonts covering the Unicode character set
local/xorg-bdftopcf 1.0.3-2 (xorg xorg-apps)
Convert X font from Bitmap Distribution Format to Portable Compiled Format
local/xorg-font-util 1.3.0-1 (xorg-fonts xorg)
X.Org font utilities
local/xorg-font-utils 7.6-3
Transitional package depending on xorg font utilities
local/xorg-fonts-alias 1.0.2-2
X.org font alias files
local/xorg-fonts-encodings 1.0.4-3 (xorg-fonts xorg)
X.org font encoding files
local/xorg-fonts-misc 1.0.1-2
X.org misc fonts
local/xorg-mkfontdir 1.0.7-1 (xorg xorg-apps)
Create an index of X font files in a directory
local/xorg-mkfontscale 1.1.0-1 (xorg-apps xorg)
Create an index of scalable font files for X

ewaller wrote:It is interesting to note those combinations are typographic ligatures. I'll bet two credits that is not a coincidence.
I bet my credits the fault is within the Calibri font.
You can do a font substitution for Calibri. I made the change for all users. Before anyone does this they might check, from the command line, what font is being used for Calibri: 'fc-match Calibri'
In /etc/fonts/conf.avail/ I added the file, 39-no-calibri.conf:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>

<match target="pattern" name="family">
<test name="family" qual="any">
<string>Calibri</string>
</test>
<edit mode="assign" name="family">
<string>Arial</string>
<string>Liberation Sans</string>
<string>sans-serif</string>
</edit>
</match>
</fontconfig>
Then I symlinked to it from /etc/fonts/conf.d/:
# pwd
/etc/fonts/conf.d
# ln -s /etc/fonts/conf.avail/39-no-calibri.conf
Finally, I updated the font cache with 'fc-cache -vf'.

Weird Font Rendering Issue?

Okay i was looking fo some back up drives online, and i stumbled upon:
http://www.circuitcity.com/ssm/Seagate-Barracuda-7200-9-500GB-Internal-Drive-ST3 500641ARK/sem/rpsm/oid/168899/catOid/-12976/rpem/ccd/productDetail.do
it renders like this:
http://img512.imageshack.us/img512/4641/picture3rn0.png
http://img218.imageshack.us/my.php?image=picture4dr1.png
but for some reason on my MacPro 2.66 the font renders odd in FireFox (doenst do it on Safari. and ive tried this exact sit eon my MacBookPro and it looks fine on Firefox.
I have the following installed (on both machines)
-FireFox 2.0.0.9
-Microsoft Office 2004
-Adobe CS2
-Macromedia Studio 8
theyre practically identical with programs & fonts installed, the only fonts that are installe are the ones that wer epreinstalled with the system, and that came with Office 04 and CS2
any way to maybe fix this issue?

hey! well i tried your site url on my MacPro and i have the same issue, so it must be a macpro thing? lol
im running the latest firefox and no additional fonts installed other than the ones you have listed yourself (office, cs2, macromedia)
so dont fret. i tried using font finangler and onyx to clean the font cache, (not sure i fhtat was a good idea,) but it shows up on mine so your not the only one! ive tried on two different macpros one wiht out any programs and it does the same thing. so it must be something with the wya its rendering on these machines.
at first it hought maybe something got corrupted in my system aswell
hope that helps!!

Weird font rendering

Hi there,
some fonts (e.g. DejaVu Sans Extralight or the default LaTeX font) render very, very ugly. See http://ubuntu-pics.de/bild/43222/shot_dTzHgC.png and http://ubuntu-pics.de/bild/43223/shot_7Nekzl.png.
I have subpixel rendering (rgb) and antialiasing switched on on a LCD monitor (notebook). How do I get those fonts render correctly?

Check your DPI against a machine that looks good to you.
xdpyinfo | grep resolution

(Tab name) font rendering in Chromium 32

With the latest upgrade to Chromium, it appears that font rendering for tab names worsened slightly. (Unfortunately, I don't have any screenshots beforehand.) This was observed on Chromium 32, x86_64, with the latest versions of vanilla fontconfig and freetype2. I suspect this is an upstream bug, however, as similar issues occurred with Chrome/ium 33 builds.

The subject says it all. Since upgrading from Chromium 31 to chromium 32 I have noticed that the font of tabs has changed I find the new font looks bad. Can I configure the tab font, giving it the previous appearance? See the attached screenshots for details.
Before... (Chromium 31):
...and after (Chromium 32):

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

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

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

<fontconfig>


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

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

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

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

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

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

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

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








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

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

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


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


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



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




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

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

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 in opera

Hi,
I am new to arch linux.
I installed opera browser (which i get used to when i used windows) and I did not get the indic fonts properly rendered. I am particularly concerned about "tamil" fonts. I googled up and followed up some instructions but could not get it in opera. But the font renders correctly in chromium and firefox. So, the problem is concerned with opera? or any system changes should be made?
Here are the screen shots:
Here is what I should get: (used chromium)
Here is what I get in opera:
No matter what fonts I change in advanced-> international option in opera.. it keeps rendering them wrongly.
Thankyou.
Last edited by thinkanish (2013-01-16 13:55:19)

Not sure if this will help, but to fix fonts in my Opera I typed "opera:config" in address bar. Looked up "fontconfig" in search, and made sure "Prefer fontconfig settings" is checked. Save and restart.
Then I made a file /.config/fontconfig/fonts.conf with the following:
<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
<match target="font" >
<edit mode="assign" name="autohint">
<bool>false</bool>
</edit>
</match>
<match target="font" >
<edit mode="assign" name="hinting">
<bool>false</bool>
</edit>
</match>
<match target="font" >
<edit mode="assign" name="rgba">
<const>rgb</const>
</edit>
</match>
<match target="font">
<edit mode="assign" name="lcdfilter">
<const>lcddefault</const>
</edit>
</match>
<match target="font" >
<edit mode="assign" name="hintstyle">
<const>hintfull</const>
</edit>
</match>
<match target="font" >
<edit mode="assign" name="antialias">
<bool>true</bool>
</edit>
</match>
</fontconfig>
Fonts in Opera seemed to be better. But then I copied all of my windows fonts from C:/windows/fonts to /.fonts/windows
So all of the fonts work good now.

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

Weird fonts with latest Freetype2 and Firefox

This is the weirdness I have
And this is my fonts.conf that I don't want to edit if possible... I like hintslight
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<match target="font" >
<edit mode="assign" name="rgba" >
<const>rgb</const>
</edit>
</match>
<match target="font" >
<edit mode="assign" name="hinting" >
<bool>true</bool>
</edit>
</match>
<match target="font" >
<edit mode="assign" name="hintstyle" >
<const>hintslight</const>
</edit>
</match>
<match target="font" >
<edit mode="assign" name="antialias" >
<bool>true</bool>
</edit>
</match>
</fontconfig>
Last edited by Cimi (2007-05-06 21:14:18)

Thank you for advices!
I did not try to downgrade freetype, but I guess Microsoft fonts look good with older versions of freetype because there is BYTECODE_INTERPRETER enabled. Here is quote from SuSE documentation:
In order to get a good rendering of the MS TrueType Core Fonts, the BYTECODE_INTERPRETER setting should be enabled in freetype2. The freetype people do recommend not to use the bytecode interpreter anymore in favor of their auto-hinting code. But while it is true that you will achieve good rendering with most of the free fonts, this is quite ugly for the MS TrueType Core Fonts.
Well.. I do not want to enable features that are not recommended by developers :-)
What about antialiasing - I do not want to enable it for small font sizes. And, of course, antialiasing is the thing that was invented not for fixing broken fonts rendering.
I decided to replace Tahoma with Verdana everywhere to solve this problem :-) Unfortunately, I coud not do this with fontconfig - debug output from freetype shows this font list after replacement:
"Verdana"(w) "Times New Roman"(s) "Thorndale AMT"(w) "serif"(s) ""(s)
Note letter "w" after Verdana. I do not know what these letters mean, let's suppose 'w' is for 'weak' and 's' is for 'strong'. Firefox (or freetype) ignores 'weak' fonts when there are 'strong' fonts in the list. And all substituted fonts always have 'weak' marking... Thus, Firefox displays Times New Roman (or any font that was set as default in Firefox) instead of Verdana.
The final solution for me was to take fontforge, make a copy of Verdana and rename this copy to Tahoma. Now I have Tahoma replaced with nice rendered Verdana everywhere
But the question is still open - is it possible to take broken Tahoma and make same looking font that would not be broken?

Weird font being used in player

For a while now, in my Flash player embedded in my browser
(any browser I use), a weird font shows up for some of the text.
Here's a
screenshot of what I mean, taken in Firefox (you can see the
font in the band name at top and on the song titles):
This also occurs in some PDF documents.
I've tried a bunch of things, including reinstalling my Flash
player and the like. Nothing has worked. I'm going to assume it's
an Adobe font issue, but I don't want to go into the font file and
muck something up just yet. Plus I have no idea what I'm looking
for.
I'm running Mac 10.4.11 and Flash Player 9.
Any ideas or leads? Thanks.

You wouldn't believe the mess that ensues when I try to start using styles in a document. It doesn't happen right away, but soon, the styles conflict and don't apply or become convoluted in a way that I have to throw away the entire document before it infects my system and I have to simply start over. I hate 'styles' and I'm sure it works for somebody, but not for me. The only way I would try styles at this point would be through a college class where I could have an instructor, week after week, where I could bring back my 'mess' and have the instructor show me where I went wrong. At this point, I do not have that and experience has taught me to just don't touch that!
Thanks Jongware, I'll try those things you recommended. Even though I have used InDesign from the day it was introduced (got rid of Quark in a hurry) there are still areas that are yet to be learned for me. What a great program it is.
Ken

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>

Font rendering differences between Xfce and KDE

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

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

Font rendering quality in Illustrator is terrible!

What the heck rode Adobe when they implemented the new font engine?
Why, oh why is Apple's font rendering so much better? And why wouldn't Adobe use something that's already readily available on the mac platform?
I have a huge problem mocking up website layouts in Illustrator. Type looks much better in Firefox or Safari. How come, huh?

I believe this is the result of sub-pixel antialiasing (SPAA), which optimizes text appearance on laptops. Illustrator's rasterizing doesn't SPAA, which is fine for most CRTs, print, and LCD displays that might be rotated.
It's more a case of the OS being savvy enough to tell what kind of display you have and antialias appropriately. Illustrator's rendering engine does need to support SPAA.

Chromium weird font rendering

Similar Messages

Maybe you are looking for