i3bar space broken

[belak]

With i3bar, [0020] shows up after every icon I use. It seems like some icon fonts supply a space character so this doesn't happen. Would something like this be a possibility for siji? Or is there another workaround?

[stark]

Weird behavior. Can you please attach a screenshot of this behavior and the respective i3bar.conf where you're using the glyphs ?

[fletcherw]

I'm having the same issue. I reproduced it with the following i3status.conf (The superset glyph is the proper email glyph, github just renders it strangely):

# i3status.conf
order += "tztime local"
tztime local {
  format = " test"
}

This is what it looks like

I'm running i3status 2.8, i3/i3bar 4.10.3, and my normal i3bar font is Terminus

[brennovich]

I'm still having issues with blank char after Siji glyph. I managed to fix by adding tab chaining FontAwesome 4

[diffficult]

@brennovich sorry to necro bump this closed issue but could you explain which character you used to? I've tried using u+0020 from fontawesome but I still get the empty [0020] character error on i3status bar.

[kootenpv]

I've also had enough. @brennovich could you reveal what exactly you did? I tried those "look a like spaces", but they don't work. Tab works, but is still very ugly most of the time.

EDIT: Ok, so that thread linked explains how to do it. Uninstall ttf-font-awesome, and install ttf-font-awesome-4

[diffficult]

@kootenpv ohh ok, I see it know. Missed that as well.

[brennovich]

Exactly, you'll need this old version of font-awesome, but soft spaces still won't work. I had to use tabs!

# i3 font config
font pango: FontAwesome, Scientifica, Siji 7

cpu_temperature 0 {
    format = "\    %degrees°C"
}

this > is my vim displaying tabs ;)

[streambag]

I'd just like to say that I worked around a similar issue in i3status by adding a u+202D character (left-to-right override) between the icon and the space. The character itself is invisible, but it seems to be enough to get pango to switch to a different font for rendering the space. Perhaps that approach could work here as well.

[brennovich]

Thanks @streambag it worked for me as well :)

1. Using u+202d + space
2. Removed FontAwesome from my font chain

I think it's better, one less font, one less dependency.