Problems with fonts

iamamiwhoami · 2016-09-06 14:03:36

Hi. With the latest update I have had problems with the font . Problems of Firefox and Chromium , maybe somewhere else, but noticed only in those programs.

I use Clean font everywhere, set it in the settings mate environment. As much as I tried not to install Clean font in mate preferences, these programs install your font . In this case , the font size is very large in the UI, and does not change. The chromium problem only occurs in the UI. In Firefox, in address context menu search bar. I tried to install archlinux in virtualbox, at the same time put only base packages , base-devel, xorg-server, xorg-utils, xterm, xorg-xinit, mate. The system does not set up . In this case , Clean fonts work well , and not only Clean, and generally any other. Speculation about this no. I hope for you. I tried to log in as a new user , the custom settings can be thought broken, but nothing hlibxft 2.3.2-1 as changed.
-
fontconfig 2.12.1-3
freetype2 2.6.5-2
libxft 2.3.2-1
-
Thanks!

p.s: I partly use google translate. I apologize for the error .

pmatts · 2016-09-13 12:39:42

My non antialiased fonts also became ugly and blotchy/jagged after a recent update. My beloved tahoma is ruined I'm running everything antialised at the moment which makes everything all blurry and painful to read.

I also have no idea why or how to fix it.

Suggestions?

bart_vv · 2016-09-13 13:19:52

Try adding:

export FREETYPE_PROPERTIES="truetype:interpreter-version=35"

to your .bashrc. You may be hit by this, since freetype 2.7 is available on arch since Sep 8 (yet iamamiwhoami states he still has 2.6.5).

I also recommend instaling infinality for great looking fonts (this should be default IMO).

Last edited by bart_vv (2016-09-13 15:08:42)

PeterD · 2016-09-13 15:05:12

You have to keep up with the news on Linux

The new v40 TrueType interpreter mode

FreeType 2.7 Released With A Big Font Rendering Change

FreeType 2.7 Bringing DirectWrite/ClearType-Like Rendering -- Much Better Looking Fonts On Linux

Or read the actual Arch Wiki for Font Configuration

Font Configuration Wiki Page

When you install the package it has the file /etc/profile.d/freetype2.sh which is used to set the export statement.

EDIT: Added config file location as this is the Newbie forum, you may need to update the permissions of the file to let the file execute, (Hint) check other files that are in that directory if you want to see what permissions will need to be set to.

Last edited by PeterD (2016-09-13 15:37:57)

kokesssss · 2016-09-13 19:55:13

Hi,

please can someone clarify what is the current recommended configuration regarding usage of MS Windows fonts in wine? Before recent subpixel hinting changes, I've just copied fonts from my Windows installation as explained here: https://wiki.archlinux.org/index.php/Microsoft_fonts and it looked ok.

However the fonts are now very ugly. I used to setup FT2_SUBPIXEL_HINTING=0 and now FREETYPE_PROPERTIES="truetype:interpreter-version=35" to have fonts looking normally when running wine application. Does anyone know how to configure wine/fonts to use the newest minimal mode? There is a section https://wiki.archlinux.org/index.php/Mi … #Windows_7 mentioning infinality, but I'd rather run the newest engine, because I do not know infinality in detail either and it is now "old".

Thanks

Last edited by kokesssss (2016-09-13 19:57:10)

0strodamus · 2016-09-13 22:50:58

I was able to get Tahoma (and other fonts) looking normal again under my user account by uncommenting and changing

export FREETYPE_PROPERTIES="truetype:interpreter-version=35"

in /etc/profile.d/freetype2.sh as directed by the freetype2-2.7 post-install message.

However, running anything as root using gksu results in Tahoma looking horrible. After trying for awhile to fix this without success, I decided to just compile freetype2 locally with hinting entirely disabled. To do that, I commented out the default SUBPIXEL_HINTING value of 2 in ftoption.h. If anyone is interested in doing the same, just remove the 2 subpixel patches in Arch's PKGBUILD and use this patch instead.

diff -aur a/include/freetype/config/ftoption.h b/include/freetype/config/ftoption.h
--- a/include/freetype/config/ftoption.h	2016-09-01 22:47:15.000000000 -0700
+++ b/include/freetype/config/ftoption.h	2016-09-11 17:03:07.313433808 -0700
@@ -675,7 +675,7 @@
   /* [1] http://www.microsoft.com/typography/cleartype/truetypecleartype.aspx */
   /*                                                                       */
 /* #define TT_CONFIG_OPTION_SUBPIXEL_HINTING  1         */
-#define TT_CONFIG_OPTION_SUBPIXEL_HINTING  2
+/* #define TT_CONFIG_OPTION_SUBPIXEL_HINTING  2         */
 /* #define TT_CONFIG_OPTION_SUBPIXEL_HINTING  ( 1 | 2 ) */

EDIT: I wanted to update my post in case it can help someone else. I figured out how to get fonts looking normal again using gksu without compiling freetype2 locally. The issue is that sudo wasn't carrying over the FREETYPE_PROPERTIES environment variable set in /etc/profile.d/freetype2.sh. I added the following to /etc/sudoers and everything is fine now.

Defaults env_keep += "FREETYPE_PROPERTIES"

Last edited by 0strodamus (2016-09-27 00:43:14)

pmatts · 2016-09-14 10:55:47

Thankyou guys. Solution from bart_vv and Ostrodamus fixed my blotchy jagged tahoma

0strodamus · 2016-09-14 21:28:57

You're welcome. Glad to know it helped you.

pmatts · 2016-09-15 09:10:45

Just discovered that chromium is somehow exempt from this fix. Any ideas how I can bring it into line?

ooo · 2016-09-15 10:15:21

pmatts wrote:

Just discovered that chromium is somehow exempt from this fix. Any ideas how I can bring it into line?

There's already a thread and bug report for this issue: https://bbs.archlinux.org/viewtopic.php?id=216988

Arch Linux

#1 2016-09-06 14:03:36

Problems with fonts

#2 2016-09-13 12:39:42

Re: Problems with fonts

#3 2016-09-13 13:19:52

Re: Problems with fonts

#4 2016-09-13 15:05:12

Re: Problems with fonts

#5 2016-09-13 19:55:13

Re: Problems with fonts

#6 2016-09-13 22:50:58

Re: Problems with fonts

#7 2016-09-14 10:55:47

Re: Problems with fonts

#8 2016-09-14 21:28:57

Re: Problems with fonts

#9 2016-09-15 09:10:45

Re: Problems with fonts

#10 2016-09-15 10:15:21

Re: Problems with fonts

Board footer