Quote:
|
I'm using Slackware64-current, so I think Pat's build of Firefox is dynamically linked against cairo instead of the static linking under 32-bit. Everything looks good to me in firefox-3.5.6 now that I've got cairo-1.8.8 patched.
|
Why is Chrome not showing fonts in a manner similar to Firefox? It defaults to using Arial and Times New Roman, and I've switched it to match what I have in Firefox, but I didn't really see any change.
|
just guessing but like you said above, chrome might be statically linked against cairo. That could be the problem.
|
After doing a little googling, it looks like Chrome uses skia (http://code.google.com/p/skia/) and not cairo.
|
Thursapr, what rmjohnso wrote is correct. You need to rebuild Firefox from source. Use the Slackware64 SlackBuild.
|
Quote:
Anyone rebuild FF after upgrading 4 package not encountered my problem? |
Quote:
|
@ dugan,
I just wanted to write that I had never before visited your web page about these fonts and things, so I went and had a look just now. It's nice! Really well written and covers a lot of angles dealing with fonts and monitors and X. Cool, nice work. I have long ago got my subpixel rendering sorted out, but never yet bothered going into great depth regarding my Slackware fonts (AFAICT they are pretty good anyhow); but it's on my list though of things to do eventually, and I'll be using this thread, and your web page, as a guide/template when I get to it. Thanks, Sasha |
The four patched SlackBuilds have been updated for 13.1.
You can find them in the "Optimizing Slackware Linux's Fonts" page in my sig. |
Thanks dugan, your page has been a real help in making my desktop MUCH getter.
|
Calibri problem
Hi
I have a problem with Calibri font: http://yfrog.com/jycalibrip When font size ranges from 8 to 14, rendering of language specific fonts seems to be broken. 15 and over - font is ok. Webcore-fonts installed from Dugan's slackbuild, fontconfig and others compiled Cleartype-style. Any ideas? |
I just noticed that the current Fontconfig patch no longer enables the "lcddefault" filter, which is the whole point of the Ubuntu patches in the first place.
You need to add the following lines to your local.conf: Code:
|
I rebuilt your packages for 13.1 on a fresh installation a couple of weeks ago, Dugan, and my fonts didn't seem as clear as they did a couple of months ago on -current. Thanks for the tweak - that made a big difference. One thing you might want to mention is that your addition needs to go between the <fontconfig> . . . </fontconfig> tags, not at the end of the file.
Something else I noticed is that I'm missing some entries in /etc/fonts/conf.avail now. Compared to your post #125, I don't have any 10-hinting-*.conf entries, and I don't have 11-lcd-filter-lcddefault.conf. Your conf.d from post #125 was last edited in 08/09 for Slackware 13.0. Is it still consistent with 13.1? My /etc/fonts/conf.avail: Code:
-rw-r--r-- 1 root root 220 2010-06-01 17:54 10-autohint.conf Code:
-rw-r--r-- 1 root root 3861 2010-06-01 17:57 freetype-2.3.12-x86_64-1_dc |
SpelledJ: Those files are no longer there. I've edited post #125 accordingly.
To tweak further, try putting <edit name="antialias" mode="assign"><bool>true</bool></edit> or <edit name="antialias" mode="assign"><bool>false</bool></edit> between the <match> tags. Also, I tried Chrome, and I noticed that the fonts in the rendering area look different than the fonts in its menus, with the menu fonts being fuzzier and the website fonts being sharper. This leads me to believe that the settings in Chrome's rendering area are actually hardcoded, and cannot be changed. I do know that this is the case with another program: the Gargoyle Interactive Fiction Interpreter. |
All times are GMT -5. The time now is 04:13 PM. |