https://bugzilla.novell.com/show_bug.cgi?id=396183
User mfabian@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=396183#c6
Mike Fabian changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #6 from Mike Fabian 2008-06-03 04:31:32 MDT ---
It is OK that KDE3 and KDE4 write to ~/.fonts.conf.
They should not overwrite any settings you wrote manually to
~/.fonts.conf though. They should read in any ~/.fonts.conf
which already exists and write back all settings which were not
changed in the KDE control centre as they were before.
I think there are some cases where this doesn’t work correctly,
but not in the simple case of your bug report, this simple
case works correctly both for KDE3 and KDE4.
You can verify that by editing for example
<match target="font" >
<edit mode="assign" name="hintstyle" >
<const>hintmedium</const>
</edit>
</match>
to different values ("hintnone", "hintslight", "hintmedium",
"hintfull") manually with an editor and then then start "kcmshell
fonts". You see that your manually edited value is read in and
displayed in "kcmshell fonts".
This works for the other values in your attached .fonts.conf as well.
KDE reads in the values from ~/.fonts.conf and therefore doesn’t
overwrite any of your settings.
In case of variables which cannot (yet) be set in KDE3 or KDE4 for
example autohint=true/false, these rules are read in by KDE3 and KDE4
and written out again unchanged, i.e. they are not destroyed either,
the value you edited manually is preserved.
I just tested again that this works with KDE3 and KDE4.
I think the only cases where it doesn’t yet work correctly are fairly
complicated rules in ~/.fonts.conf where the order is important and
and KDE doesn’t write back the correct order as it was intended by the
manual edit.
In your attached .fonts.conf, the order of the rules doesn’t matter
at all.
→ INVALID.
--
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.