freetype2 2.6.4-2 is broken

stef_204 · 2016-09-11 21:53:56

brebs wrote:

*Look* at the source code. FT2_SUBPIXEL_HINTING is not in the source code, so it is irrelevant.

You're correct. The only reason I have FT2_SUBPIXEL_HINTING is because I have downgraded freetype2 until I find a fix.

What you want, with freetype 2.7, is e.g.:
export FREETYPE_PROPERTIES="truetype:interpreter-version=38"

Correct. And I have already posted several times (in my original post re. freetype 2.7-2 and subsequent ones) that I HAVE used those properties, all of them as a matter of fact, and none are having an impact on my system.

Last edited by stef_204 (2016-09-11 22:02:01)

stef_204 · 2016-09-12 00:15:51

brebs wrote:

*Look* at the source code.

@brebs

I took another look and didn't realize I could enable/disable some properties/parameters at compile time by editing ftoption.h (my bad as I already do that with other programs like dwm, etc.)
https://www.freetype.org/

I have now downloaded the source using abs and looked at ftoption.h. (In your original reply, I had just looked at the "diff" and incorrectly assumed it was a patch, not noticing the file name.)

#define FT_CONFIG_OPTION_ENVIRONMENT_PROPERTIES

is definitely enabled in abs source ftoption.h--used to compile official package. Not sure how compiling it locally would make a difference since this package version just came out today and my system is up-to-date but I will try, might work.

As far as options available to switch on/off in ftoption.h, I do know not if there are any other ones to tweak so as to achieve same effect as freetype2 2.6.5 version with classic mode--which I guess in 2.7 should be now be

truetype:interpreter-version=35

.

Will post back after compile. And will also

echo $FREETYPE_PROPERTIES

afterwards to see if it "took", etc.

Thanks.

Last edited by stef_204 (2016-09-12 00:17:24)

stef_204 · 2016-09-12 00:33:29

Well, off to a bad start here.....

==> Starting prepare()...
patching file modules.cfg
Reversed (or previously applied) patch detected!  Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file modules.cfg.rej
==> ERROR: A failure occurred in prepare().
    Aborting...

============

Edit: the above error is fixed, it compiles. Will install and test tomorrow.

Last edited by stef_204 (2016-09-12 19:40:09)

stef_204 · 2016-09-12 08:01:32

Good news: After compiling it locally, it finally works. I don't know why the official binary wasn't "taking" on my box, e.g. what libs, etc,. are "out of sync" with the most recent distro state, or whatever else is the problem.

In summary:

0) get over initial frustration with fonts and font rendering
1) comment out (or remove)

/etc/profile.d/extras.sh

containing

export FT2_SUBPIXEL_HINTING=0

2) leave in place the xml file mentioned previously, i.e. "$HOME/.config/fontconfig/fonts.conf"
3) download freetype2-2.7-2 with abs and just compile it directly.
4) make sure

/etc/profile.d/freestyle2.sh

contains

truetype:interpreter-version=35

(or whatever property desired)
5) I chose to reboot instead of just logging out.
6) check env variable:

% echo $FREETYPE_PROPERTIES 
truetype:interpreter-version=35

As brebs mentioned, does not hurt to read source, e.g. ftoption.h (and other files) and Wiki page

Looks like there's quite a bit of customizing available.

Thanks brebs and all whom replied to me on this issue.

Last edited by stef_204 (2016-09-12 10:34:47)

stefan · 2016-09-12 08:03:15

Another idea: Have you verified that FREETYPE_PROPERTIES is actually
set in your environment? Sorry, I did not see this in your posts (but
I just browsed them quickly)

$ echo $FREETYPE_PROPERTIES
truetype:interpreter-version=35

If not, is `/etc/profile.d/freetype2.sh` executable?

$ ls -l /etc/profile.d/freetype2.sh
-rwxr-xr-x 1 root root 544 Sep 12 09:43 /etc/profile.d/freetype2.sh

I had to set the x-bits...

stef_204 · 2016-09-12 08:12:34

stefan wrote:

If not, is `/etc/profile.d/freetype2.sh` executable?
$ ls -l /etc/profile.d/freetype2.sh
-rwxr-xr-x 1 root root 544 Sep 12 09:43 /etc/profile.d/freetype2.sh
I had to set the x-bits...

Problem is already solved (see previous post.)

To comment on the permissions issue you mention, freetype2.sh is installed with 644, based on PKGBUILD. (There is no need to execute anything actually, it is just a variable which needs to be read)
It has -rw-r--r-- 1 root root permissions.

Line 75 in PKGBUILD is:

 install -Dm644 ../freetype2.sh "${pkgdir}/etc/profile.d/freetype2.sh"

and that works on my box.

Last edited by stef_204 (2016-09-12 10:32:36)

everytrash · 2016-09-12 12:33:13

Same problem here! After setting this:

FREETYPE_PROPERTIES='truetype:interpreter-version=35'

It works again BUT "chromium" looks like sh***!

fatmike · 2016-09-12 14:57:53

Ok, i have

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

in /etc/profile.d/freetype2.sh
and

<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
  <match target="font">
    <edit name="hintstyle" mode="assign">
      <const>hintfull</const>
    </edit>
    <edit name="rgba" mode="assign">
      <const>rgb</const>
    </edit>
    <edit name="lcdfilter" mode="assign">
      <const>lcddefault</const>
    </edit>
  </match>
</fontconfig>

in ~/.config/fontconfig/fonts.conf and now i'm back to normal.

Bonus: Tune some Windows fonts

  <!-- Slight hinting for some windows fonts -->
  <match target="font">
    <test qual="any" name="family">
      <string>Segoe UI</string>
    </test>
    <edit name="hintstyle" mode="assign">
      <const>hintslight</const>
    </edit>
  </match>

  <!-- Disable embedded bitmap for some fonts -->
  <match target="font">
    <test qual="any" name="family">
      <string>Calibri</string>
    </test>
    <edit name="embeddedbitmap">
      <bool>false</bool>
    </edit>
  </match>

Last edited by fatmike (2016-09-12 14:59:53)

Onyros · 2016-09-12 21:39:41

everytrash wrote:

Same problem here! After setting this:
FREETYPE_PROPERTIES='truetype:interpreter-version=35'
It works again BUT "chromium" looks like sh***!

Looks like Chromium has a mind of its own when it comes to the hinting it uses.

This whole freetype2 thing has been quite the (upstream, I suppose) clusterfuck, lately.

Last edited by Onyros (2016-09-12 21:40:06)

andronasx · 2016-09-13 08:55:59

everytrash wrote:

Same problem here! After setting this:
FREETYPE_PROPERTIES='truetype:interpreter-version=35'
It works again BUT "chromium" looks like sh***!

Same here. I just set the same thing, and chromium also looks like crap. But at least my regular fonts are back! I had to look around for a while before I found this fix. Thanks guys! (It was a really frustrating experience.)

jasonwryan · 2016-09-13 09:12:28

As freetype is now at 2.7 this is done. There is a separate thread about the ongoing issues with Chromium.

Closing.

Arch Linux

#51 2016-09-11 21:53:56

Re: freetype2 2.6.4-2 is broken

#52 2016-09-12 00:15:51

Re: freetype2 2.6.4-2 is broken

#53 2016-09-12 00:33:29

Re: freetype2 2.6.4-2 is broken

#54 2016-09-12 08:01:32

Re: freetype2 2.6.4-2 is broken

#55 2016-09-12 08:03:15

Re: freetype2 2.6.4-2 is broken

#56 2016-09-12 08:12:34

Re: freetype2 2.6.4-2 is broken

#57 2016-09-12 12:33:13

Re: freetype2 2.6.4-2 is broken

#58 2016-09-12 14:57:53

Re: freetype2 2.6.4-2 is broken

#59 2016-09-12 21:39:41

Re: freetype2 2.6.4-2 is broken

#60 2016-09-13 08:55:59

Re: freetype2 2.6.4-2 is broken

#61 2016-09-13 09:12:28

Re: freetype2 2.6.4-2 is broken

Board footer