New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing bytecode font hinting #11402

Closed
rpallai opened this Issue Dec 11, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@rpallai
Copy link

rpallai commented Dec 11, 2017

  • Electron version: 1.6.9
  • Operating system: Fedora 26

Electron does not use bytecode font hinting at all. This is very visible with disabled antialiasing. With enabled antialiasing the effect is not so obvious, feels like font rendering is blurry or simply weird. Autohint is used which better than nothing but worse than bytecode hinting.

Reproduce on Linux:

  1. Save the following snippet into ~/.fonts-atomtest.conf:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
        <include>/etc/fonts/fonts.conf</include>

        <match target="font">
            <!-- enable hinting -->
            <edit name="hinting" mode="assign"><bool>true</bool></edit>
            <!-- no autohint but bytecode -->
            <edit name="autohint" mode="assign"><bool>false</bool></edit>
            <edit name="hintstyle" mode="assign"><const>hintfull</const></edit>
            <!-- for very visible results -->
            <edit name="antialias"><bool>false</bool></edit>
        </match>
</fontconfig>
  1. Run FONTCONFIG_FILE=~/.fonts-atomtest.conf atom -f
  2. Use a bytecode hinted font in Atom, like the good old Arial or Liberation Mono and see ugly, fuzzy font rendering. Try other application (eg. kwrite) with the same FONTCONFIG_FILE and font family and see the difference.

There is no reason to avoid bytecode hinting, use if possible.

@welcome

This comment has been minimized.

Copy link

welcome bot commented Dec 11, 2017

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

To help make it easier for us to investigate your issue, please follow the contributing guidelines.

@MarshallOfSound

This comment has been minimized.

Copy link
Member

MarshallOfSound commented Dec 11, 2017

@codebytere

This comment has been minimized.

Copy link
Member

codebytere commented Sep 24, 2018

We are no longer implementing bugfixes for versions of Electron <= 1.7.x, so i'm going to close this issue but if it is still persisting in more recent versions of Electron we can certainly reopen it!

@codebytere codebytere closed this Sep 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment