Getting better font rendering

I'm using a TrueType font in my AIR app to write live text. It's installed on Windows XP. But every font looks terrible in my AIR app. It looks as if it's a Flash movie with quality set to Draft.
How can I improve the appearance and anti-aliasing of fonts in my AIR app?

I installed:
cairo-ubuntu
Then it pulled down everything ellse as dependencies.
I run KDE. You do not need to rebuild anything.
I bet your problem is that in KDE "System Settings" -> "Application Appearance" -> "Fonts" -> "Use anti-aliasing"
You had changed that option in the dropdown from System Settings to enabled, or messed with Froce fonts DPI. Once you changed these settings KDE overwrites the font config files that the cairo-ubuntu package configured correctly. I just made that mistake yesterday. Now even when I change "Use anti-aliasing" back to the defualt System Settings it dose not go back to the way it was.
Now I have to leave it on Enabled and Use sub-pixel rendering RGB; Hinting style Full
If you don't mind reconfigureing KDE.
Backup .kde4/share/apps/kwallet and stuff
Then delete delete ~/.kde4 and all should be well.
Owe, and -Bitstream Vera Sans- is the best font, but still install the cairo-ubuntu package to configure everything.
Last edited by hunterthomson (2012-12-25 01:32:48)

Similar Messages

I am trying to get better playback rendering speed Premiere CS6

I am new to Adobe Premiere CS6. I am trying to get faster playback rendering speed from my machine.
Windows 7
i7 4790K Haswell overclocked to 4.5 (watercooled with Corsair)
16 GB DDR3@799MHz
Asus Z87-WS (4 double graphic card slots)
Geforce GTX 760 (Primary) GPU hardware acceleration enabled
Quadro FX5800
250GB Samsung solid state C: (Windows and Adobe)
250GB Crucial solid state (Scratch)
2TB Seagate 7200RPM (video files)
3TB Seagate 7200RPM (storage)
Seasonic 1000watt PSU
I am primarily editing GoPro videos with effects like TimeWarp or Twixtor and color correction.
I have tried to run the PPBM6 program with no success. I kept getting failure to access files.
I have been looking at adding a second GTX760 with SLI so they will work together. And possible removing the Quadro if it is slowing things down.
Any advice would be appreciated. Thanks!

...are you SURE your 760 GPU is "enabled" by PPro, and giving you the option of "Mercury Playback Acceleration" under "General Preferences" ??? If the "Mercury Acceleration" is GREYED OUT and limits you to "software Only", go to Studio 1 website and learn to apply the well known "hack" to enable your 760 in PPro,OR, download their simple program to do it for you.
...Your machine is POWERFUL....especially with your CPU overclock......you MAY want to increase your memory to 32 GB if you are using After Effects....even PPro MAY run better with 32 GB, depending on your workflow.....most systems like yours have at LEAST 32GB system memory.
.....The GoPro codec is natively HIGHLY COMPRESSED and difficult to process, even for beefy machines. That is why they provide the free Cineform tool,( which used to be an expensive professional editing codec), to convert some,or,all of your footage to a more "edit friendly" AVI codec, which will FLY on your machine. HOWEVER, those new AVI files are HUGE.....TRIPLE the original size and requiring a LARGE and FAST disk transfer system. Right now, your single 7200 drive for your media is your SLOWEST component in the chain. The CHEAPEST improvement for you would be to add another MATCHING 2TB 7,200 rpm drive to your existing one and then use the 2 drives to create a fast RAID 0 directly off the mother board to improve the speed of your "media drive". THEN, you MUST insure that this RAID 0 is DILIGENTLY BACKED UP in case of a drive failure in the RAID. This ALSO means you must protect against an unexpected power failure which could destroy the RAID data if the failure happened during a critical write operation.....so,a good UPS is required.
You can OBSERVE how the various components in your system are performing while performing strenuous tasks by bringing up the "task manager" window and watching the CPU load.... if all cores are PEGGED at near 100%, you are "CPU bound". As you are ALREADY overclocked, you can't do anything other than to TRANSCODE your footage to the free Cineform. Your ENABLED GPU can be observed....real time....using the free MSI Afterburner,( or, similar). Certain operations are accelerated by the GPU with PPro....not ALL!! Scaling and some effects will use use the "Mercury Acceleration" while rendering previews AND during export.In some cases, rendering previews,or, exporting can be sped up by TEN TIMES by Mercury Acceleration. Watch the "GPU Usage" on Afterburner to see if the GPU is indeed being used, and if you are "saturating" it to its capacity of 100% with accelerated effects.
Make sure your Windows is fully updated to the current time........make sure your NVidia 760 has the most recent driver and DON'T use the Quadro for now. Set your "Windows page file" to be STATIC on your "C" drive at 24GB. Disable "Hibernation" Set all drives NOT to allow "indexing". Do NOT allow any spinning HDD to be over 50% filled....performance WILL decrease.....make sure any HDD is defragged,( do NOT defrag an SSD ! ). Stop all unnecessary processes, esp. anti-virus programs, while editing. Find out how to best "tune" windows to speed it up at the PPBM 6 and 7 websites.
BE AWARE that the "run of the mill" SSDs use cheaper Sandforce controllers, and are less suited to handle highly compressed digital video files. Samsung PRO models and recent Crucial M550 series SSDs ONLY are recommended for video use. Both these non-Sandforce SSDs maintain high WRITE speeds,( over 400MB/sec), AND maintain their high speeds after reaching their "steady state" condition. Cheaper EVO series and non-Marvell controlled SSDs MAY lose their fast write speeds over time and SLOW YOU WAY DOWN !!! Test your current SSDs by transferring large video files between them and watching MB per second that appears under "details" in the pop up window during transfer. Make sure none are slow.....test them with HD Tune Pro as well.
Certain non-Adobe plug-ins and certain effects may NOT use all the CPU threads well,or, may not use the GPU.....forcing the CPU to do additional work. You will have to identify problem plug-ins,or, effects by switching them on and off to see if any cripple your system.
Your machine is POWERFUL.....go to PPBM7 website and read the "tweakers" page to learn more....then, register for free and TEST your machine with their video benchmark test for PPro. It should do WELL.....AND it will help identify if you have any "bottlenecks" which are impairing your system.
Good Luck !!!!!.....THEN, start using CC 2014.....like Patton said : "...all glory is FLEETING !!"......so is the lifespan of former PPro versions !!!!!!

Better font display: Ask for tester

Here is my chinese opmitised fonts.conf file, and ANYBODY who is using another language is supposed to benefit from it, you can get better font display if it works, so I ask for more tester, all you neet to do is to replace your original fonts.conf file(under your /ete/fonts/) with this one, don't forget backup firstly.
I don't know how to enclose an attachment, so I post my fonts.conf 's content here, I am using freetype 2.1.8 and fontconfig 2.2.2, I compiled them by abs, and almost the same PKGBUILD as Judd, however I don't apply any patches.
fonts.conf:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">

<fontconfig>


<dir>/usr/share/fonts</dir>
<dir>/usr/X11R6/lib/X11/fonts/Type1</dir>
<dir>/usr/X11R6/lib/X11/fonts/TTF</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>


<alias>
<family>Times</family>
<family>Times New Roman</family>
<family>Nimbus Roman No9 L</family>
<family>Luxi Serif</family>
<family>Kochi Mincho</family>
<family>AR PL SungtiL GB</family>
<family>AR PL Mingti2L Big5</family>
<family>Baekmuk Batang</family>
<family>NSimSun</family>
<family>SimSun</family>
<default><family>serif</family></default>
</alias>

<alias>
<family>Helvetica</family>
<family>Arial</family>
<family>Verdana</family>
<family>Tahoma</family>
<family>Nimbus Sans L</family>
<family>Luxi Sans</family>
<family>Kochi Gothic</family>
<family>AR PL KaitiM GB</family>
<family>AR PL KaitiM Big5</family>
<family>Baekmuk Dotum</family>
<family>FZYuanTi</family>
<default><family>sans-serif</family></default>
</alias>

<alias>
<family>Courier</family>
<family>Courier New</family>
<family>Andale Mono</family>
<family>Luxi Mono</family>
<family>Nimbus Mono L</family>
<family>SimHei</family>
<default><family>monospace</family></default>
</alias>

<match target="pattern">
<test qual="all" name="family" compare="not_eq">
<string>sans-serif</string>
</test>
<test qual="all" name="family" compare="not_eq">
<string>serif</string>
</test>
<test qual="all" name="family" compare="not_eq">
<string>monospace</string>
</test>
<edit name="family" mode="append_last">
<string>sans-serif</string>
</edit>
</match>

<include ignore_missing="yes">~/.fonts.conf</include>

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

<alias>
<family>Times</family>
<accept><family>Times New Roman</family></accept>
</alias>
<alias>
<family>Helvetica</family>
<accept><family>Verdana</family></accept>
</alias>
<alias>
<family>Arial</family>
<accept><family>Verdana</family></accept>
</alias>
<alias>
<family>Courier</family>
<accept><family>Courier New</family></accept>
</alias>

<alias>
<family>serif</family>
<prefer>
<family>Nimbus Roman No9 L</family>
<family>Luxi Serif</family>
<family>Kochi Mincho</family>
<family>Baekmuk Batang</family>
<family>Times New Roman</family>
<family>Times</family>
<family>STZhongsong</family>
</prefer>
<accept>
<family>SimSun</family>
<family>ZYSong18030</family>
<family>AR PL SungtiL GB</family>
<family>AR PL Mingti2L Big5</family>
</accept>
</alias>
<match target="pattern">
<test qual="any" name="family">
<string>sans-serif</string>
</test>
<edit name="family" mode="append" binding="strong">
<string>Verdana</string>
</edit>
</match>
<alias>
<family>sans-serif</family>
<prefer>
<family>Luxi Sans</family>
<family>Nimbus Sans L</family>
<family>Helvetica</family>
<family>Kochi Gothic</family>
<family>Baekmuk Gulim</family>
<family>Verdana</family>
<family>Arial</family>
<family>FZYuanTi</family>
</prefer>
<accept>
<family>SimHei</family>
<family>STKaiti</family>
<family>AR PL KaitiM GB</family>
<family>AR PL KaitiM Big5</family>
</accept>
</alias>
<alias>
<family>monospace</family>
<prefer>
<family>Luxi Mono</family>
<family>Nimbus Mono L</family>
<family>Kochi Gothic</family>
<family>Baekmuk Gulim</family>
<family>Andale Mono</family>
<family>Courier New</family>
<family>SimHei</family>
</prefer>
<accept>
<family>AR PL SungtiL GB</family>
<family>AR PL Mingti2L Big5</family>
</accept>
</alias>

<match target="font">
<test name="lang" compare="contains">
<string>ja</string>
</test>
<edit name="hinting" mode="assign">
<bool>false</bool>
</edit>

<edit name="rh_prefer_bitmaps" mode="assign">
<bool>false</bool>
</edit>
</match>
<match target="font">
<test name="lang" compare="contains">
<string>ko</string>
</test>
<edit name="hinting" mode="assign">
<bool>false</bool>
</edit>
</match>
<match target="font">
<test name="lang" compare="contains">
<string>zh</string>
</test>
<edit name="hinting" mode="assign">
<bool>false</bool>
</edit>
</match>

<match target="font">

<test name="slant">
<const>roman</const>
</test>

<test target="pattern" name="slant" compare="not_eq">
<const>roman</const>
</test>

<edit name="matrix" mode="assign">
<times>
<name>matrix</name>
<matrix><double>1</double><double>.2</double>
<double>0</double><double>1</double>
</matrix>
</times>
</edit>

<edit name="slant" mode="assign">
<const>oblique</const>
</edit>
</match>
<config>

<blank>
<int>0x0020</int> 
<int>0x00a0</int> 
<int>0x00ad</int> 
<int>0x115f</int> 
<int>0x1160</int> 
<int>0x1680</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>0x3000</int> 
<int>0x3164</int> 
<int>0xfeff</int> 
<int>0xffa0</int> 
<int>0xfff9</int> 
<int>0xfffa</int> 
<int>0xfffa</int> 
</blank>

<rescan>
<int>30</int>
</rescan>
</config>
</fontconfig>
and my freetype 2.1.8 PKGBUILD:
# $Id: PKGBUILD,v 1.18 2004/04/30 03:22:41 judd Exp $
# Maintainer: judd <[email protected]>
force=y
pkgname=freetype2
pkgver=2.1.8
pkgrel=1
pkgdesc="TrueType font rendering library"
url="http://freetype.sourceforge.net"
depends=('glibc' 'zlib')
source=(ftp://gd.tuwien.ac.at/publishing/freetype/freetype2/freetype-$pkgver.tar.bz2)
install=freetype2.install
md5sums=('f717615787a1aadbdb164d1bc23c2308')
build() {
cd $startdir/src/freetype-$pkgver
# enable the bytecode interpreter
# patch -Np1 -i ../bytecode.patch
./configure --prefix=/usr
make || return 1
make DESTDIR=$startdir/pkg install
PKGBUILD for fontconfig 2.2.2:
# $Id: PKGBUILD,v 1.5 2004/02/07 20:49:19 judd Exp $
# Maintainer: judd <[email protected]>
pkgname=fontconfig
pkgver=2.2.2
pkgrel=1
pkgdesc="A library for configuring and customizing font access"
url="http://www.freedesktop.org/software/fontconfig"
depends=('expat' 'freetype2' 'zlib')
backup=('etc/fonts/local.conf' 'etc/fonts/fonts.conf')
source=(http://pdx.freedesktop.org/software/fontconfig/releases/fontconfig-$pkgver.tar.gz)
md5sums=('af6e9a8addfa89aa68d703d5eb004185')
build() {
cd $startdir/src/$pkgname-$pkgver
# patch -Np1 -i ../freetype.patch
./configure --prefix=/usr --sysconfdir=/etc
make || return 1
make DESTDIR=$startdir/pkg install
install -D -m644 ../fonts.conf $startdir/pkg/etc/fonts/fonts.conf
mkdir -p $startdir/pkg/usr/X11R6/bin
ln -sf /usr/bin/fc-cache $startdir/pkg/usr/X11R6/bin/fc-cache

I got brave and gave your font.conf a shot. everything worked great but when building the fontconfig pkg I had to change the source line to...
source=(http://freedesktop.org/~fontconfig/release/fontconfig-2.2.2.tar.gz)
other than that the freetype and font pkgbuild files worked and installed fine.
When I replaced my font.conf file with yours, after backing up mine ofcourse, and rebooted I didn't have any problems but the overall apearence was not as good as it was when using my original file. I switched back to my original and no harm done. I don't speak chinese but was curious. I'm just learning abs and building my own packages. I was impressed with your pkgbuild files working and then installing with no errors. The first ones I have ever used that worked. but now when I run pacman -Su it wants to upgrade back to fontconfig-2.2.1-2 and freetype2-2.1.7-1. I should say downgrade. I guess I need to search for an answer to why it doesn't recognize the new pakages as being the latest.

Font rendering glitches

Hi,
I am getting occasional font rendering glitches.
It appears to affect fonts in any applications, occasionally a single character will be completely messed up. see attached image.
It appears to happen when I have an lcdfilter entry in my font config. But without this fonts don't look very good.
lcdfilter = lcddefault or lcdlight give the problem
lcdfilter = lcdnone or lcdlegacy are okay
I tried installing freetype2-infinality and fontconfig-infinality as a long shot, but this didn't help.
Anyone have any idea what might be causing this, and how to fix?
Thanks
P.S. I'm sorry if this post isn't perfectly categorised.
Last edited by daulpavis (2013-10-10 09:22:38)

Thanks. That worked.
I found from the versions I had 2.21.12-1 was also good. 2.21.14-2 was the next version which was bad.
For reference the most up to date version at the time, which I was originally using, is 2.21.15-1.
If I have some time I'll try to dig into this one a little deeper.

How could I change font for IBM 9068 A03 printer so I get better output?

Closing as duplicate post please continue with [/questions/1014845]
I am a linux user. In past I used Chrome for my browser. But a few months ago, my corporate changed our software and optimized it for using in Firefox. Unfortunately, the output printing font I got so bad. My printer is IBM 9068 A03 with IBM Proprinter II driver, and it's no matter about font in Chrome. Can I change font in FIrefox to get better printing output? Thankyou very very much for helping.

see [/questions/1014845]
Sorry linked to itself in my last post !
Posting again to ensure you have the correct link in your emaiI.

Is it possible to get my fonts and graphics more like Ubuntu.

Is it possible to get decent graphics in Arch? I've tried all sorts of things and I never seem to get things the way I want. At work, I use Ubuntu 11.04 with GNOME fallback and I really like the fonts under the stock setup, but I can't seem to get Arch to do the same. In fact, I nearly can't stand reading pdf files (something I do a lot of for work) in Arch, because they are rendered so poorly. It is as if the whites are two white and the blacks too black, and there is a yellow like haze around the fonts. It is nearly painful to look at for extended periods! My hardware at home is comparable (if not better) to my hardware at work, so it doesn't make sense for it to be that way.
If I've got an ATI Radeon HD 4670 card, should I use the proprietary driver or generic driver? Or, does it not even matter?
I've installed and messed with the infinality font patches, but I can't seem to get anything good with them either. (I posted about font problems a while back, but I've upgraded a lot of hardware since then.) I've looked at the ubuntu font packages, but everything I see states that they are outdated.
I like Arch, because it is light and snappy compared to Ubuntu, so I don't want to switch OS'es.

I took a quick look at the Ubuntu packages for evince and poppler, and couldn't see an obvious reason for improvement over stock.
Poppler's font rendering is known to be bad (and difficult to fix).
The quality of individual monitors is one of many variables that can make a huge difference to the perceived quality of fonts.
The radeon vs ATI proprietary driver shouldn't make any difference, unless the open-source driver is royally broken, and I can't recall anyone else calling such brokenness plausible - it would be blatantly obvious to every user of it, surely.

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?

[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

Fireworks & Photoshop CS6 font rendering

Hi everyone,
Just a quick question. Has Adobe now unified the font rendering engine for both Fireworks and Photoshop? I've always found that when working with PSD or Fireworks PNG files between the two apps, that fonts get rendered or kerned differently, which is a little frustrating.
I would hope that after 8 years, Fireworks would have no trouble working with PSD files and fonts. I was a bit disappointed to see that things hadn't changed in CS5.5.
One may ask why I don't just use Photoshop all the time. Well, I would, but for doing quick edits of files, Fireworks fits the bill perfectly for working with web graphics. Photoshop is a little more involved for this sort of thing, and sometimes I have to work with PSD files in Fireworks, to export my slices.
Thanks in advance for the comments :-)
Steve

I love the graphic! Awesome. But that's gotta be the worst pickup line ever.
I'm impressed with how closely you matched the Photoshop versions using FW's Custom Anti-Alias. I've occasionally used text rendered in a web browser—and taken a screenshot of it—when I thought it looked better than Photoshop or Fireworks.
A few thoughts:
Photoshop CS2 applies kerning by default (it's called "Metrics"). To match that in Fireworks, you'd want to turn Auto Kern on. (This would be the flip side to the approach taken in TrapperKeeper's graphic, where all kerning has been turned off.)
Photoshop used to link up with Image Ready, which was Adobe's answer to Macromedia Fireworks. I imagine it was easier to retain text rendering with that setup, and I'm surprised that Adobe didn't build in some sort of method for preserving text rendering in that type of workflow, when they decided to discontinue Image Ready.
When using Fireworks to create slices of a PSD file with text, a good workflow might be to make a copy of the file in Photoshop, flatten the text, and then use that version to slice up in Fireworks.
Following is a pretty amazing article about text rendering on monitors that includes some insights into Photoshop's Anti-Alias settings:
http://www.smashingmagazine.com/2009/11/02/the-ails-of-typographic-anti-aliasing/

Font rendering in opera

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

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

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

Weird font rendering glitch in firefox

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

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

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

I repeatedly get "error during rendering/encoding of menus/slideshow" message. This process is the same on my iMac, MacBook and another iMac. I have been burning dvd's int he same way for the past 12 months using the exact same steps successfully.

I keep getting "error during rendering/encoding of menus/slideshows" message. I have been burning DVD's in exactly the same way for the past 12 months and mostly on my MacBook which is 3 years old. Obviously I'm using iDVD. I purchased an iMac about a year ago and moved to use this for dvd burning without problem. A few months ago (approximately) I started to experience problems with burning with the error message above. I tried everything including starting the whole process from scratch right down to capturing the movie clips from my video recorder into iMovie, then using them in iDVD. Still the same message came up. I lost count of how many times I repeated the process with different clips and variations and the same thing happened. This was also the case with my MacBook and my husband's iMac.
After taking both of mymac's tothe service centre, having new optical thingys put it and even a new hard drive on my iMac along with a new DVD burner the same thing happened. They told me it must be the process that I am using that is incorrect!
I took my 27" iMac to an apple shop and asked them to assist me while I use the same technique as I always had. The same message came up so they tried using my clips in one of their mac's. The same message. They tried it with different clips and the same message. The only way we could get theirs to work was with a magic DVD which did not produce what I needed and was limited with only one page.
I now cannot use any of my Mac's for the intended purpose that I bought them for - to produce good media for my work! It was suggested that I purchase some non Mac software to burn DVDs which defeats the object of having a mac with iDVD in my opinion. I have a book on iDVD which is very informative and have followed the process to the letter and checked all the trouble shooting and still no remedy. It was mentioned that an up-date may have caused the problem on all my macs.
I feel that this issue should be addressed by Apple as a matter of correctness.
I now find that on the net there are many posts in forums and such like with exactly the same (almost word for word) problems. Please Apple, keep/regain your good name and sort this out.
Jayne Connelly

Thanks Bengt W for your attention to this matter. So much appreciated. And thanks for putting me right on the aim of forums (new to this). Although, you may regret asking for more information. I've added everything I can below.
The process I used is as follows:
Import recorded clips of between 5 and 15minutes each from my video recorder into i
Edit the clips (remove unwanted start and endng)
Add title to front of clips
‘Share’ them to ‘movie’ (export using QuickTime)folder in .mov format individually
Open iDVD and ‘create new project’
Select ‘favourite’ theme that I have set up forall my work dvd’s (this has been used successfully many times and I’ve triedwithout using the favourite them).
Add 2 submenus for each group of clips
Select submenu - drag and drop between 3 – 6 clips in each of the twosubmenus
Change title colours on clips
Dragand drop image into drop zones where required
In‘map’ view I check for any yellow warnings before burning to disc
In an attempt to remedy the problems I’ve tried the following:
Try new DVD discs
Try different themes (favourites and standardones)
Change images in drop zones
Start whole process again even from importingfrom camera again
Two other completely different computers (iMacand MacBook) with iDVD
Go to apple shop and use their computers to doin iDVD
Try with one clip and no menu pages added
Use a clip that I already have that did notoriginate from my camera
Turn computer off and restart
New hard drive
New optical lense (thing)
New DVD burner
Saving to disc image rather than dvd disc
Other points:
I also have a ‘flip’ and ‘iPhone’ whereI’ve imported footage camera which, although limited, records and makes videoclips and burns them to DVD through iDVD without problem.
For example, I have just gone through steps 5 - 11 using some clips that were already imported from my iphone to iPhoto and dragged across. I used a theme that I've used before which has failed and added one sub menu page where the clip went. It burned to disc image successfully.
The startup disc, I believe will have no space issues asit’s a new hard drive with no use apart from this. That could have been an issue before (I didn’t check it) butnot now.
Other technical stuff that I don't understand but you may:
I have…… Mac OS X Version 10.6.7 with all updates onit. Processor 2.8 GHz Intel Corei7. Memory 4GB 1067 MHz DDR3.
iDVD version 7.1.1
HardwareOverview:
Model Name: iMac
Model Identifier: iMac11,1
Processor Name: Intel Core i7
Processor Speed: 2.8 GHz
Number Of Processors: 1
Total Number Of Cores: 4
L2 Cache (per core): 256 KB
L3 Cache: 8 MB
Memory: 4GB
Processor Interconnect Speed: 4.8 GT/s
Boot ROM Version: IM111.0034.B02
SMC Version (system):            1.54f36
OPTIARCDVD RW AD-5680H:
Firmware Revision:     3AHB
Interconnect:    ATAPI
Burn Support:   Yes (AppleShipping Drive)
Cache:    2048KB
Reads DVD:    Yes
CD-Write: -R, -RW
DVD-Write:   -R, -R DL,-RW, +R, +R DL, +RW
Write Strategies: CD-TAO,CD-SAO, CD-Raw, DVD-DAO
Media: Toshow the available burn speeds, insert a disc and choose View > Refresh
If you can solve this you are better than the 'apple geeks' in the shop and the service technicians in the service centre (and of course me but that's no achievement).
Eagerly awaiting your reply.
Jayne

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

Can't get TypeKit fonts to work in Adobe Muse!

HI there!
Just wondering if anybody new how to get purchased fonts from TypeKit to work as HTML in Adobe Muse?
I have tried following the link below but when I go to publish my site the text is still all images.
Problem is I know nothing about code but this seemed pretty straight forward to follow but don't seem
to be getting any luck with it.
I was trying to use the font 'Museo Sans Rounded' and I was told to try maybe other fonts which I did and
also they did not work, but If I just take a font from within the Adobe Muse/TypeKit 'Web Fonts' then this works.
Please could someone explain to me if I'm doing something wrong or if there is a better way of acheiving this?
Many thanks
Darren
www.segmentdesign.co.uk
http://museinsider.com/how-to-add-typekit-fonts-to-your-muse-site.html

Hi Liz,
Many thanks for getting back to me.
Below are the screen shots of me:
1. Going into Typekit
2. Selecting chosen ‘Kit’ and checking that the font ‘Museo Sans Rounded’ is WEB SAFE.
3. Launching ‘Kit Editor’ and setting the ’Selectors’ > ‘.body’ & ‘.header’ > ‘PUBLISH’
4. Then I go into Muse and select the ’header' font e.g. I’m a freelance graphic designer &
illustrator based in Bristol.’ then go to ‘Paragraph styles and highlight ‘header’. I then PUBLISH
my site only for it to still be an image.
Am I doing this correctly?
How do I get the ‘Museo Sans Rounded’ web safe font from Typekit into the window e.g. your screen grab?
I will have a go at putting Arial font into title and then see what happens from there!
Many thanks
Darren
SegmentDesign™
Darren James
Freelance Graphic Designer & Illustrator
07983 547 028
[email protected]
segmentdesign.co.uk
 > & illustrator based in Bristol" ?
Instead of choosing a system from the font menu, please try selecting one of the "web safe" fonts that are built into Muse, such as Arial. When you re-publish your site, you should see regular text again instead of the images.
2) using the font from Typekit
Once you have text showing up instead of images, we can work on applying the Typekit fonts.
The kit that you are currently using in your site (ID bnb1odj) doesn't include the font Museo Sans Rounded. Would you please check in your Kit Editor that you are using the right embed code for your Museo Sans Rounded kit?
You can find the embed code by logging into https://typekit.com, launching your Kit Editor, and clicking the "embed code" link at the top right. Copy this code and add it to Muse under the Page > Page properties menu item.
Please give that a try, and let me know how it goes! Once you have republished the site, I can take another look and give you some information on how to set the Typekit fonts in your CSS.
Thank you,
-- liz
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/6237014#6237014
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/6237014#6237014
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/6237014#6237014. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Help with using Adobe Muse CC at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

Getting better font rendering

Similar Messages

Maybe you are looking for