Totally perplexed, fonts rendering bad on Windows (IE & Firefox)

My site
http://www.bluearsefly.com
is almost complete but I tested it with a Windows machine and font looks terrible. It looks perfect on My Mac with both firefox and safari. But with windows XP / 2000 with both Firefox and IE it looks aweful.
I also had friends around the world try it and it looked aweful to them as well in IE.
Any advice would really be appreciated. I know it has something to do with fonts but what ... im not sure
Cheers

Hi there thanks for the quick reply.
Yes its one of Suzanne's and you aree spot on, Suzanne suggested the same cross platform issue.
I dont really want to convert to PNG as I would have to apply that to the whole site , including dynamic stuff like the diary (aka blog).
Suzanne suggested trying a standard font like Verdana for the benefit of windows people , which at the end of the day still account for the majority.. at least for now.
Ive been researching on this forum (which is excellent by the way) and was wondering if it could be some font duplication / missing font issue? I dont see to have a LucindGrand-bold font nor is it defined in Suz's CSS? I have duplicate arial fonts (difff versions) but thats not being used in the site so im not sure how that would effect things.
Very strange indeed
Incidently if i look at Suzannes templates at her site on a windows machine the font looks nasty as well. but I dont recall it looking nasty a few months back..
Thats why Im confused.. what could have changed?
appreciate any further thoughts

Similar Messages

  • Fonts rendering incorrectly since update to Firefox 13.0.1

    Since I updated to Firefox 13.0.1, any website using the Helvetica Neue font is rendering an outline font instead. I do have this font installed on my computer, and cannot uninstall it as I am a graphic designer and I use it all the time. Any change we can get a fix on this?
    I just pasted one example, but even this page is doing it: https://support.mozilla.org/en-US/questions/new/desktop/d1/form?search=Fonts+rendering+incorrectly+since+update+to+Firefox+13.0.1. I also know Pinterest does it.

    There may be a problem with the Helvetica Neue font if Firefox is using another font instead.
    You can do a font test to see if you can identify corrupted font(s).
    *http://browserspy.dk/fonts-flash.php?detail=1
    You can use this extension to see which fonts are used for selected text.
    *fontinfo: https://addons.mozilla.org/firefox/addon/fontinfo/

  • Font rendering issue in Windows 7 with Aero

    I'm running Windows 7 Home Premium 64-bit, and using Firefox 19.0.2. Aero is enabled, but the ClearType font smoothing is turned off.
    At completely random intervals, text is rendered like this in Firefox:
    http://i49.tinypic.com/vgshv4.png
    Sometimes it can be fixed as simply as hovering the mouse pointer over the affected parts. Sometimes I have to mark the text to get it rendered correctly, and sometimes it can be fixed by scrolling the page.
    It can happen on any sites with any encoding, regardless of the font size and color, but I noticed it's extremely rarely happens with Japanese text. It never affects the whole page, only random parts of the on-screen text, and sometimes the interface text as well. Also worth mentioning that it never happens when Aero is turned off.
    Is this a Firefox bug, or is something wrong with my system? Thanks in advance.

    I had the same issue, uninstalling windows update kb2670838 fixed it for me. See also:
    http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/text-rendering-issues-in-firefox-after-installing/1aaefaec-ba47-4577-82c3-44b72a50049b

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

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

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

  • Small fonts for Firefox 35.0.1 display badly after Windows Update 2/10/15

    After Microsoft did an update (image attached) the display of many small fonts is nasty (image attached). I see it in no other programs including IE. Not all fonts are bad, just some small ones. Everything on your page here looks fine.
    Thanks,
    Chris

    hi chris, this is probably caused by microsoft update kb3013455 which can cause font rendering issues on vista:
    <blockquote>After you install security update 3013455, you may notice some text quality degradation in certain scenarios. The problem only occurs on systems that are running Windows Vista SP2 or Windows Server 2003 SP2. Microsoft is researching this problem and will post more information in this article when the information becomes available. </blockquote>
    <sup>https://support.microsoft.com/kb/3013455</sup>

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

  • Windows OpenType CFF Font Rendering

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

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

  • ClearType support for font rendering on Windows?

    JavaFX 2.1 or higher supports LCD text - that's fine. But there is a big rendering difference to native font rending on Windows - JavaFX 2 text doesn't look as sharpen as Windows native apps looks. It's because we need clear type support like in JavaSwing!
    Is it planned to implement native font rendering with clear type?
    Best regards,
    Tobi

    Check out the announcement at the top of this forum listing:
    https://forums.oracle.com/forums/ann.jspa?annID=1713

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

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

  • Disable CC 2014 live font rendering

    How can I turn off the live font rendering in Photoshop? It is incredibly annoying when I am looking for a font and every font I scroll over changes my font in the Photoshop file.
    I have looked all over for an option to turn this off, but can't find it. Surely, Adobe would allow this feature to be turned off since they also allow font preview to be turned off, right?

    Likewise, I'm still learning new things.  I don't think that ever stops with a tool as rich as this.
    Tooltips are fairly easy to ignore, and there are ways (on a Windows system at least) to change their timing if that sort of thing would suit you.
    One thing I'm sensitive to - and am always trying to learn more about as well - is the human quality (or maybe it is a shortcoming) where we feel resistance to change.
    There's a lot of change in the high tech world that truly ISN'T an improvement, and there's other change that actually isn't bad - once you get used to it.  I'm not saying the new font choice mechanisms are one way or the other, but it's CERTAIN that there is some resistance to change involved with the change.
    I'm sure that, given a product this mature, Adobe has a hard time changing anything without upsetting someone who's totally tuned to the "old way" of working.  And I'm a BIG fan of offering options whenever there's a fundamental change if at all possible, which allow users to deal with the transition on their own terms.  As an example, because an option was provided, personally I didn't switch over from using the windowed interface to the tabbed interface (introduced in Photoshop CS4) until about halfway through the time period where Photoshop CS5 was current.
    -Noel

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

  • How to change the font in query builder window in Reports 6i?

    Hi
    I am facing the old problem again and again, which is I can not find any way to change the font in query builder window in Reports 6i. The current font is so bad for alignment and ordering each part of SELECT statement. Is there any way to change this to COURIER NEW for example?

    No, but I suggest using a different editor which does allow a different text option and just pasting it in.

Maybe you are looking for

  • Clients Agent no longer installing all components properly

    I attempted an upgrade to R2, but it failed, so I reverted back to a VM snapshot before the upgrade attempt and all is well except for installing the client during OSD. The imaging process works fine, but once complete the agent isn't listing all the

  • Display problem import photos

    Hello, I have a display problem when I try to import photos into Lightroom. I use the version 5.2. The problem can be viewed in the following video. At the begining you can view that there is something weird as under the folder "Panoramas" there is a

  • Wireless printing upgrade kit

    COULD ANY ONE TELL ME PLEASE, I HAVE OFFICEJET ALL IN ONE  PRINTER 5610 , WOULD IT BE POSSIBLE TO MAKE MY PRINTER WIRELESS BY BUYING A  HP WIRELESS UPGRADE KIT HOPE SOME ONE MIGHT KNOW THANKS

  • Taking RMAN backup in 3 files

    Hi all, I took backup of Datafiles , archivelog files and controlfile through RMAN. Now, i want 3 backup file will created as a output of RMAN operation. It would be : 1 backupfile for all the datafiles 1 backupfile for all the archivelog files 1 bac

  • Clearify for owb11g: where is the all_rt_map_run_sources

    the 11g documentaion describes a view called all_rt_map_run_sources. this is introduced in owb 10g documenation but non existing in 11g real life!!! so: it is a copy/paste error inside the documentation and how is the 11g synonym named? ## Documentat