FS#56899 - [ttf-font-awesome, i3wm] new font-awesome 5.0.x leads to an unrendered symbol in i3bar

Attached to Project: Community Packages
Opened by Andreas Radke (AndyRTR) - Friday, 29 December 2017, 18:56 GMT
Last edited by Morten Linderud (Foxboron) - Tuesday, 27 February 2018, 10:51 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jelle van der Waa (jelly)
Levente Polyak (anthraxx)
Morten Linderud (Foxboron)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 12
Private No

Details

Description:

With new ttf-font-awesome 5.0.2 pkg I have an unrendered square behind icons(Icon-unrenderedLetter-workspace name). Old version v4 works well here (icon-space-workspace name). No idea if this is an issue on the i3-wm side (no upstream bug found) or an unwanted "feature" in font-awesome v5. Another Arch user confirmed this behavior in #i3 IRC channel.
This task depends upon

Closed by  Morten Linderud (Foxboron)
Tuesday, 27 February 2018, 10:51 GMT
Reason for closing:  Upstream
Additional comments about closing:  This seems to be an upstream issue, not a packaging issue. If TTF doesn't work. Use OTF. If you are still missing glyphs; use Regular and Bold.
Comment by Morten Linderud (Foxboron) - Friday, 29 December 2017, 19:18 GMT
This is a font awesome issue i believe. The OTF font works, TTF does not. I have no idea why, and haven't really had time to investigate.

There is probably a few problems with the 4.7 -> 5 bump as glyphs have been removed and so on.
Comment by Alex Ozer (mind) - Saturday, 30 December 2017, 14:49 GMT
Also confirmed with polybar; none of the unique 6 icons I use appear, and polybar logs report unmatched characters.
Comment by Florian Keruzore (fkrz) - Saturday, 30 December 2017, 15:39 GMT
Can confirm problem with font-awesome. I have the same using polybar with bspwm. Will try otf and give update.
Comment by Morten Linderud (Foxboron) - Saturday, 30 December 2017, 15:57 GMT
I am contemplating just revering the 5.x update and stick with 4.7.0. Current font awesome is payware with a free subset that is packaged. Need some opinions
Comment by Bill Williamson (Bill_Williamson) - Saturday, 30 December 2017, 19:47 GMT
I confirm that this problem exists at i3blocks. Spaces before and after the FontAwesome characters turn into rectangles with numbers. Also, some of the FontAwesome characters stopped displaying correctly.
Comment by Morten Linderud (Foxboron) - Saturday, 30 December 2017, 21:16 GMT
{{Was duplicate}}
Comment by Alex Ozer (mind) - Saturday, 30 December 2017, 21:54 GMT
I don't quite understand, why can't the free subset of 5.x be packaged?
Comment by Morten Linderud (Foxboron) - Sunday, 31 December 2017, 00:34 GMT
Glyphs have been removed, modified and new ones have been added. Even if TTF is fixed, you might have to change symbols. I also don't like the payware model they are using.
Comment by Ho Tuan Kiet (tuankiet65) - Tuesday, 02 January 2018, 05:08 GMT
Looks like that right after an icon character, the U+0020 (aka space) character isn't rendered correctly, and will be rendered as a rectangle box instead. Spaces work right after text though.
   Screenshot from 2018-01-02 12... (5.7 KiB)
Comment by ice (icemodding) - Saturday, 06 January 2018, 06:06 GMT
same problem here. icon+0020 that character isn't rendered correctly. i3wm + i3blocks. ttf-font-awesome 5.0.2-1. meanwhile, install from aur: ttf-font-awesome-4. :-/
Comment by ael (ael) - Saturday, 06 January 2018, 16:18 GMT
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
Comment by ael (ael) - Saturday, 06 January 2018, 16:58 GMT
Anyway installing otf-fontawesome-5 fixed the problem for me.

Loading...