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
FontAwesome icons not rendered correctly #65
Comments
Setting Are you wanting to use font-awesome directly in markup? Or are you finding one of the existing admon icons isn't correct? |
Yes, the sources I deal with contain |
I remember a bit more about why the font support is so odd. The CSS for this backend is based on Antora and they don't currently have support for font-awesome. We use the I've got something hacked locally that reinstates font-awsome 4 support but I need to do some more testing before it can be merged. |
Thanks for the update, Phil! Happy to give some snapshots a spin if that helps. |
@odrotbohm I've pushed something, but you'll need to set a |
I can confirm this works as described! Thanks, Phil! 🙇 |
In contrast to the standard HTML backend, our generated documents are missing the directive to include the FontAwesome icon CSS file
There's code that sets the icons to be font-based by default, but also deactivates remote fonts (a line below). If we really want the latter, we'd have to ship FontAwesome CSS and fonts ourselves.
The text was updated successfully, but these errors were encountered: