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

FontAwesome.ttf #28

Open
Luckygirlllll opened this issue Mar 1, 2018 · 6 comments
Open

FontAwesome.ttf #28

Luckygirlllll opened this issue Mar 1, 2018 · 6 comments

Comments

@Luckygirlllll
Copy link

Where is the FontAwesome.ttf? Without adding this file to the project library wouldn't work?

@grobmeier
Copy link
Contributor

Download it manually - this lib won't do it for you.

@keung7252
Copy link

Where is the FontAwesome.ttf? Without adding this file to the project library wouldn't work?

@leandrosimoes
Copy link
Collaborator

Where is the FontAwesome.ttf? Without adding this file to the project library wouldn't work?

The FontAwesome.ttf is no longer used, because fontawesome does not have this file anymore. Now the fontawesome use separated files named like this:

fa-brands-400.ttf
fa-regular-400.ttf
fa-solid-900.ttf

@mdere-unbound
Copy link

mdere-unbound commented Feb 28, 2019

so for IOS - do we need to rename it ? I am getting Unrecognized font family 'FontAwesome5FreeSolid'

@bmcn99
Copy link

bmcn99 commented Mar 7, 2019

Where is the FontAwesome.ttf? Without adding this file to the project library wouldn't work?

The FontAwesome.ttf is no longer used, because fontawesome does not have this file anymore. Now the fontawesome use separated files named like this:

fa-brands-400.ttf
fa-regular-400.ttf
fa-solid-900.ttf

I've downloaded those files, put them in my fonts folder and run react-native link again but am still getting the square box with a cross instead of the icon. Do you know if there's anything else undocumented that needs to be done to get this going?

@forjoyilive
Copy link

I had to modify FontAwesomeIcons.js and change the font names, which weren't matching the actual names of the font files that I saw when opening the fonts in FontBook.

e.g. instead of "FontAwesome5FreeSolid" I changed it to "Font Awesome 5 Pro" -- or "Font Awesome 5 Free" if I were using the free set.

There might be a better solution, but I'm not sure what it is?

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

7 participants