-
Notifications
You must be signed in to change notification settings - Fork 12.2k
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
Wrong icon when using FA Pro OTF with Microsoft Word 365 #15181
Comments
let's try the following Use ligatures
Rollback to Font Awesome 5.6.3Font Awesome 5.7+ has some issues with some softwares and ligatures. Please try again with version 5.6.3 and report results Ref: #14614 |
Hello, Iam back at work, could you please navigate me, where I can get version 5.6.3? |
Here: https://github.com/FortAwesome/Font-Awesome-Pro/releases Direct link: https://github.com/FortAwesome/Font-Awesome-Pro/releases/download/5.6.3/fontawesome-pro-5.6.3-desktop.zip If you don't have access to the above repository, please make sure you have linked your Font Awesome Account to your GitHub account at https://fontawesome.com/account#linked-accounts |
I see that account is linked to my colleague that is out of office now. I have to wait... |
@tagliala: I can confirm version 5.6.3 is working fine for us. You can close the issue. |
@JanKudera thanks. This bug still does not have a fix, but let's continue on #14614 |
Hello, thank you for comprehensive answer. Let met provide you with additional information.
I am at windows 10, using microsoft word 365, installed only one font "font awesome 5 pro-solid-900 otf." Lets say I wish insert your icon: ellipsis-v. with unicode f1c3. I type to application in regular font (e.g. calibri). I see "f881". With selected string I press alt-x and switch to awesome font. The result is a Flask with different unicode (f0c3). With previously mentioned codes above I see a) blank square b) different icon, not matching with your guide. Am I doing something wrong, or is it a bug with font?
Originally posted by @JanKudera in #13433 (comment)
The text was updated successfully, but these errors were encountered: