KDE : slow font rendering

Hi everyone !
I'm completely new to Arch (coming from Ubuntu) and was really amazed at how fast my system could get and how easy it was to set it up.
I only have one problem left (apart from the missing japanese fonts) :
When anti-aliasing is turned on (in KDE), fonts rendering gets really slow. It can be noticed when selecting a big chunk of text with the mouse, in Konqueror or Kate : you can feel it takes some time. Or when switching tabs in Konqueror. Those are definitely much faster in Opera and Firefox.
However, with anti-aliasing turned off, it is almost instant, as it should. But it looks really awful (in general, I have much trouble getting a good font rendering in linux. Probably because of my 19" LCD that only reached 1280x1024)
Do you have any idea ? My config is : nvidia geforce 6600, proprietary drivers, athlon 64 3200+. I tried some MS fonts and the DejaVu font.
Just in case, you may see my xorg.conf, below.
THANKS EVER SO MUCH for reading this far I think my problem may concern many other newbies like me
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder3) Thu Nov 9 17:56:12 PST 2006
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
RgbPath "/usr/lib/X11/rgb"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
EndSection
Section "ServerFlags"
Option "Xinerama" "0"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "fr"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "LG L1915S"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
# HorizSync source: xconfig, VertRefresh source: xconfig
Identifier "Monitor1"
VendorName "Unknown"
ModelName "TV-0"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6600"
BusID "PCI:2:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6600"
BusID "PCI:2:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "metamodes" "CRT: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Videocard1"
Monitor "Monitor1"
DefaultDepth 24
Option "metamodes" "TV: 800x600 +0+0"
SubSection "Display"
Depth 24
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Oh gees, it seems the culprit was the "sub-hinting" (halo de sous-pixellisation) option. I thought I had tried all possible combinations
However, I wonder if it is supposed to slow down the display that much...
Anyway... I would still be eager to find a solution to display japanese fonts
Thanks for listening to me
Last edited by mahen (2007-02-05 11:55:09)

Similar Messages

  • KDE. Font rendering without antialiasing

    I don't like antialiasing and always turn it off. Everything is ok, except modern fonts on the web. They look realy ugly. Is there any way to improve their rendering without antialiasing?
    Thanks in advance!

    Hi ryvasy - I'm no expert, but from what I understand is that some fonts are designed to look good with antialiasing,  and some are designed to look good withoutwiki antialisasing. So what you should do is apply the antialising that the font wants! This means antialias ON for some fonts, and OFF for others. let your eyes decide.  I'm just diving into this (like I said, no expert!), I think it's in a fonts config file (see the  wiki).
    The other thing is the size.  This post is from someone who puts aliassing on large letters only, but who keeps the smaller sizes antialiased.

  • Kde vs i3wm font rendering

    Hi all,
    I am migrating from KDE to i3wm. I see a huge difference in the rendering of the fonts between kde font rendering and i3wm font rendering.
    I would like to know how I can get i3wm to render fonts correctly.

    litemotiv wrote:
    KDE overrides font rendering rules through it's preferences panel (System Settings > Appearance > Fonts), this should be a matter of finding out what tweaks you have made there and apply them to fontconfig manually.
    Everything you need to know about font configuration should be available in the wiki. If you have questions about specific details it is fine to ask them here, but something like "how I can get i3wm to render fonts correctly" will only solicit generic responses obviously.
    Start here: https://wiki.archlinux.org/index.php/Font_Configuration
    Tip: many people prefer Infinality for their advanced font tweaking needs.
    I noticed that KDE changes ~/.fonts.conf contents based on the changes made in 'system settings'. Since this file (even though deprecated) is used by fontconfig, it should cause the same rendering in other WMs as well.

  • Slow text rendering in KDE.

    Hi there,
    I recently starting getting quite fed up with how I felt that writing stuff in kate (or kile, or kdevelop etc) was very slow and unresponsive. The effect I was getting is that there was a big delay (of up to a second or two sometimes) between hitting the key and the character appearing on the screen. It's especially noticeable if you type a whole bunch of stuff very quickly - wait for the screen to catch up!
    I did a few experiments, and managed to rule out any kate plugins etc, though I wasn't experiencing the same thing in konsole / yakuake. Also, I noticed that if I made the kate window smaller, so not so much of the text I was editing was visible, it would speed up. In fact, the size of the lag seems proportional to the amount of text visible and being rendered while typing (even if that text is not being changed).
    I fiddled with a few settings and noticed that I could fix the lag (i.e. completely get rid of it) by disabling "sub-pixel rendering" in KDE's font settings (and restarting the relevant program). Incidentally, it's not enough to have the the "sub-pixel rendering" box enabled and select "none" - that still creates the lag.
    Therefore, I can work around this for now by unchecking the box, but it got me interested in this. I'm thinking that it's something to do with the way Qt is rendering the fonts, possibly to do with my intel graphics driver, but possibly not.
    So this post is twofold really; firstly to let others know of the workaround in case they're also experiencing this, but also to ask around to see if other people are noticing this, with a view to filing a bug / feeding back to developers / deciding that I need newer hardware.
    My specs:
    - KDE from kdemod 4.2.2
    - intel 945GM graphics card onboard
    - xorg intel driver  (currently version 2.3.2, but I've experienced the same with earlier and later versions, up to the current git version)
    - XServer 1.6, though again, I've experienced this with 1.5 too.
    - Using EXA for rendering, though again I've had the same experience with XAA. Haven't tried UXA yet.
    So... anyone any contribution?
    Cheers,
    Pete.

    I experience sever slowdown in scrolling in Kate with my Intel 965.  However, I do not experience any problems in other applications (Kontact, Konsole, etc.).  I did not experience the problem (at least noticably) when I was using Xorg 1.4 and XAA.  Hopefully, 4.5.1 resolves this issue for me as well...  It's harder to deal with large code files now.

  • Font rendering differences between Xfce and KDE

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

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

  • Font rendering in KDE 4

    I recently installed Arch (switching from Ubuntu 8.10) and decided to give KDE a try.  So far I'm mostly happy, but the font rendering isn't working so well.  There are two problems: the first is that fonts all look too thin.  The second is that most of them are way too big!  (For some reason they render properly in some places, like some sites online [e.g. Gmail], but they're way off in most applications.)
    I've tried the suggestions under "LCD" packages from the Arch fonts wiki, along with this guy's suggestions for setting up fontconfig.  I've also tried (variously) changing my DPI settings for KDM and System Settings -> Appearance -> Fonts (with aliasing anti-aliasing enabled or with system settings, and forcing the DPI to 120 or disabled).
    Oh, and I have a 15.4" widescreen 1680x1050 LCD monitor, which I think is (supposed to be) 129 DPI.
    What can I do to get fonts to look the way they should?

    hunterthomson wrote:
    OK, you problem is not with KDE. This weirded me out when I moved to Archlinux from Ubuntu too. In Archlinux you have to install all the fonts you want to use. The default fonts suck. So, You just need to install better fonts. You want the TrueType Fonts "ttf". You can install them with    pacman
    Try this to list all the font packages available.
    sudo pacman -Ss font
    These are some ones that are good
    ttf-dejavu
    ttf-freefont
    ttf-liberation
    you instal them you just do...
    sudo pacman -S ttf-liberation ttf-freefont ttf-dejavu
    Then you will want to open up the Konfiguration thing that you change the KDE configurations settings in and then change the fonts in there.
    Thanks for the tip!  I installed those (and a few others), and I definitely like (for instance) FreeSans better than the default Sans that most everything was using.  Most things look better; I think I'm going to have to tweak the hinting a bit still, but this is definitely an improvement.  Many of the things I thought were rendering related were actually just bad fonts, like you said.
    There are just a couple of problems remaining that I'm hoping will be just as easy to conquer...  First, some websites are still rendering horribly.  Take a look at this screenshot of this site, followed by this one:
    At first I figured it was a problem with Firefox (I know GTK doesn't always play nicely with KDE), but it looks the same in Konqueror.  A quick peek at the HTML for the first seems to say that it's asking for Verdana, Arial, or Helvetica...and I have Verdana and Arial installed.  (The second one calls for a ridiculous font, Palatino Linotype, which I don't have.)  Either way, though, the pages look totally wrong (the font is much too large) compared to any other machine I've seen it on (even my previous Ubuntu setup).   Does anyone know what's going on?
    One other example of font size weirdness: the digital clock plasmoid.  Here's what it looks like:
    The odd thing is that it looked like this for a while when I first installed Arch and KDE, and then played nicely for a few days...and now it's back to looking ugly.
    And finally, here are my font settings in System Settings:
    (And yes, I've rebooted since installing the new fonts and changing font settings, just in case.)
    Any more ideas?

  • Font rendering issue & multimedia keys not working

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

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

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

  • Font rendering and legacy X applications

    For some time, I have had problems keeping older applications working well as the X font system evolves. For example, I have many drawings created in Xfig, and the fonts stopped being rendered correctly some time ago. Converting all these files for a new drawing package like Inkscape would be a pain. The other main problem occurs with a commercial CAD package (Eagle), which is statically linked to Qt2, and does not play nicely when anti-aliasing is applied to Qt3/KDE apps.
    Xfig and others
    The problem here is that Xfig would render fonts with the letters too closely spaced, such that the on-screen representation no longer matches the printed or PDF output. I fixed this by forcing 75 x 75 DPI resolution, rather than using the resolution determined by the X server from probing the monitor. To do this, put a line in the Monitor section of XF86Config or xorg.conf:
        DisplaySize 433 347
    The above x and y values were calculated for a resolution of 1280 x 1024.
    Another fix I have done for Xfig is to patch the sources to pick up the URW font names instead of the Adobe names for the standard Postscript fonts. If anyone is interested, I could make a proper Arch package for this.
    Forcing the resolution is admittedly a kludge. I might look into font rendering in an Xlib application, to see if there is some extra code needed to handle the proper resolution correctly.
    Gtk-2.0 UI fonts at 75DPI
    An unfortunate side effect of forcing 75 x 75 DPI resolution is that the menu and other UI fonts in Gtk apps end up too small. This was noticed on Gvim and Gnumeric. KDE and Qt programmes appear to be unaffected. This can be fixed by creating a .gtkrc-2.0 file in your home directory with the following contents:
        gtk-font-name = "Bitstream Vera Sans 12"
    Put whatever font and size you like. I have no information on the format of the gtkrc file. The above was adapted from a page found on Google.
    Mozilla (which uses Gtk) needs some individual tweaking, as the UI fonts end up far too big. In preferences->fonts, set the resoultion to 72 DPI.
    The above measures should only be required if you have forced 75DPI. I had no problems with Gtk apps prior to doing that.
    Eagle
    The problem with Eagle appears to be related to the fact that it uses Qt2 (statically linked) in a Qt3 environment. This might also occur with other apps, but Eagle is the only one I know about. When antialising is turned on via KDE control center, this modifies .qt/qtrc, and so affects all Qt applications. If I have anti-aliasing turned on, the fonts in Eagle are very ragged and badly spaced.
    I fixed this by modifying the font path in XF86Config, to remove the entry /usr/X11R6/lib/X11/fonts/TTF. The problem appears to be that Eagle is picking up one of the True Type fonts, instead of a Type 1 or bitmapped font. Turning on antialing in Qt appears to alter its font selection behaviour (fontconfig?) as well as font rendering.
    An interesting outcome of experimenting with the font path is that removing entries only affects older applications. KDE and other modern apps work perfectly well with only the mandatory /usr/X11R6/lib/X11/fonts/misc entry present. As far as I know, this is because modern toolkits like Qt3 and Gtk2 use fontconfig to find fonts.

    I now made two screenshots of Mail: The first one while the external display was disconnected, the second one when it was connected (and Mail moved to the external display). I opened both screenshots in Photoshop and there was a clear difference between the font renderings: On the screenshot of the internal display, the fonts are smoothed with black and grey pixels only, while on the screenshot from the external display they are smoothed with colored pixels. This is the reason why the text looks so bad on the external one. Therefore, it is definitely a problem of the font rendering. In Photoshop, the difference of font rendering is clearly visible!
    See here:
    http://img208.imageshack.us/img208/5389/fontt.jpg
    The first line is internal display, the second line external display. That's unbelievable.
    Another thing: I found out that it's not only Mail that has the problem - it is any application that was started after the external display had been connected. It seems that OS X applies the font rendering setting at the moment a application is starts. When I disconnect the display, start Finder, Mail, Safari and so on, and then connect the display, then all the applications look great even on the external display. When I quit the apps and then restart, the font rendering is broken again

  • Qt5 font rendering

    Is there a way to configure font rendering for Qt5 applications? After last update my Qt4 assistant and designer were removed, and I'm forced to use Qt5 versions, which have a very ugly look.

    MadCat_X wrote:That is rather odd. My QtCreator window now looks like this. The menus and the vertical panel look fine as far as font rendering goes, but the central screen is rather ugly - and no, those are not compression artifacts:). Qt4 version of QtCreator was perfectly OK. Is Qt5 supposed to load "Application Appearance" settings from KDE correctly? If it is, then it certainly isn't happening on my machine. Is there anything I can do to track the problem down? Thank you.
    Your QtCreator is fine. You cannot use a Qt4 theme (Oxygen) on a Qt5 application.

  • Adobe Photoshop CS6 Very Slow On Rendering Type

    I have a notebook with specification as mentioned below :
    Lenovo Ideapad Y470P
    2nd generation Intel Core i7-2670QM Processor( 2.2GHz 1333MHz 6MB)
    Windows 7 Ultimate x64
    AMD Radeon HD 7690 2GB
    8.0GB PC3-10600 DDR3 SDRAM 1333 MHz
    750GB 5400
    I'm using Adobe Photoshop CS6 (64 Bit) for doing my job.
    Right now, i have a task to create a banner with dimension 800 x 900 Centimeters with Resolution 300 DPI and Color Mode RGB 16 Bit.
    The file size when blank is about 56.1 GB.
    The problem is, when i add some text with Horizontal Type Tool and click on the Move Tool, the Rendering Type screen show up and take a very very long time to finished.
    I have made some configurations to my Photoshop that i found on Adobe Forum, but the problem still persisted.
    Some configurations that i've made is :
    - Turn off the Automatically Save Recovery Information
    - Set Maximize PSD and PSB File Compatibility to Ask
    - Set the Memory Usage to 95%
    - Set the Cache Levels to 8 and Cache Tile Size to 1024K
    - Set the Graphics Advanced Settings to Drawing Mode Advanced, and Check the option Use Graphics Processor To Accelerate Computation, and Uncheck the option Anti-Alias and 30 Bit Display
    - Set the Scratch Disk to another partition ( C:System D:PageFile E:Data F:Scratch Disk)
    And after all of that configuration, my Photoshop still slow when Rendering Type.
    Could you give me some tips to solve my problem?
    Thanks

    300 ppi for a banner that size is categorically not normal.  Guaranteed. 
    Get specific instructions from the shop that is going to print it.
    You keep confusing ppi with dpi.  The resolution of an image file really is expressed in ppi, pixels per inch, not "dpi" which is dots per inch.  The precise terminology is as follows:
    DPI = Dots per inch = units used to measure the resolution of a printer
    LPI = Lines per inch = The offset printing 'lines' or dots per inch in a halftone or line screen.
    PPI = Pixels per inch = the number of pixels per inch in screen/scanner file terms.
    Here's a link to a discussion that may interest you:
    http://graphicdesign.stackexchange.com/questions/487/what-ppi-should-a-large-format-artwor k-for-print-be-done-at
    It includes the following chart and subsequent comments :
    "The rule of thumb is that we need 1.5 to 2 times the LPI in PPI to get acceptable results.
    "Viewing Distance   Present Study    
    20 feet    greater than 10 LPI  
    18 feet    18.75 LPI or greater 
    16 feet    18.75 LPI or greater 
    14 feet    37.5 LPI or greater  
    12 feet    37.5 LPI or greater  
    10 feet    50 LPI or greater    
    8 feet     65 LPI or greater    
    6 feet     85 LPI or greater    
    4 feet     100 LPI or greater   
    2 feet     133 LPI or greater   
    1 foot     150 LPI or greater   
    6 inches   150 LPI or greater
    "Presumably, for a banner 3m x 5m, you'd be standing at a minimum of, say, 10 feet. (Just eyeballing the wall here.) So, by this table, you'll need 50 LPI minimum. That would mean your raster graphics should be about 100 PPI, or 75 PPI at 12-14 feet. Considering that and the fact that 2x LPI is pretty conservative for reproducing fidelity (often 1.5xLPI is "enough"), this agrees with [the given] advice of 75 PPI being acceptable."
    Talk to your printer.  I suspect they will want a file at under 75 ppi, or even much less.  Follow the printer's advice/request.

  • Font Rendering Got Bad After 32.0 Update

    After the recent update, the font started to get badly rendered. Kind of blurry with jagged edges and transparent parts. It used to be okay D:
    Sometimes it becomes okay for a moment as I scroll down on pages, and sometimes when I stop scrolling, the font stays as it is; as if there are specific positions for the text to render properly. However, not all of the fonts are affected. Only the ones inside the scroll area.
    On times that the font renders properly, the bookmarks font, title bar, and tab names are unaffected and still appear not-smooth. Same thing does not happen on other browsers. All my other system fonts look okay; it's really just Firefox.
    Restarting Firefox = didn't work
    Restarting Computer = didn't work
    Tried setting up Clear Type = didn't work
    Tried enabling and disabling Hardware Acceleration on Firefox = didn't work
    Tried enabling and disabling the Graphics card itself = didn't work
    Tried just about all of the suggestions I found on Google = none worked
    Tried complete uninstall and re-install of Firefox 32.0 = didn't work
    Graphics Driver are updated ~
    Windows is updated ~
    I'm using Windows 7 Ultimate 32 bit
    Graphics AMD Radeon HD 6800
    I fixed it by downgrading to Firefox 31 which makes me sure that 32.0 is the culprit. As I was about to send the message on top; I tried downgrading as my last resort and it worked. Now I'm only sending this as a report. I am hoping you'll figure out what caused it because I am quite strict (OC) that everything in my PC must remain updated >_<; thus I want to use Firefox 32.0 as much as possible.

    No one to help on this ??????

  • Flex 4.5/FP10.2 web app: Font rendering problem

    Heya,
    Upped a web app from Flex 4.0/4.1 to Flex 4.5 & fonts started to render really badly (blurry & 'stronger').
    They are embedded as CFF, no errors or warnings gives. Also upgraded to Flash Player 10.2, which apparently has 'enhanched' font rendering.
    Haven't set applicationDPI on the s:Application tag, so DPI management should be disabled according to the docs.
    (See http://help.adobe.com/en_US/flex/mobileapps/WS19f279b149e7481c682e5a9412cf5976c17-8000.htm l)
    It's straight up @font-face embeds in a CSS file, nothing odd or wrong there.
    Is the case that this is how it's supposed to look now? In that case, how do I revert back to sane rendering?
    Do I need to configure 4.5 somehow to get it to do fonts right?

    Also tested Franklin Gothic, same deal. Tested on Mac (10.2) & PC (10.2 & 10.3). Flex 4.5 for both platforms.
    fonts.css:
    @font-face
    src: url("fonts/arial.ttf");
    font-family: Arial;
    font-weight: normal;
    embedAsCFF: true;
    FontTest.mxml:
    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
       xmlns:s="library://ns.adobe.com/flex/spark"
       xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">
    <fx:Style source="fonts.css"/>
    <s:Label x="20" y="20"
    fontFamily="Arial"
    fontLookup="embeddedCFF"
    fontSize="12"
    cffHinting="horizontalStem"
    text="TESTAR Testar testar" />
    </s:Application>

  • Font rendering quality in Illustrator is terrible!

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

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

  • Font rendering OS X issues

    Hi people,
    I baught a MacBook Air and I am new to OS X. I have this machine since 1 month and I simply cannot get used to the font rendering of OS X. I thought I get used to it after a while, but I don't. I feel like I have body lotion in my eyes all the time, fonts are really blurry and I can only work on that machine for some time. On my windows machine I worked all day long, with no such problems, but not in OS X. It is set to native resolution and I already set the font smoothing to 1, but this is still not enough, while turning font smoothing completely off makes everything look very ugly.
    I wonder why no one ever mentioned that in reviews, etc.? Does it not bother mac users? However, is there some other option (besides scaling down to lower resolution)? I have headache almost every evening, so this is really a problem to me.
    Thanks in advance.

    Do any other applications behave like that? Or just these two?

Maybe you are looking for