Messed up font rendering in Acrobat 8 after pdf minor edit

I was given a pdf to make a minor spelling edit which involved opening the InDesign original, correcting the placed(as a graphic)pdf page (using advanced editing/text touch up tool).
This always worked fine in Acrobat 7.
I then updated in the Indd file and output to a new pdf document.
Only now the pdf text component had substituted characters which garbled it.
I went back into >advanced/preflight/options/browse internal structure of doc fonts.< and found the font causing problems and made sure it was loaded on the system- but didn't help. My sense is this is a font conflict problem. In the end I rebuilt the file in Illustator, then saved a new pdf which solved the problem. Could I have resolved this directly from Acrobat/
Thanks for any insights.
RE

Editing of pdf files is a crap shoot. Sometimes it works many times it
doesn't. It is not the preferred workflow.
Mike

Similar Messages

Font Rendering issues in export to PDF-SSRS

Hi,
Its a very strange issue,I am facing from last two days.
I have created a report having text with Gill Sans MT font.I am able to see the text in the mentioned font properly on report server as well as on my development machine.
Issue occurs when I export the report to PDF, as when i open the report in acrobat reader to view the font of the rendered text,it shows the font as Gill#20Sans#20MT which causes the text rendering up in Arial(default font).
If I Export from Word document the font is set as GillSansMT i.e name without spaces and text is rendered in correct font.I have installed the required font on both the locations i.e. report server as well as Development environment.
Thanks & Regards,
AS

Hi Anand Sardesai,
Since the Gill Sans MT font is not been installed on the production server at first. Please make sure the font is installed correctly and that font embedding is granted font. If the referenced font is not installed on the report server, the resulting PDF
file might not contain the correct mappings and might not display correctly when viewed.
Reference:
http://technet.microsoft.com/en-us/library/ms159713(SQL.100).aspx
Alternatively, I recommend you reboot the server try to resolve the issue. There is a similar issue for your reference:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/6a6cc993-e5bc-4919-9a27-d0b177402c6f/ssrs-r2-font-not-persisting-when-exporting-to-pdf
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

Odd font rendering in IE 8 after update

I'm wondering if Tuesday night's IE security update KB3021952 might have messed the way IE displays text on websites.
When I log into our web-based E-Mail client, SmarterMail, the font looks smaller than usual, and is harder to read. Even making it large. Some letters seem randomly bold, and the letters are all slightly distorted.
This is on Windows Server 2008 64-bit Standard, SP2 and Internet Explorer 8.
I am not seeing the issue in IE11. I am also not seeing it in IE10, or in IE10 with browser mode set to IE8.
Zoom and font settings have not changed.
I get the same effect on major websites such as Google.

Ah thanks for linking that Robear, noticed this bit:
After you install security update 3013455, you may notice some text quality degradation in certain scenarios. The problem occurs on computers that are running the following operating systems:
Windows Server 2008 SP2
Windows Server 2003 SP2
Windows Vista SP2
Microsoft is researching this problem and will post more information in this article when the information becomes available.
I may simply uninstall this update until Microsoft resolves the issue.
Assuming you edited your first post above and replaced Windows Server 2008 64-bit...SP1 with
Windows Server 2008 64-bit...SP2, yes, see if uninstalling KB3013455 resolves the behavior.
PS: When you say "I have tried updating from IE8 to 9, but it hasn't worked," do you mean that IE9 failed to install or installing IE9 didn't correct the fonts issue?
~Robear Dyer (PA Bear) MS MVP-Windows Client since 2002 Disclaimer: MS MVPs neither represent nor work for Microsoft

Acrobat Pro DC PDF Portfolio Edit

Have upgraded to Pro DC from 10X - some great new features and some remind me of Windows 8 type going backwards functionality. Having trouble editing the sequence of documents in a Portfolio. Seems there is a rather elaborate ordering systems were you select size, name etc and then you select the method you want.In 10X you would just click "edit" and you could select and drag the files into any order you wanted. I cannot find this in Pro DC - it seems to want to just offer you a preset ordering system all of which do not seem to allow you to take say 10 files and put them in any random order you want. Anyone know how to manage this?

Have been testing this and it is proving to be a very convoluted design. I really appreciate your help so I am merely advising what it happening - though I suspect you well know. To create a sequence using numbers you need to go 1 1.1 1.2, 2 2.1, 3.1 etc 1 - 20 no good. In addition to that you have to remember to select sort by the field you have created as well as sort order and then make sure only it is selected. Adobe seem to have taken something a five year old could understand in 10x and turned it into a series of totally unnecessary and complicated steps and procedures.

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

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

[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

Firefox/Thunderbird Font Rendering changed after upgrade of xulrunner

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

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

Font rendering is poor after a hard reset

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

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

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

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

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

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

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

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

Why does the font rendering change after I publish to the web?

I created an animation in Edge Animate with four slides, using Open-Sans as the font. The font rendering looks good in Edge Animate and looks good in the local html version as well, but when I publish it to the website, the font formatting is not acceptable.
Here is the local HTML version:
Here is how it appears on the website:
Is there a way to control this better?
Thanks.

Hopefully someone else will be brave enough to respond to this, but in the meantime, the best solution I have found so far is to post the animation files to a separate directory on the server. Then pull that page in using an iframe. This way the animation is not influenced by the parent page's styling.

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

Touch-up tool causes font issue in Acrobat 9 and X

While I edit text using the Edit Document Text tool (formerly TouchUp Text) the font style are getting changed, for example If i select the Uppercase style text using Document Text Tool after exit the selection and trying to save as the doucment some characters with in the text changed into lower case. In Acrobat 7 and 8 the TouchUp Text tool works fine. Please suggest a solution to get rid of this issue in 9 pro and X pro.

Hi LoriAUC,
I have attached the screenshots for your reference, How I selected the text and what the problem was occur in the pdf files. Actually this is pdf file which is exported from InDesign as per customer provided export settings. if I change 100% of subset fonts in that export settings(See the screenshots below) I can get rid of the font issues in Acrobat 9 and X pro but I am not supposed do any changes in that settings.
If you want check/analyze the problematic pdf file I can send it as an attachement to your mail ID? if so please let me know your mail ID.
Please let me know if you need any other details or questions to be clarified regrading this.
Thanks for your support.

Font Issue in Acrobat 9 pro and X pro

Fonts are not displaying properly after selecting the text with Touc-up tool in Acrobat 9 pro and X pro how to solve this issue?

When Acrobat X installs it will remove an Acrobat 9 install.
Suggest you Deactivate then uninstall Acrobat 9 before installing Acrobat X.
May want to root about to locate that Acrobat 9 CD first.
As the preponderance of resources in Adobe's "Education" space deal with use of Acrobat X you may be better off in the long run by working out of and learning "X".
http://www.adobe.com/education.html
Be well...

Messed up font rendering in Acrobat 8 after pdf minor edit

Similar Messages

Maybe you are looking for