https://bugzilla.novell.com/show_bug.cgi?id=118131 ------- Comment #99 from mfabian@novell.com 2007-03-23 17:07 MST ------- Sven Burmeister> It certainly does work for me with the packages from Sven Burmeister> ftp://ftp.suse.com/pub/projects/OpenOffice.org/10.2-i386/2.1-0.1 Sven Burmeister> and editing /etc/fonts/suse-hinting.conf. Yet Sven Burmeister> something resets that value, I think it is Sven Burmeister> SuSEconfig. Yes, the comment at the top of /etc/fonts/suse-hinting.conf warns you that this is overwritten by SuSEconfig and that you should put your changes into ~/.fonts.conf. I.e. you can put <match target="pattern" > <edit mode="assign" name="autohint" > <bool>false</bool> </edit> </match> into ~/.fonts.conf to get this for one user. To get the change for all users you could create a file /etc/fonts/local.conf and put the change there (see /etc/fonts/conf.d/55-local.conf). The template used by SuSEconfig to overwrite /etc/fonts/suse-hinting.conf comes from the package “fonts-config” (/usr/share/fonts-config/suse-hinting.conf.template). You could also edit that template to get the change system wide. But just wait a few hours and get the updated “fontconfig”and “fonts-config” packages from http://software.opensuse.org/download/M17N/openSUSE_10.2/ I've already submitted updated “fontconfig” and “fonts-config” packages to STABLE and the openSUSE build service. They will be available under the above URL as soon as the build service has finished building them which seems to be a bit slow at the moment. Might take some more hours. Sven Burmeister> I get bytecode-rendered fonts without aa for both UI and text. Yes, and also with aa the byte code interpreter is used. I still think that it is a bug in OpenOffice to take the autohint value from “pattern” if it is there and enforce it even if a rule matching on “font” tries to override this. I don't think any other program does something like this. OpenOffice should not fiddle with the hinting settings in such mysterious ways, if at all possible the system settings should be used just like all the other programs do. Of course then one may run into problems because of the distortion of the metric caused by the hinting. But there must be other ways to solve this. *And*, the metrics are distorted mainly when the autohinter is used. When the autohinter is used lenghts of strings change significantly when comparing rendering with and without hinting. It appears to me that when the byte code interpreter is used the lengths of strings don't change significantly when comparing rendering with and without hinting. I.e. the byte code interpreter distorts the metrics far less than the autohinter does. Possibly there is no distortion at all. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.