From: "Sebastian Werner" <sebastian@werner-productions.de>
To: <gentoo-dev@cvs.gentoo.org>
Subject: AW: [gentoo-dev] Antialiasing in GTK - Galeon problems
Date: Sun Sep 9 04:11:01 2001 [thread overview]
Message-ID: <FEEFLNONAAEGJBJFBGKJIEOJCAAA.sebastian@werner-productions.de> (raw)
In-Reply-To: <E15g0kF-00002T-00.2001-09-09-10-19-16@mail11.svr.pol.co.uk>
Hello,
yes, while galeon use the gecko-engine from mozilla to render pages
it don't work at this point. Mozilla hacks some parts in gdk so it don't
use this extension. I don't think that it use aa-fonts if you recompile
mozilla. It works eventually if the mozilla-developers use this extension
to.
The same problem in in nautilus, which use mozilla to display websites, too.
Sebastian
-----Ursprüngliche Nachricht-----
Von: gentoo-dev-admin@cvs.gentoo.org
[mailto:gentoo-dev-admin@cvs.gentoo.org]Im Auftrag von Viktor Lakics
Gesendet: Sonntag, 9. September 2001 11:20
An: gentoo-dev@gentoo.org
Betreff: [gentoo-dev] Antialiasing in GTK - Galeon problems
Hi Gentooers,
I have setup AA-ed fonts in GTK apps. Gdkxft 1.1 was just released, I
followed the instructions, everything compiled smoothly. It works fine, all
the menus and dialogs are AA-ed. Except Galeon rendered WEB pages. ( I mean
fonts are AA in galeon menus but not where it would be really important, in
the pages themselves. I tryed to set several fonts without success.
Any idea?
TIA : Viktor
_______________________________________________
gentoo-dev mailing list
gentoo-dev@cvs.gentoo.org
http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
prev parent reply other threads:[~2001-09-09 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-09 3:20 [gentoo-dev] Antialiasing in GTK - Galeon problems Viktor Lakics
2001-09-09 4:11 ` Sebastian Werner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FEEFLNONAAEGJBJFBGKJIEOJCAAA.sebastian@werner-productions.de \
--to=sebastian@werner-productions.de \
--cc=gentoo-dev@cvs.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox