Bug 121836 - Everytime a package is installed (or YOU update the system), /etc/fonts/suse-hinting.conf is reseted
Summary: Everytime a package is installed (or YOU update the system), /etc/fonts/suse-...
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Mike Fabian
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-08 09:20 UTC by Florent CHANTRET
Modified: 2005-10-10 10:39 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Florent CHANTRET 2005-10-08 09:20:00 UTC 
Hi,

All is in the title.

I've just launch a YOU update and my fonts are now ugly cause the less_eq value
for MS TT Core Fonts in /etc/fonts/suse-hinting.conf as been switched back from
18 (the value I previously set) to 0 (the initial value).

It's quite annoying and it happen too when I install new packages.
Comment 1 Mike Fabian 2005-10-10 10:09:17 UTC 
That's not a bug, see the comment at the top of the file:

    <!-- Generated by SuSEconfig.fonts, don't edit, your changes will get lost. -->
    <!-- Edit /etc/sysconfig/fonts-config instead.                              -->
    <!-- Or put rules into your personal config file ~/.fonts.conf.             -->

That means you should *not* edit that file to get your prefered value
of 18 for the limit to use the byte code interpreter for the MS
webfonts, you should put this into /etc/sysconfig/fonts-config.
Like this:

    ## Path:        Desktop
    ## Description: Display font configuration
    ## Type:        integer
    ## Default:     0
    #
    # Fonts which have high quality byte code interpreter instructions
    # can look very good in small sizes when rendered in black and white
    # (no anti-aliasing!) using the byte code interpreter (not the autohinter!).
    # The results look as good as high quality bitmap fonts.
    #
    # If you want to use this rendering style by default for all fonts
    # which are known to have good byte code instructions (these are the
    # fonts from the agfa-fonts package and the Microsoft webfonts), enter
    # an integer number greater than 0 here. For example, if you enter "18",
    # black and white rendering using the byte code interpreter will be used
    # for pixel sizes <= 18, for larger sizes the autohinter and anti-aliasing
    # will be used. You can disable this by entering "0".
    #
    BYTECODE_BW_MAX_PIXEL="18"

Closing as INVALID.
Comment 2 Florent CHANTRET 2005-10-10 10:27:24 UTC 
Sorry for the wrong bug report. I haven't read the file header as there were no
problem with RC1 and that was the methode given in another bug report ;o)

I will update my OpenSuse WIKI topic about MS TT Core Fonts soon ;o)

Regards
Comment 3 Mike Fabian 2005-10-10 10:39:24 UTC 
I have explained this in bug #114949 already and you were in the CC: all
the time.

See for example comment #6 and comment #13 for example in bug #114949.