Home Home > 2015 > 02 > 17 > fonts @ openSUSE
Sign up | Login

Deprecation notice: openSUSE Lizards user blog platform is deprecated, and will remain read only for the time being. Learn more...

fonts @ openSUSE

February 17th, 2015 by

Since I maintain fontconfig, time to time I hear contradicting opinions which font families should be used in the system if not said otherwise, i. e. which families should be preferred for sans, serif and monospace generic aliases and how they should be rendered. Bug reports I got was talking about overall system defaults, concerning fontconfig rules therefore.

General idea was to weaken the word ‘default’ in regard to font setting by creating a direct window into basic fontconfig setting of the system (of course: for advanced effects, fontconfig xml coding is still needed).

For my convenience, YaST framework was used and new module called fonts had seen the light of the day not long ago. It is packaged as yast2-fonts in Tumbleweed and in my home for openSUSE 13.2.


I hope that, together with fontinfo.o.o, tuning your fonts will be much easier!

Certainly, this module is not done. Firstly, I would like to fix bugs which users will meet. After this stabilizing period, perhaps next hackweek, I will consider how hard would be to add per-user setting capability to fonts-config script, which would almost automatically mean per-user font setting capability in the module itself.


Both comments and pings are currently closed.

2 Responses to “fonts @ openSUSE”

  1. Excellent something that “smooth” our live, if you’ve not done it I would like to see it in action at oSC15 …. 😉

  2. Eugene

    This is a great tool, many thanks Petr. I see there not only default fonts’ settings but font rendering options as well. What do you think about an ability to create font groups to set different rendering settings for them: i.e. to render fonts with good TT instructions with full hinting, and poorly hinted fonts with slight hinting; to enable embedded bitmaps/autohinter/whatever only for fonts in a group ? It greatly improves font rendering and it would be very convenient to manage these groups within UI.