You are not logged in.

#26 2020-03-14 17:43:38

linux_user
Member
Registered: 2016-11-04
Posts: 458

Re: Bunsenifying Debian Buster in a Thinkpad X230

ohnonot wrote:

Also look at ~/.config/fontconfig/fonts.conf.
This is what mine looks like:

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>

<!-- CAREFUL!
USER CONFIGURATION PRIORITY RAISED FROM 50- TO 21- 
IN /etc/fonts/conf.d -->

<!-- Generic name aliasing -->
<alias>
	<family>sans</family>
	<prefer>
		<family>IBM Plex Sans Condensed</family>
	</prefer>
</alias>
<alias>
	<family>sans-serif</family>
	<prefer>
		<family>IBM Plex Sans Condensed</family>
	</prefer>
</alias>
<alias>
	<family>serif</family>
	<prefer>
		<family>IBM Plex Serif</family>
	</prefer>
</alias>
<alias binding="same">
	<family>monospace</family>
	<accept>
		<family>IBM Plex Mono</family>
		<family>xos4 Terminus</family>
		<family>Terminus</family>
		<family>Monaco</family>
		<family>Andale Mono</family>
	</accept>
</alias>

<!-- Bitstream Charter is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font -->
<match target="pattern">
	<test name="family" qual="any">
		<string>Bitstream Charter</string>
	</test>
	<edit mode="assign" name="family" binding="same">
		<string>sans-serif</string>
	</edit>
</match>

<!-- Helvetica is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font -->
<match target="pattern">
	<test name="family" qual="any">
		<string>Helvetica</string>
	</test>
	<edit mode="assign" name="family">
		<string>sans-serif</string>
	</edit>
</match>

<match target="font">
 <edit mode="assign" name="rgba">
  <const>rgb</const>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="hinting">
  <bool>true</bool>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="hintstyle">
  <const>hintslight</const>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="antialias">
  <bool>true</bool>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="lcdfilter">
   <const>lcddefault</const>
 </edit>
</match>

<match target="font">
 <edit mode="assign" name="autohint">
  <bool>false</bool>
 </edit>
</match>

<!--
Interesting! This one overrides EVERYTHING
<match target="pattern">
    <edit name="family" mode="prepend" binding="strong">
        <string>Comic Sans MS</string>
    </edit>
</match>
-->

</fontconfig>

Helium renders Helvetica just fine. I check the fonts.conf of Helium and I see that the fallback for Helvetica as in yours isn't mentioned here. Is it mentioned in any other config files? Or is there any other way that Helvetica is rendered in Helium?

toor@X230:~$ cat /media/toor/ssd/toor/.config/fontconfig/fonts.conf 
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
    <match target="font">
        <edit mode="assign" name="hinting" >
            <bool>true</bool>
        </edit>
        <edit mode="assign" name="autohint" >
            <bool>true</bool>
        </edit>
        <edit mode="assign" name="hintstyle" >
            <const>hintslight</const>
        </edit>
        <edit mode="assign" name="rgba" >
            <const>rgb</const>
        </edit>
        <edit mode="assign" name="antialias" >
            <bool>true</bool>
        </edit>
        <edit mode="assign" name="lcdfilter">
            <const>lcddefault</const>
        </edit>
    </match>

<!--
    This section allows the user to define the fonts used for the
    "serif", "sans-serif" and "monospace" aliases.

    These aliases can then be set in lxappearance (the theme-changing
    GUI used by BunsenLabs) and also in individual programs to allow
    this file to be used for desktop-wide font configuration.

    By default, BunsenLabs uses one of these aliases everywhere
    a font needs to be specified. Set your favourite fonts here
    to ensure consistency across your working environment.
    You can still change fonts on a per-application basis if you want.
-->

    <alias>
        <family>serif</family>
        <prefer>
            <family>Noto Serif</family>
        </prefer>
    </alias>
    <alias>
        <family>sans-serif</family>
        <prefer>
            <family>Noto Sans</family>
        </prefer>
    </alias>
    <alias>
        <family>monospace</family>
        <prefer>
            <family>Noto Mono</family>
        </prefer>
    </alias>

</fontconfig>

"Blind faith to authority is the greatest enemy of truth."

Offline

#27 2020-03-15 08:40:28

ohnonot
...again
Registered: 2015-09-29
Posts: 4,418
Website

Re: Bunsenifying Debian Buster in a Thinkpad X230

How a font renders depends on which fonts are actually installed that provide that font name.
Helvetica used to be a problem there because it's a fairly common name, but used to default to some bitmap font. I don't think this is often the case anymore in 2020. But by all means try this:

fc-match helvetica

Offline

#28 2020-03-15 08:50:00

linux_user
Member
Registered: 2016-11-04
Posts: 458

Re: Bunsenifying Debian Buster in a Thinkpad X230

ohnonot wrote:

But by all means try this:

fc-match helvetica

Thanks, your code gave me some insights. It may explain why Firefox is rendering a different font for Helvetica.

toor@X230:~$ fc-match Helvetica
DejaVuSans.ttf: "DejaVu Sans" "Book"

As I have it in my fonts.conf file, Dejavu Sans is no more the default Sans font, it's been replaced by Noto Sans. This change is effective system wide as I can see. Also, in fonts.conf, Helvetica is to be replaced by the default Sans, which is Noto Sans (Not Dejavu Sans). I am wondering why this change is in effect. To save time, here's my fonts.conf,

toor@X230:~$ cat .config/fontconfig/fonts.conf 
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>

<!-- CAREFUL!
USER CONFIGURATION PRIORITY RAISED FROM 50- TO 21- 
IN /etc/fonts/conf.d -->

<!-- Generic name aliasing -->
<alias>
	<family>sans</family>
	<prefer>
		<family>Noto Sans</family>
	</prefer>
</alias>
<alias>
	<family>sans-serif</family>
	<prefer>
		<family>Noto Sans</family>
	</prefer>
</alias>

<!-- Bitstream Charter is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font -->
<match target="pattern">
	<test name="family" qual="any">
		<string>Bitstream Charter</string>
	</test>
	<edit mode="assign" name="family" binding="same">
		<string>sans-serif</string>
	</edit>
</match>

<!-- Helvetica is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font.
<match target="pattern">
	<test name="family" qual="any">
		<string>Helvetica</string>
	</test>
	<edit mode="assign" name="family">
		<string>sans-serif</string>
	</edit>
</match>-->

<!-- Helvetica is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font-->

    <match>
        <test name="family"><string>Helvetica</string></test>
        <edit mode="assign" name="family" binding="strong"><string>sans-serif</string></edit>
    </match>

<match target="font">
 <edit mode="assign" name="rgba">
  <const>rgb</const>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="hinting">
  <bool>true</bool>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="hintstyle">
  <const>hintslight</const>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="antialias">
  <bool>true</bool>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="lcdfilter">
   <const>lcddefault</const>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="autohint">
  <bool>false</bool>
 </edit>
</match>

</fontconfig>

"Blind faith to authority is the greatest enemy of truth."

Offline

#29 2020-03-15 09:02:15

ohnonot
...again
Registered: 2015-09-29
Posts: 4,418
Website

Re: Bunsenifying Debian Buster in a Thinkpad X230

fc-match doesn't lie and reflects changes made to ~/.config/fontconfig/fonts.conf immediately.

Do you know what XML comments look like?

<!-- This is a comment -->

Are you using a code editor with syntax highlighting? You really should.

Offline

#30 2020-03-15 10:01:13

linux_user
Member
Registered: 2016-11-04
Posts: 458

Re: Bunsenifying Debian Buster in a Thinkpad X230

ohnonot wrote:

fc-match doesn't lie and reflects changes made to ~/.config/fontconfig/fonts.conf immediately.

Do you know what XML comments look like?

I see what you mean @ohonot smile. Below that commented Helvetica replacement code, there is another similar code which was told to be updated code by hhh much later after you had posted your fonts.conf. Just tried it too. The important thing is both code doesn't make Firefox render NotoSans instead of Helvetica.

Last edited by linux_user (2020-03-15 10:22:38)


"Blind faith to authority is the greatest enemy of truth."

Offline

#31 2020-03-17 01:23:56

hhh
Meep!
Registered: 2015-09-17
Posts: 9,309
Website

Re: Bunsenifying Debian Buster in a Thinkpad X230

linux_user wrote:

I see what you mean @ohonot smile. Below that commented Helvetica replacement code, there is another similar code which was told to be updated code by hhh much later after you had posted your fonts.conf. Just tried it too. The important thing is both code doesn't make Firefox render NotoSans instead of Helvetica.

Link to a website, and screenshot of your rendering, please.

Offline

#32 2020-03-17 12:31:21

linux_user
Member
Registered: 2016-11-04
Posts: 458

Re: Bunsenifying Debian Buster in a Thinkpad X230

  • Forum home page in Helium: (mega, imgur)

  • Forum home page in Buster: (mega, imgur)

  • Forum home page in Buster being inspected: (mega, imgur)

  • Forum home page in Buster with Helvetica removed: (mega, imgur)

The screenshots have been explained in this post,

Last edited by linux_user (2020-03-17 12:37:11)


"Blind faith to authority is the greatest enemy of truth."

Offline

#33 2020-03-18 05:45:43

ohnonot
...again
Registered: 2015-09-29
Posts: 4,418
Website

Re: Bunsenifying Debian Buster in a Thinkpad X230

Please show us your complete and current ~/.config/fontconfig/fonts.conf again. How it looks now. I’m not sure you understood my remark about XML comments. In code, a comment means something that the interpreter considers non-existent. It could be a comment the programer left to explain what their program is doing, it could be a block of code not in use.

Offline

#34 2020-03-19 11:39:14

linux_user
Member
Registered: 2016-11-04
Posts: 458

Re: Bunsenifying Debian Buster in a Thinkpad X230

^ the config hasn't changed at all from earlier. And I have checked it with Sublime Text - seems nothing that shouldn't be commented is commented. Anyway, here's the configs,

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>

<!-- CAREFUL!
USER CONFIGURATION PRIORITY RAISED FROM 50- TO 21- 
IN /etc/fonts/conf.d -->

<!-- Generic name aliasing -->
<alias>
	<family>sans</family>
	<prefer>
		<family>Noto Sans</family>
	</prefer>
</alias>
<alias>
	<family>sans-serif</family>
	<prefer>
		<family>Noto Sans</family>
	</prefer>
</alias>

<!-- Bitstream Charter is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font -->
<match target="pattern">
	<test name="family" qual="any">
		<string>Bitstream Charter</string>
	</test>
	<edit mode="assign" name="family" binding="same">
		<string>sans-serif</string>
	</edit>
</match>

<!-- Helvetica is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font.
<match target="pattern">
	<test name="family" qual="any">
		<string>Helvetica</string>
	</test>
	<edit mode="assign" name="family">
		<string>sans-serif</string>
	</edit>
</match>-->

<!-- Helvetica is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font-->

    <match>
        <test name="family"><string>Helvetica</string></test>
        <edit mode="assign" name="family" binding="strong"><string>sans-serif</string></edit>
    </match>

<match target="font">
 <edit mode="assign" name="rgba">
  <const>rgb</const>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="hinting">
  <bool>true</bool>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="hintstyle">
  <const>hintslight</const>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="antialias">
  <bool>true</bool>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="lcdfilter">
   <const>lcddefault</const>
 </edit>
</match>
<match target="font">
 <edit mode="assign" name="autohint">
  <bool>false</bool>
 </edit>
</match>

</fontconfig>

What surprises me is that Helium doesn't have this code to replaced Helvetica with the default Sans!

Last edited by linux_user (2020-03-19 11:55:17)


"Blind faith to authority is the greatest enemy of truth."

Offline

#35 2020-03-19 19:39:19

ohnonot
...again
Registered: 2015-09-29
Posts: 4,418
Website

Re: Bunsenifying Debian Buster in a Thinkpad X230

Your editor's syntax highlighting must be broken.
This is a comment:

<!-- Helvetica is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font.
<match target="pattern">
	<test name="family" qual="any">
		<string>Helvetica</string>
	</test>
	<edit mode="assign" name="family">
		<string>sans-serif</string>
	</edit>
</match>-->

Please remove the leading "<!--" and the ending "-->" if you want the content of this block to work.

linux_user wrote:

What surprises me is that Helium doesn't have this code to replaced Helvetica with the default Sans!

Why does that surprise you?
None of this is standard or default set up.

As I already wrote in post #7:

ohnonot wrote:

Try to get your default font fallbacks right.
If that isn't enough, read these articles: https://dt.iki.fi/search?q=fontconfig

Offline

#36 2020-03-19 20:29:40

linux_user
Member
Registered: 2016-11-04
Posts: 458

Re: Bunsenifying Debian Buster in a Thinkpad X230

ohnonot wrote:

Your editor's syntax highlighting must be broken.
This is a comment:

<!-- Helvetica is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font.
<match target="pattern">
	<test name="family" qual="any">
		<string>Helvetica</string>
	</test>
	<edit mode="assign" name="family">
		<string>sans-serif</string>
	</edit>
</match>-->

Please remove the leading "<!--" and the ending "-->" if you want the content of this block to work.

That piece of code is commented because as explained in my previous post, there was an 'updated code' posted by hhh. That code is below the commented code. For your convenience,

<!-- Helvetica is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font-->

    <match>
        <test name="family"><string>Helvetica</string></test>
        <edit mode="assign" name="family" binding="strong"><string>sans-serif</string></edit>
    </match>

Here, the actual code isn't commented. However, as I explained earlier, whether I use hhh's code or your code to replace Helvetica with default Sans, the system doesn't obey it. Something overrides it.

toor@X230:~$ fc-match helvetica
DejaVuSans.ttf: "DejaVu Sans" "Book"
ohnonot wrote:

Why does that surprise you? None of this is standard or default set up.

It surprises me because, by default, the Helium renders Nimbus Sans in place of Helvetica and I can't find the code that forces this change in Helium neither in /etc/fonts/fonts.conf or ~/.config/fontsconfig/fonts.conf.

toor@X230:~$ fc-match helvetica
n019003l.pfb: "Nimbus Sans L" "Regular"
ohnonot wrote:

Try to get your default font fallbacks right.
If that isn't enough, read these articles: https://dt.iki.fi/search?q=fontconfig

I've read the article. The fallbacks of my default fonts are are set in the same config file: default sans is Noto Sans and this is effective system wide. So I am assuming that there is nothing wrong with default fallbacks.

toor@X230:~$ fc-match san-serif
NotoSans-Regular.ttf: "Noto Sans" "Regular"
toor@X230:~$ fc-match sans
NotoSans-Regular.ttf: "Noto Sans" "Regular"
toor@X230:~$ fc-match anything
NotoSans-Regular.ttf: "Noto Sans" "Regular"

The problem is with the fallback of Helvetica to default Sans (Noto Sans in my case) set inside ~/.config/fontsconfig/fonts.config which the system is not obeying, probably because something over-rides it. Can't find out what it is.

I've already posted my .config/fontsconfig/fonts.config. Here's my /etc/fonts/fonts.conf, nothing seems odds here with regards to Helvetica as well.

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<!-- /etc/fonts/fonts.conf file to configure system font access -->
<fontconfig>
	<its:rules xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
		<its:translateRule translate="no" selector="/fontconfig/*[not(self::description)]"/>
	</its:rules>

	<description>Default configuration file</description>

<!--
	DO NOT EDIT THIS FILE.
	IT WILL BE REPLACED WHEN FONTCONFIG IS UPDATED.
	LOCAL CHANGES BELONG IN 'local.conf'.

	The intent of this standard configuration file is to be adequate for
	most environments.  If you have a reasonably normal environment and
	have found problems with this configuration, they are probably
	things that others will also want fixed.  Please submit any
	problems to the fontconfig bugzilla system located at fontconfig.org

	Note that the normal 'make install' procedure for fontconfig is to
	replace any existing fonts.conf file with the new version.  Place
	any local customizations in local.conf which this file references.

	Keith Packard
-->

<!-- Font directory list -->

	<dir>/usr/share/fonts</dir>
	<dir>/usr/X11R6/lib/X11/fonts</dir> <dir>/usr/local/share/fonts</dir>
	<dir prefix="xdg">fonts</dir>
	<!-- the following element will be removed in the future -->
	<dir>~/.fonts</dir>

<!--
  Accept deprecated 'mono' alias, replacing it with 'monospace'
-->
	<match target="pattern">
		<test qual="any" name="family">
			<string>mono</string>
		</test>
		<edit name="family" mode="assign" binding="same">
			<string>monospace</string>
		</edit>
	</match>

<!--
  Accept alternate 'sans serif' spelling, replacing it with 'sans-serif'
-->
	<match target="pattern">
		<test qual="any" name="family">
			<string>sans serif</string>
		</test>
		<edit name="family" mode="assign" binding="same">
			<string>sans-serif</string>
		</edit>
	</match>

<!--
  Accept deprecated 'sans' alias, replacing it with 'sans-serif'
-->
	<match target="pattern">
		<test qual="any" name="family">
			<string>sans</string>
		</test>
		<edit name="family" mode="assign" binding="same">
			<string>sans-serif</string>
		</edit>
	</match>

<!--
  Ignore dpkg temporary files created in fonts directories
-->
	<selectfont>
		<rejectfont>
			<glob>*.dpkg-tmp</glob>
		</rejectfont>
	</selectfont>
	<selectfont>
		<rejectfont>
			<glob>*.dpkg-new</glob>
		</rejectfont>
	</selectfont>

<!--
  Load local system customization file
-->
	<include ignore_missing="yes">conf.d</include>

<!-- Font cache directory list -->

	<cachedir>/var/cache/fontconfig</cachedir>
	<cachedir prefix="xdg">fontconfig</cachedir>
	<!-- the following element will be removed in the future -->
	<cachedir>~/.fontconfig</cachedir>

	<config>
<!--
  Rescan configuration every 30 seconds when FcFontSetList is called
 -->
		<rescan>
			<int>30</int>
		</rescan>
	</config>

</fontconfig>

"Blind faith to authority is the greatest enemy of truth."

Offline

#37 2020-03-20 10:14:01

ohnonot
...again
Registered: 2015-09-29
Posts: 4,418
Website

Re: Bunsenifying Debian Buster in a Thinkpad X230

I'm tired of this.
Re-read all my blog posts about this (or do your own research by all means). After 1 minute of reading I found a possible answer.
At the very least it will aid you to do proper troubleshooting.

Offline

#38 2020-03-22 08:19:18

linux_user
Member
Registered: 2016-11-04
Posts: 458

Re: Bunsenifying Debian Buster in a Thinkpad X230

Well @ohonot, I read them, over and over. Your first blog (chapter 1) is the one that is relevant to my issue and I see that you're changing the priorities of certain config files thereby fixing the default fonts. In your case, you knew which two config files were conflicting. In my case, I don't know which files are conflicting (assuming there is a conflict in the first place). My default fonts are all set. My only problem is in rendering the default font in place of Helvetica.

I have three files inside my /etc/fonts/: conf.d, conf.avail and fonts.config.
I have posted /etc/fonts/fonts.config in post# 36 (also, ~/.config/fontsconfig/fonts.config in post# 34).
Below are /etc/fonts/conf.d and /etc/fonts/conf.avail.

toor@X230:~$ ls /etc/fonts/conf.d
10-hinting-slight.conf                         58-dejavu-lgc-sans.conf       66-lohit-gurmukhi.conf
10-scale-bitmap-fonts.conf                     58-dejavu-lgc-sans-mono.conf  66-lohit-kannada.conf
11-lcdfilter-default.conf                      58-dejavu-lgc-serif.conf      66-lohit-odia.conf
20-unhint-small-dejavu-lgc-sans.conf           59-lohit-devanagari.conf      66-lohit-tamil-classical.conf
20-unhint-small-dejavu-lgc-sans-mono.conf      60-generic.conf               66-lohit-tamil.conf
20-unhint-small-dejavu-lgc-serif.conf          60-latin.conf                 66-lohit-telugu.conf
20-unhint-small-dejavu-sans.conf               65-0-fonts-beng-extra.conf    67-fonts-smc-manjari.conf
20-unhint-small-dejavu-sans-mono.conf          65-0-fonts-deva-extra.conf    67-smc-anjalioldlipi.conf
20-unhint-small-dejavu-serif.conf              65-0-fonts-gubbi.conf         67-smc-chilanka.conf
20-unhint-small-vera.conf                      65-0-fonts-gujr-extra.conf    67-smc-dyuthi.conf
30-0-google-crosextra-carlito-fontconfig.conf  65-0-fonts-guru-extra.conf    67-smc-karumbi.conf
30-metric-aliases.conf                         65-0-fonts-orya-extra.conf    67-smc-keraleeyam.conf
30-opensymbol.conf                             65-0-fonts-pagul.conf         67-smc-raghumalayalamsans.conf
40-nonlatin.conf                               65-0-fonts-telu-extra.conf    67-smc-suruma.conf
45-generic.conf                                65-0-smc-meera.conf           67-smc-uroob.conf
45-latin.conf                                  65-0-smc-rachana.conf         69-unifont.conf
49-sansserif.conf                              65-fonts-persian.conf         70-yes-bitmaps.conf
50-user.conf                                   65-nonlatin.conf              80-delicious.conf
51-local.conf                                  66-lohit-assamese.conf        90-fonts-linux-libertine.conf
57-dejavu-sans.conf                            66-lohit-bengali.conf         90-synthetic.conf
57-dejavu-sans-mono.conf                       66-lohit-devanagari.conf      README
57-dejavu-serif.conf                           66-lohit-gujarati.conf

50-user.conf tells the system to load the font conf in this order:

<include ignore_missing="yes" prefix="xdg">fontconfig/conf.d</include>
<include ignore_missing="yes" prefix="xdg">fontconfig/fonts.conf</include>

Since I do not have a conf.d file but only the fonts.conf file inside .config/fontconfig/, I do not see any conflicts.

I opened few other conf files to see if I can get some hints about Helvetica rendering, but it leads nowhere, perhaps because I am not adept in it. As I have mentioned in my first few posts, the very reason I am building packages on a bare system is to learn. So far, its been great but I'd agree though that I do not have the expertise of someone used to using a bare system.

Here's are the configs inside /etc/fonts/conf.avail

toor@X230:~$ ls /etc/fonts/conf.avail/
20-unhint-small-dejavu-lgc-sans.conf           62-google-crosextra-carlito-fontconfig.conf  66-lohit-gurmukhi.conf
20-unhint-small-dejavu-lgc-sans-mono.conf      65-0-fonts-beng-extra.conf                   66-lohit-kannada.conf
20-unhint-small-dejavu-lgc-serif.conf          65-0-fonts-deva-extra.conf                   66-lohit-odia.conf
20-unhint-small-dejavu-sans.conf               65-0-fonts-gubbi.conf                        66-lohit-tamil-classical.conf
20-unhint-small-dejavu-sans-mono.conf          65-0-fonts-gujr-extra.conf                   66-lohit-tamil.conf
20-unhint-small-dejavu-serif.conf              65-0-fonts-guru-extra.conf                   66-lohit-telugu.conf
30-0-google-crosextra-carlito-fontconfig.conf  65-0-fonts-orya-extra.conf                   67-fonts-smc-manjari.conf
30-droid-noto.conf                             65-0-fonts-pagul.conf                        67-lohit-malayalam.conf
30-droid-noto-mono.conf                        65-0-fonts-telu-extra.conf                   67-smc-anjalioldlipi.conf
57-dejavu-sans.conf                            65-0-smc-meera.conf                          67-smc-chilanka.conf
57-dejavu-sans-mono.conf                       65-0-smc-rachana.conf                        67-smc-dyuthi.conf
57-dejavu-serif.conf                           65-droid-sans-fallback.conf                  67-smc-karumbi.conf
58-dejavu-lgc-sans.conf                        66-lohit-assamese.conf                       67-smc-keraleeyam.conf
58-dejavu-lgc-sans-mono.conf                   66-lohit-bengali.conf                        67-smc-raghumalayalamsans.conf
58-dejavu-lgc-serif.conf                       66-lohit-devanagari.conf                     67-smc-suruma.conf
59-lohit-devanagari.conf                       66-lohit-gujarati.conf                       67-smc-uroob.conf

Right now, I am going through some of the man pages: https://jlk.fjfi.cvut.cz/arch/manpages/man/fonts-conf.5 and https://wiki.archlinux.org/index.php/Font_configuration. Also, I'll also check the configs in side Helium. Hopefully, something helps me out.


"Blind faith to authority is the greatest enemy of truth."

Offline

Board footer

Powered by FluxBB