Skip to content
This repository was archived by the owner on Apr 24, 2020. It is now read-only.
This repository was archived by the owner on Apr 24, 2020. It is now read-only.

Dealing with awesome-fontconfig codepoints #382

@bhilburn

Description

@bhilburn

Okay, it looks like we might have a code-point issue with some "awesome" fonts.

While doing some testing recently, I switched over to awesome-fontconfig and the OK_ICON was actually the medium.com logo. I'm not the only person it impacted - as an example, check out this bug report that just got filed, #375, and note that where there should be a checkmark there is actually the medium.com logo.

Per @V1rgul's comment, here, though, on his font the other icons were preferrable:
95f0c3c#commitcomment-20573173

Need to do some digging. I suspect that the solution is going to be that some people need to put manual overrides for certain ICONs in their configs. Not a huge deal, but it is an additional step, so we should try to make it work for as many people as possible out-of-the-box.

It would be great if more people could comment, here, on whether or not the old way or the new way is better for them. Please also describe how you installed your fonts, which font you are using, and which PL9k you are using.

@/all
@V1rgul @dritter @rjorgenson @Tritlo @ryanoasis @lcorsini

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions