Since a few weeks the fonts in Maverick aren't rendering right anymore. The rendering goes wrong in Maverick itself and other such as Firefox. Tried to change the font in the appearance preferences dialog. Changing the default font in Firefox also hasn't any effect.
View 1 RepliesI've got a slight problem here, and have had it for a while: When I use the "Sharp'N'Clear" .fonts.conf from Here, and set an optimized font like Arial, gtk-based applications render correctly, while Qt-based ones don't As you can see, the top window(Firefox) has it's fonts clean and nice. The bottom one(Dolphin) does not. Both are set to Arial 9. I've tried it with a number of different applications, including some custom PyQt4 stuff, and it's clear that it's -all- Qt-based applications and not just one or two.
For further information, I've had this problem ever since I upgraded from Kubuntu 9.10 a while back - That version worked correctly on both Qt and gtk, but nothing since has.
able to find anything on this particular issue. The problem I'm having is that the contrast ratio of text in firefox seems very inconsistent. For example: if I'm reading an article on NYtimes, from one paragraph to the next it looks like some sentences are in bold-face and others are not. If I refresh the page, it'll be different areas that are or aren't bf. Sometimes they even change (getting darker or lighter) as I'm sitting there reading. I tried to take a screenshot but unfortunately the text all becomes uniform as soon as I hit prt-scr so the image doesn't show the effect.
Another example is viewing my personal favorite forum where threads that I haven't read are in bf as opposed to those I have read which are normal. The problem is that when I do a mouse-over of the bf threads the font rendering becomes more greyed out. It's still bold-face, just not as dark.
A final example is in text-entry boxes. As I'm typing this right now the line I'm on looks normal but the paragraph above seems to go from regular to bold-face from one line to the next. The paragraph above that looks entirely bold-face...
It did occur to me that this could be a monitor issue or even a vid-card issue. But it's definitely not monitor because I can scroll the whole screen and the variation moves with the text... And it's not vid-card because I installed Chrome as a check and it doesn't have the same problem. None of the above symptoms carry over to that application.
I'm running Fedora 13 x86_64 on a Dell Precision Workstation with a Dell Flatscreen Monitor. My fonts render well everywhere, using Dejavu fonts, but in Firefox and Epiphany they have these terrible yellow outlines and jagged edges.Has anyone else seen this? I've only noticed it recently (since the upgrade to Fedora 13), but it also happens on a Fedora 12 machine at home.
View 5 Replies View RelatedIn the next couple of days I'm intending to move to openSuse after a year of vacillating between XP, Vista, 7 and Ubuntu/Mint. One of my main uses for a computer is word processing, but I've noticed font rendering is not at its best in much of Linux. Ubuntu made a great leap as of 9.04, and therefore so did Mint, but whatever was done with the configuration, despite the free and open source factor, hasn't been implemented in many other distros, including I think openSuse. Even Kubuntu is behind - the settings don't seem to alter no matter what is picked in the relevant configuration panel. Several versions of KDE 4 have come and gone without this being seen to.
I am going by live CDs, for example I have 11.2 KDE version which I tried again today and found the same mysterious lack of change as occurs with Kubuntu when the settings are altered. So, has this since been put right with an update or user's tweak, or do people not even know or notice what I'm meaning? Using Open Office's word processor, the fonts aren't correct, often too skinny or spidery, which is what made me hesitant about Linux when I first dipped in, with Ubuntu 8.10.
I've tried the last four openSuse Gnome editions, and with the 'slight' settings for lcd screens the colour fringing is very apparent, as with Ubuntu 8.04 and 8.10. The 'medium' and 'full' settings cause fonts, Roman type especially, to become skinny and spidery.
i have upgraded my desktop from 13.0 to 13.1 and the font rendering suffered big time (did the same procedure on the laptop but no problems there). anyway, the fonts on kdm are really bad as well as konsole and firefox. other qt apps don't seem too bad but should be much better. xterm and xmobar don't seem to be affected at all. the machine is running the 13.1 sbo of nvidia drivers.
i have tried a few things: playing with the anti-aliasing settings in kde control center (all the settings offered differnet level of 'badness' and no 'goodness') and trying to use the settings in the nvidia control panel but that didn't seem to have any effect.
I've installed some custom programming fonts, namely Speedy.pcf. Its a .pcf, so I just coped it into /usr/share/fonts/misc, and ran mkfontscale, mkfontdir. I can use the font fine in 'xfontsel' and 'urxvt', but when GTK2 tries to render this font. its not even the same font, its just using some default font.
View 3 Replies View RelatedIs it just me or does the font rendering in Slackware64 13.37 look bad? It reminds me of the bad old days of having to recompile freetype with the then-patent-encumbered option to make the fonts look decent. When I print, everything looks normal. On screen it doesn't look right. I don't really know how to describe it other than it how things used to change after a freetype recompile. Is there anything major that changed between 13.1 and 13.37 WRT fonts in KDE, X, or freetype for that matter? FWIW, I did a clean install with a new .kde instead of using the old one.
View 14 Replies View RelatedThis happens to me with any browser (tested: Firefox, Chrome and Opera) and DE (tested; Gnome, KDE, LXDE). While for the most part, the text is OK, some text looks quite messed up (please look at the attachment for an example).
By inspecting the affected pages, I fond that usually (maybe ever?) when the characters are garbled, the font is Tahoma.
Then I tested with The Gimp and its text tool: I choosed Tahoma and I tried to type something inside an image. Same issue. It seems to happens when the font size is 14 px or >= 17 px.
I am running ubuntu 10.04 and am using nvidia drivers and my resolution is 1680x1050.
I've been trying to get the windows-like font rendering to work, but I'm having problems with almost every font except Tahoma for some reason. I installed microsoft fonts using this tutorial.
(LINK) This is how bad the fonts look in google chrome
(LINK)This is what my xorg.conf looks like
(LINK)This is my .fonts.conf, I have anti-alising disabled for all fonts there (I think), so the fonts would be sharp
[Code].....
How to return to original state To get font rendering to Subpixel smoothing in F15In a normal user terminal (non root)
cat >> ~/.fonts.conf << FOE
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
[code]...
Tried out the latest Fedora 13 release for kicks, and seem to be liking it so far I'm an openSUSE user and created some RPMs (on openSUSE) for myself which have the Ubuntu font rendering patches in them. I played around with the Fedora RPMs and managed to patch freetype-freeworld, cairo, fontconfig and Xfto achieve subpixel hinting on par with Ubuntu I wanted to share them with the Fedora community, if interested. Is there any place like an openSUSE Build Service for Fedora where I can host them...or maybe some community site that can host them? A screenshot of my desktop:
View 14 Replies View RelatedSee the pic. It happens in both Yakuake and Konsole. I am using inconsolita size 13, but the problem occurs irrespective of size.
I think it's only the bolded text which gets cutoff, but I am not sure. This problem is especially bad when writing something using nano or vim.
Just tried it with DejaVu Sans Mono, and the problem disappears. Weird. I would still like a solution, if you know anything, I am somewhat picky about inconsolita.
Below are example screenshots of Freemind from Ubuntu Lucid and Debian Squeeze
Lucid
Squeeze
You'll notice that there is slightly different quality, it is also applies to pdf documents.
and my question is.. how do i increase rendering quality in debian squeeze?
I just preupgraded from Fedora 14 to 15 on my Toshiba NB205 netbook (the preupgrade went smoothly by the way).
Immediately upon logging in, I discovered catastrophically poor quality of font rendering in every terminal window program I tried, (and I checked plenty like LilyTerm, Sakura, gnome-terminal, etc) and in web-browsers.
The symptoms are the same for all applications: the glyphs are very thin, anorectic, and very ugly.
The described behavior is desktop independent: same in Gnome (3 and the fallback mode), fluxbox, Openbox.
I used the directions from this thread: [url]
Then after installing it, I realized not only did firefoxes fonts look terrible, the fonts on the entire system were totally different, they look terrible.
So I uninstalled all the new programs, removed the new moz repository, and then reinstalled the regular firefox 3.5 from regular ubuntu repos. Dropped all support software down to 3.5 as well. System fonts are still totally fubar!
I tried creating a .fontconfig file with the text from the threads, supposedly to fix the new firefoxes fonts, and it did not help.
As my fonts looked absolutely wonderful, now they look terrible. I tried messing with all the settings in the appearance tab of the gnome menu, nothing seems to help!
Regular firefox is back, and running fine, but its fonts and all the rest of the fonts on the system look horrible, like they are not getting aliased/hinted at all!
How can i change that login window's font rendering, i mean that screen which you can select user and type password. Is anybody have the experience for tweaking gnome login font or background image?
View 3 Replies View RelatedAfter installing wqy-zenhei chinese font, everything used it perfectly except Midori browser. It seems to be stuck on the ancient 'fixed' font set, which is abysmal for Chinese. It also takes ages to load a page with Chinese, pretends to freeze for a minute or two. I've played with Midori's appearance settings, selecting UTF-8, but to no avail.
View 3 Replies View RelatedI'm using Debian Testing (Stretch, right now), and for a little while, a couple of months or so, QtCurve wasn't working properly (and lately, not at all) on GTK2.
After quite a lot of frustrated attempts, I think i fixed it in a way that's probably not recommended at all. I copied the file libqtcurve.so from Wheezy's version of gtk2-engines-qtcurve, and used it instead. It "just worked".
So, experiencing problems with QtCurve on GTK (most noticeably, being unable to set fonts and icon themes for GTK2 apps), or was it just an oddity of my install? My installs are often not all that standard, so I'm never sure. I'm asking because I have to figure out lots of things if I'm to make a bug report, and the bug may not even really exist . I think I'll even check before if the Testing package from another server works, maybe that's the problem.
I just found that this fix/version makes inkscape crash, would probably do the same to some other stuff -- newer versions (even with proper full package install) also have the same effect, except for that latest one, that doesn't seem to work in GTK2.
It's reported as a bug in Ubuntu. The "correct"/better fix seems to be commenting the font-related lines in /usr/share/themes/QtCurve/gtk-2.0/kdeglobals (Not to be confused with KDE's own file of the same name) on the newer package. That doesn't seem to make inkscape crash.
The same file also set the icon theme on GTK2 as Oxygen, commenting the icon line on the same file doesn't fix it, the correct theme apparently has to be spelled out, it seems it has to be for all users using any QtCurve theme, and GUI tools to change the icon theme won't work (but I haven't really tested the "native GTK" ones).
[URL] .....
I downloaded an FLV video and placed an extra MP3 file over it. Two files. Total: 30 MBI experimented with about seven rendering containers, and QuickTime renderer was the only rendering container that didn't result in sped-up/compressed video or correct rendering for just fifteen seconds.How in the name of all that is holy did this rendering end up with 570 extra MB?
View 2 Replies View RelatedI recently downloaded Frets On Fire and the HRP Polymer pack for Duke3D...Duke3D runs fine with just EDuke32 and no mods, just Duke3D and EDuke32. But when I try the HRP Polymer pack, it says in Terminal "NVIDIA: Direct Rendering failed, attempting indirect rendering." This is fine...if I want the game to lag like hell, I'm sure my video card and the driver for it support DR, the video card is a NVIDIA Geforce FX 5200, the same message appears in terminal when I run Frets On Fire, I think it does with other games too, if someone could explain how to enable Direct Rendering.
View 5 Replies View RelatedEssentially I have found this guide, but it is for miktex, i need a guide for texlive on Debian/Ubuntu which will not pollute dpkg installed texmf.
I'm interested in converting TrueType font to be usable in (pdf)(La)TeX.
All the power google turn up just stuff f relating how to install microsoft fonts or do stuf on MikTeX.
I CANNOT USE XeLaTeX!!! I use pstricks and the font must be available in plain TeX! Otherwise my document looks inconsistent!
Most of my work happens in a terminal, so I need a clear, readable font. I've settled a while ago on Terminus [URL]..., which works wonders for me. I added XTerm*faceName : Terminus in my ~/.Xdefaults, and I do get the Terminus font. Unfortunately, a lot of Unicode glyphs are missing (mathematical symbols, greek and hebrew letters), displaying as little square blocks instead.
If I remove the faceName entry, the default configuration seems able to display most of the glyphs (including math, greek, hebrew, runic, and whatever else), but the default font is much harder to read.
A google search hints that it should be possible to use Terminus as the default font, and fallback to (an)other one(s) for missing glyphs, but provides no further explanation. I've seen documentation that recommends Bitstream Vera Sans as a fallback, but it lacks the glyphs I need too; I don't know how to identify the default font used by xterm either, I had a look at /usr/share/X11/app-defaults/XTerm, but all I can find are generic references to old pre-fontconfig font names.
Using Gentoo Linux, fontconfig and xterm are up to date, USEs trutype and unicode enabled, X.Org server 1.6.
Edit: I alternate between Ratpoison, Awesome and XMonad, without a desktop environment.
I can't change fonts in Firefox preferences (Content).
My OS is openSUSE 11.3, KDE 4.4.4. release 8.
Any type and size of font I use, nothing happens. It's still same font which I choose for the first time I've started Firefox afer installing openSUSE 11.3.
Actually I want to log a bug but I don't really know what package to log it against. The problem is that by default Pango is choosing the AR PL UMing CN as the font to render Japanese text when the current font doesn't have Japanese glyphs. But AR PL UMing CN is a Chinese font, so Chinese glyphs for kanji characters (e.g., 覚) are displayed. This is jarring and confusing for Japanese readers.
This situation mostly arises when you have mixed English and Japanese text. Some applications (for instance Firefox) will allow you to select a font for Asian text. Thus if the text contains only Asian characters it will use the font you select, rather than what Pango would have selected. But if it is a mix of English and Japanese, you end up with the wrong glyphs.
Other environments (like gnome-terminal, or a gedit) have difficulties as well. Since the primary interface requires mono spaced roman characters you run into difficulty selecting fonts. Most Japanese fonts only have proportional roman characters. This means that if use a nice roman font and use Japanese text (for instance file names), you end up with Chinese glyphs. What I want is a mechanism that will work across all of Gnome for selecting the font I want to use for Chinese characters. That way I can choose either Japanese or Chinese glyphs.
I realize this is low priority. It only bugs me a little, but many of my Japanese colleagues are put off from using Ubuntu because they are confused by the Chinese glyphs that pop up on my screen from time to time. As I said, I'd like to file a bug, but I'm not sure against what package...
In all previous versions of KDE I had Console8x16 set as KDE font for all cases (Settings->Appearance->Fonts). After tonight upgrade, this (only!) font is not working. I can see it in font manager, I can set it in ...Appearance->Fonts, but actually remains default font. Two of about 30 attempts somehow (can not reproduce) succeeded to set "console 12" font, but it disappeared after restart.
1. What can be the problem in 4.4?
2. In /usr/share/fonts tere are 3 files named console8x16.pcf, console8x8.pcf and console9x15.pcf, but in the font list in Appearance->Fonts I can see only 2 - one named "Console" (seems to be 8x16 and "console" (8x8). File 9x15 does not appear at all. Why?
Last results of attempts: cannot use console font in part of areas, while part works OK. For example: kdevelop editor, kmail message body text works OK. But kmail other parts - does not. The most interesting is that although setting the kmail body message text to console displays the message body text correctly (with console font), but the example message in "Configure kmail" dialogue "The Quick Brown Fox Jumps Over The Lazy Dog" is displayed in the default font, as if there is no console font!
I am seeing a weird error in a font display. I see a small question mark next to a font that I am using as a simple graphic. Does this mean that some function call in xlib is being passed an invalid paramter?
View 1 Replies View RelatedI'm having serious problems in making glx rendering work in ubuntu lucid lynx. This is related to difficulties in installing fglrx. If I type glxinfo this is what I get:
Code:
name of display: :0.0
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
[code]....
I had a working pdftotext script working and custom made a parser for the info in it, but upon moving from CentOS 5.5 to Ubuntu (version unknown) and installing poppler-utils, pdftotext works, but the rendering is different by quite a bit causing a ton of issues. I also tried on another CentOS (5.2 this time) and it rendered the same as Ubuntu. I'm trying to figure out the problem so it renders the same, I'm using the same code and everything.
View 2 Replies View RelatedI have openGL working fine on my system.The only problem is that when I try to run the executable file, nothing appears unless the full scene has been rendered.In fact, it appears in parts, i.e. updates after a second, then after another second etc...However, earlier, the rendering used to be continuous and I could see each pixel getting rendered in a continuous fashion.
View 3 Replies View Related