Hi, I’m using openSuse11x64, nvidia card and lcd at 1680x1050.
I’ve tried using half a dozen fonts, including the m/soft ones, but they all look quite poor, pixellated and grainy, compared with eg Ubuntu. At -control-Appearance and Themes-fonts- I can switch anti-aliasing and hinting on/off but it doesn’t make any visible difference which setting is used. And this community page,
suggests that subpixel rendering is indeed disabled. But when I follow that page I just get error messages in the console, don’t know why - maybe the files haven’t been updated for os11? So if hinting is disabled in openSuse 11, is there a way to enable it?
Thanks for your time.
> Hi, I’m using openSuse11x64, nvidia card and lcd at 1680x1050.
> I’ve tried using half a dozen fonts, including the m/soft ones, but
> they all look quite poor, pixellated and grainy, compared with eg
> Ubuntu. At -control-Appearance and Themes-fonts- I can switch
> anti-aliasing and hinting on/off but it doesn’t make any visible
> difference which setting is used. And this community page,
> ‘SubpixelHinting - openSUSE-Community’
> suggests that subpixel rendering is indeed disabled. But when I follow
> that page I just get error messages in the console, don’t know why -
> maybe the files haven’t been updated for os11? So if hinting is
> disabled in openSuse 11, is there a way to enable it?
> Thanks for your time.
there’s a problem in the script as it’s looking for things
in /usr/share/automake and it doesn’t exist anymore what does exist
is /usr/share/automake-1.10 so you need to create a soft link:
ln -s /usr/share/automake-1.10 /usr/share/automake
and then again follow the instructions
ps - next time include the error messages you get
Great, that installs automake, but I’m still getting the above error.
When I looked in download/freetype folder it was empty, so I d/loaded the .rpm manually from the link in the error message and put it in the downlad/freetype folder and ran the command again. This gives a different error message,
david@linux-w6z3:~> mkdir -p ~/download/freetype2
david@linux-w6z3:~> cd ~/download/freetype2 wget http://ftp.skynet.be/pub/suser-guru/rpm/experimental/packages/freetype2/src/freetype2-2.3.5-0.1.guru.suse102.src.rpm TARGET_OPT=case \uname -m` in i86) echo --target=i586;; esac`
david@linux-w6z3:~/download/freetype2> rpmbuild --rebuild $TARGET_OPT --with subpixel freetype2-.guru.suse*.src.rpm
warning: InstallSourcePackage: Header V3 DSA signature: NOKEY, key ID 58857177
error: unpacking of archive failed on file /usr/src/packages/SOURCES/bugzilla-159166-reduce-embolden-distance.patch: cpio: rename failed - Operation not permitted
error: freetype2-2.3.5-0.1.guru.suse102.src.rpm cannot be installed
Oh, what a relief it is to have text that doesn’t make my eyes bleed anymore. Literally, they were bleeding! (My optometrist says it’s probably my contact solution but I think it was the blocky fonts in openSUSE.)
Sadly, it doesn’t seem to have applied to Firefox 3. I know there was some of the same in Ubuntu (my other distro) but their (altered) package fixed it. I wonder if there’s some way to get it right in openSUSE too.
Anyway, I guess that’ll have to wait for another day. Thank you guys so much for posting this discussion.
I too followed the instructions in this post and did not get it working.
I am getting the same sort of errors attempting the RPM build. I have done this as root and added the permissions to the various directories mentioned in this thread as well as ensuring the correct dependencies are installed.
RPM build errors:
InstallSourcePackage: Header V3 DSA signature: NOKEY, key ID 58857177
Bad exit status from /var/tmp/rpm-tmp.49298 (%prep)
It’s terrible, I know.
What worked for me is setting: KDE configuration centre (desktop settings) >> looks & themes >> Fonts >>> DPI settings >> 120dpi, it works for me with settings of all fonts to ‘11’ and using ‘Verdana’.
Also I have anti-aliasing on, no (!) sub-pixel hinting and hinting to full.
May not work for you, but play around in that department
Strangely enough, those are the settings I was using, except I had DPI at 96 as I found 120 a bit big and blocky, (and turning hinting on/off doesn’t make any difference). But a better compromise is dpi at 120 and verdana at 10, that works better for me, thanks for that! (Btw if anyone else is trying this you have to log out to see changes in DPI.)
Just noticed that the Community page has been updated to a simple one-click install,