Skip to content
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

Weird block space characters after ttf-font-awesome characters #53

Closed
YodaEmbedding opened this issue Dec 31, 2017 · 9 comments
Closed

Comments

@YodaEmbedding
Copy link

YodaEmbedding commented Dec 31, 2017

It looks like spaces (0020) are being poorly displayed:

i3blocks

I'm guessing this comes with the recent update to ttf-font-awesome. The reason I raised this issue here is because vim and Sublime Text seem to be displaying the font correctly:

vim
subl

i3 config:

bar {
    status_command i3blocks
    font pango:FontAwesome 10
}

i3blocks config:

[disk]
label=
interval=30

(Notice that there is no space explicitly defined within label=.)

@0x6C38
Copy link

0x6C38 commented Dec 31, 2017

Same issue after update

@Anachron
Copy link
Owner

Anachron commented Jan 8, 2018

That's weird, does "fp-cache -f" do any change? (run as admin)

@YodaEmbedding
Copy link
Author

YodaEmbedding commented Jan 11, 2018

sudo fc-cache -f doesn't seem to have any effect.

@Anachron
Copy link
Owner

The weird thing is I cannot reproduce this on Void Linux (glibc).
If you specify two fonts (fallback font like "Ubuntu Mono, Source Code Pro" or alike), does the problem still appear?

@YodaEmbedding
Copy link
Author

YodaEmbedding commented Jan 12, 2018

I tried the following i3config configurations:

font pango:FontAwesome, pango:Roboto Mono 10
font pango:Roboto Mono, pango:FontAwesome 10

But none of them fixed this issue. I am using the i3-wm and i3blocks packages for Arch.

@chrisdruta
Copy link

Find a solution yet? I'm running i3-gaps with i3blocks on arch as well.

@Anachron
Copy link
Owner

I saw issues like this on the font-awesome repo issues. Can you report upstream?

@pree
Copy link

pree commented Jan 29, 2018

Found a Topic on the Archlinux Forums about this: https://bbs.archlinux.org/viewtopic.php?id=233098

Uninstalling ttf-font-awesome and installing otf-font-awesome worked for me.

@YodaEmbedding
Copy link
Author

This issue can be closed. (Though, I suppose for now that it might be better to leave open for visibility.)

Quoting @ael:

The bug is actually related to Pango. In fact i3wm use Pango to render text. The problem is that Pango does not correctly fallback to another font to render the space character U+0020 [1][2]. The new ttf Font Awesome 5 fonts do not provide anymore a space character, thus using a space after a proper Font Awesome char trigger the Pango bad behavior.

If you have ttf-fontawesome-5 installed you can reproduce the problem with:
pango-view -t ' A ' --font "pango:Font Awesome 5 Free"

You will see that the space after the bike (U+F206) is not correctly rendered while the space after the A letter is properly rendered.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=775202
[2] https://bugzilla.gnome.org/show_bug.cgi?id=780068

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants