Bug 17722 - Don't overwrite user's configurations in default config

Use "append" to avoid overwriting the user configuration.
This presumes most clients may takes care of the first value only.
This commit is contained in:
Akira TAGOH 2012-03-26 10:58:18 +09:00
parent 900675d0b0
commit 1aaf8b773d
10 changed files with 70 additions and 10 deletions

View File

@ -3,6 +3,12 @@
<fontconfig> <fontconfig>
<!-- Use the Autohinter --> <!-- Use the Autohinter -->
<match target="font"> <match target="font">
<edit name="autohint" mode="assign"><bool>true</bool></edit> <!--
This configuration is available on the major desktop environments.
We shouldn't overwrite it with "assign" unconditionally.
Most clients may picks up the first value only. so using "append"
may simply works to avoid it.
-->
<edit name="autohint" mode="append"><bool>true</bool></edit>
</match> </match>
</fontconfig> </fontconfig>

View File

@ -3,6 +3,12 @@
<fontconfig> <fontconfig>
<!-- Enable sub-pixel rendering --> <!-- Enable sub-pixel rendering -->
<match target="font"> <match target="font">
<edit name="rgba" mode="assign"><const>none</const></edit> <!--
This configuration is available on the major desktop environments.
We shouldn't overwrite it with "assign" unconditionally.
Most clients may picks up the first value only. so using "append"
may simply works to avoid it.
-->
<edit name="rgba" mode="append"><const>none</const></edit>
</match> </match>
</fontconfig> </fontconfig>

View File

@ -3,6 +3,12 @@
<fontconfig> <fontconfig>
<!-- Enable sub-pixel rendering --> <!-- Enable sub-pixel rendering -->
<match target="font"> <match target="font">
<edit name="rgba" mode="assign"><const>bgr</const></edit> <!--
This configuration is available on the major desktop environments.
We shouldn't overwrite it with "assign" unconditionally.
Most clients may picks up the first value only. so using "append"
may simply works to avoid it.
-->
<edit name="rgba" mode="append"><const>bgr</const></edit>
</match> </match>
</fontconfig> </fontconfig>

View File

@ -3,6 +3,12 @@
<fontconfig> <fontconfig>
<!-- Enable sub-pixel rendering --> <!-- Enable sub-pixel rendering -->
<match target="font"> <match target="font">
<edit name="rgba" mode="assign"><const>rgb</const></edit> <!--
This configuration is available on the major desktop environments.
We shouldn't overwrite it with "assign" unconditionally.
Most clients may picks up the first value only. so using "append"
may simply works to avoid it.
-->
<edit name="rgba" mode="append"><const>rgb</const></edit>
</match> </match>
</fontconfig> </fontconfig>

View File

@ -3,6 +3,12 @@
<fontconfig> <fontconfig>
<!-- Enable sub-pixel rendering --> <!-- Enable sub-pixel rendering -->
<match target="font"> <match target="font">
<edit name="rgba" mode="assign"><const>vbgr</const></edit> <!--
This configuration is available on the major desktop environments.
We shouldn't overwrite it with "assign" unconditionally.
Most clients may picks up the first value only. so using "append"
may simply works to avoid it.
-->
<edit name="rgba" mode="append"><const>vbgr</const></edit>
</match> </match>
</fontconfig> </fontconfig>

View File

@ -3,6 +3,12 @@
<fontconfig> <fontconfig>
<!-- Enable sub-pixel rendering --> <!-- Enable sub-pixel rendering -->
<match target="font"> <match target="font">
<edit name="rgba" mode="assign"><const>vrgb</const></edit> <!--
This configuration is available on the major desktop environments.
We shouldn't overwrite it with "assign" unconditionally.
Most clients may picks up the first value only. so using "append"
may simply works to avoid it.
-->
<edit name="rgba" mode="append"><const>vrgb</const></edit>
</match> </match>
</fontconfig> </fontconfig>

View File

@ -3,6 +3,12 @@
<fontconfig> <fontconfig>
<!-- Disable hinting --> <!-- Disable hinting -->
<match target="font"> <match target="font">
<edit name="hinting" mode="assign"><bool>false</bool></edit> <!--
This configuration is available on the major desktop environments.
We shouldn't overwrite it with "assign" unconditionally.
Most clients may picks up the first value only. so using "append"
may simply works to avoid it.
-->
<edit name="hinting" mode="append"><bool>false</bool></edit>
</match> </match>
</fontconfig> </fontconfig>

View File

@ -3,7 +3,13 @@
<fontconfig> <fontconfig>
<!-- Use lcddefault as default for LCD filter --> <!-- Use lcddefault as default for LCD filter -->
<match target="font"> <match target="font">
<edit mode="assign" name="lcdfilter"> <!--
This configuration is available on the major desktop environments.
We shouldn't overwrite it with "assign" unconditionally.
Most clients may picks up the first value only. so using "append"
may simply works to avoid it.
-->
<edit mode="append" name="lcdfilter">
<const>lcddefault</const> <const>lcddefault</const>
</edit> </edit>
</match> </match>

View File

@ -3,7 +3,13 @@
<fontconfig> <fontconfig>
<!-- Use lcdlegacy as default for LCD filter --> <!-- Use lcdlegacy as default for LCD filter -->
<match target="font"> <match target="font">
<edit mode="assign" name="lcdfilter"> <!--
This configuration is available on the major desktop environments.
We shouldn't overwrite it with "assign" unconditionally.
Most clients may picks up the first value only. so using "append"
may simply works to avoid it.
-->
<edit mode="append" name="lcdfilter">
<const>lcdlegacy</const> <const>lcdlegacy</const>
</edit> </edit>
</match> </match>

View File

@ -3,7 +3,13 @@
<fontconfig> <fontconfig>
<!-- Use lcdlight as default for LCD filter --> <!-- Use lcdlight as default for LCD filter -->
<match target="font"> <match target="font">
<edit mode="assign" name="lcdfilter"> <!--
This configuration is available on the major desktop environments.
We shouldn't overwrite it with "assign" unconditionally.
Most clients may picks up the first value only. so using "append"
may simply works to avoid it.
-->
<edit mode="append" name="lcdfilter">
<const>lcdlight</const> <const>lcdlight</const>
</edit> </edit>
</match> </match>