search

FortAwesome / Font-Awesome

The iconic SVG, font, and CSS toolkit
https://fontawesome.com
Other
73.64k stars 12.19k forks source link

Missing Icons in Microsoft Word (FA >= 5.7.0) #14614

Closed SAID-developer closed 4 years ago

SAID-developer commented 5 years ago

Describe the problem

I updated my version of FontAwesome last week and now I am missing several icons in the symbol window in Microsoft Word. These icons were there previously and working without any issue. The screenshot shows what I am seeing and recently used icons from the sets that are no longer there. I downloaded the most recent version again and reinstalled and nothing changed. I've also rebooted the computer completely, opened and closed Word and nothing fixes it. This issue is across everyone in my office, not just my computer.

image

What did you expect?

I expected to see the full icon set as I always have.

What version and implementation are you using?

Version: The issue started with 5.7.0 and is still there with 5.7.1 Microsoft Word Version 1901, Office 365 Business

Reproducible test case

Bug report checklist

SAID-developer commented 5 years ago

Just a note, I've also tried entering the character code and that doesn't work either. It brings up the wrong character, selecting one from the set that is showing rather the one from the full set that it should show.

tagliala commented 5 years ago

Ok, I'm able to replicate this even on Office 2007.

Apparently, only microsoft products are affected by this issue

I'm using the .otf file 5.7.1

image

This is what happens when I type unicorn on Word: image

Wordpad has the same issue, too

Photoshop and other graphics suite looks fine

SAID-developer commented 5 years ago

Hi, just checking if there are any thoughts about this issue? Thanks!

tagliala commented 5 years ago

I've forgot to assign @robmadole

robmadole commented 5 years ago

@SAID-developer I can confirm that there is an issue as well but as of now do not have a fix for it. We'll keep working on this one.

SAID-developer commented 5 years ago

@robmadole Thank you! I appreciate that. I built out a series of ux documents using the icons and it would be ideal to have a fix as opposed to redoing them.

tagliala commented 5 years ago

I've just checked 5.7.2 and the problem is still there

I think that a proper description of the issue is that ligatures stopped working on 5.7+ on certain applications

image

Gehanii commented 5 years ago

Tried using v5.8.1 and the issue persists. :(

loesje001 commented 5 years ago

I have the same problem since I updated to V5.8.1, also tried V5.8.2 also same problems. Only when I installed the .ttf V5.6.3 en then the .otf V5.6.3 I got that one working, newer versions are all missing icons. I hope this will get fixed soon!

rdhar commented 5 years ago

Just to add on to this, I experience the same issue of missing/incorrect glyphs when using the Desktop OTFs. In my case, when I copy-pasted the unicode glyph for Diploma (f5ea), it would actually display Paste (f0ea) instead.

Following on from @loesje001's message, I replaced the Desktop OTFs with Web TTFs instead and that appears to resolve the issue immediately. However, upon saving the document with MS Word's built-in "Export PDF" option, the aforementioned Diploma icon is rendered as white space, despite appearing correctly within Word itself! Curiously, the same is true for the Graduation-cap glyph (f19d) but not for Briefcase (f0b1), which is rendered just fine in MS Word and as a PDF.

Instead of the native "Export PDF" option, I just tried saving it through Adobe Acrobat DC instead since I have that installed as part of Adobe CC. Wouldn't you know it, every single glyph is rendered exactly as intended, just as they appear in MS Word.

It almost seems as if only Unicode prefixed with 'f0' is working as expected while others are unpredictable. —@rdhar, hot-take

System: Windows 10 Pro, v1903 Office: Microsoft Word 2019, v1905 FA5: Pro, v5.9.0

tagliala commented 5 years ago

@rdhar could you please confirm that 5.6.3 works properly?

qkflies commented 5 years ago

While I don't use the Pro version, I've also been running into this issue as described by rdhar with newer versions of FA. I've been sticking with v5.6.3, which does appear to work as intended.

System: Windows 10 Pro, v1803 Office: Office 365 / Microsoft Word v1905 (Build 11629.20246 Click to Run)

avinoamsn commented 5 years ago

+1 for the Adobe Acrobat workaround

rdhar commented 5 years ago

@rdhar could you please confirm that 5.6.3 works properly?

@tagliala Here are my results with FA5 Pro v5.6.3.

Format Processor Status
OTF Word Fine
OTF Word Export PDF Fine
TTF Word Fine
TTF Word Export PDF Missing*

*Of my sample doc with only 4 icons, only Briefcase (f0b1) appeared as expected in both MS Word as well as its in-built PDF export. The following characters were missing:

The export via Adobe Acrobat DC remains as a viable workaround throughout. It really seems like the issue is isolated to MS Office. I just tried out LibreOffice's in-built PDF export and that rendered the TTF icons with no problems whatsoever, neither in Writer nor in the PDF.

Hope this helps.

Gehanii commented 5 years ago

I was able to use Desktop Pro 5.10.0-11 (or whatever that versioning is supposed to be) for 1 day in MS Word before glyphs started to no longer render. I was able to continue my work in InDesign ES4 for another 2 days beyond that before that too stopped rendering glyphs. The truly bizarre thing is that my XDF file is still able to access icons that are no longer rendering if I am inserting the character into a field via JavaScript. The characters were copied to the standard clipboard from MS Word & pasted into the XML edit-stream of the XDF file.

I made a composite image from this document with both 5.6.3 & 5.10.0. Maybe some of the differences in the character matching might help? The char code column is the character code value Word displays in its Insert Symbol dialog window when selecting the said character.

I also find it interesting that with >5.6.3, Word displays a secondary box next to the glyphs (as well as at the end of each table row & paragraph.) These are NOT the hidden text characters that Word uses; they still appear if hidden text is displayed.

563 vs 5100

Another observation is that the Windows 10 font view/installation window shows the "th" ligature in the font-view for 5.6.3 but does not for subsequent (and "broken") versions.

Thank you for your attention to this issue.

samayo commented 5 years ago

Same issue. Last year it was working just fine, but I guess someone decided to break it :/

rdhar commented 5 years ago

Same issue. Last year it was working just fine, but I guess someone decided to break it :/

I think it's a bit unfair to describe it as someone deciding to break it. Not least because it makes absolutely no sense for the maintainers to intentionally add regression issues to their product. Additionally, as mentioned just a couple of posts above, viable workarounds currently exist in the form of:

ischang commented 5 years ago

Unfortunately, these workarounds aren't working for me -- using Microsoft Word 2019 (version 16.29) on MacOS Sierra. I've tried Desktop FA <=v.5.6.3 (tried using 5.6.3 and using 5.6.0, etc). This is for both FA Brands and FA Regular/Solid. I tried the recent Web FA (latest and older) as well.

For example, from brands, I'm missing some of the Github icons (f09b, f092, etc) and all the LinkedIn ones. From regular FA, I've noticed I'm missing the globe icon, along with envelope.

Gehanii commented 5 years ago

Any further word on this? 5.11 is broken immediately on installation.

pixeokoen commented 5 years ago

I used FontAwesome in Microsoft Word, in Photoshop and in websites. But the Word issues made me switch to a different icon font: https://materialdesignicons.com/ (they also have a very useful Chrome plugin for searching icons)

If it were up to me, I'd use FontAwesome, but I have a very strong feeling they just don't care about this ...

robmadole commented 5 years ago

Just a quick update on this issue. We've worked on this issue a couple of times an have not been able to identify the cause. Since it continues to be a problem for folks we'll try again to take a look. However, since Word appears to be the issue (it works fine in other programs) we consider this to be an issue with Word itself. We'll try to fix it if we can but has anyone filed a bug with Microsoft? Or has anyone ran across a thread that might be related to this?

pixeokoen commented 5 years ago

Just a quick update on this issue. We've worked on this issue a couple of times an have not been able to identify the cause. Since it continues to be a problem for folks we'll try again to take a look. However, since Word appears to be the issue (it works fine in other programs) we consider this to be an issue with Word itself. We'll try to fix it if we can but has anyone filed a bug with Microsoft? Or has anyone ran across a thread that might be related to this?

Thank you for the response! I have not filed the issue with Microsoft. The main reason for this is that earlier versions of FontAwesome, and other icon fonts (like the one I suggested) do work fine. I'm not sure I want to be in the middle of a ping-pong match between FontAwesome and Microsoft. I'm a FontAwesome paying customer by the way. ;-)

qkflies commented 5 years ago

I've not seen anything on Microsoft's side, but I do want to mention that this appears to impact all MS Office products (Word, Excel, PowerPoint, etc.).

I'm using the latest stable version of Office 365 for consumers (I'll update with version numbers when I get to my desktop).

robmadole commented 5 years ago

I just raised this up with Dave and Travis (CEO and CTO) to see if this needs to be prioritized. @pixeokoen I understand the ping-pong match and you have a better chance of us fixing it than of Microsoft paying attention to it. This is just a difficult one to solve so any feedback we could get from them (a clue, a hint, a trail to follow) might be the thing that breaks the case.

tagliala commented 5 years ago

@robmadole since this has been introduced from 5.6.3 to 5.7.0, and we fixed something about the font name (it was wrong before), we can try the following to check if it works with:

This link may be useful:

Anyway, this is a time consuming task. At the moment I cannot help on this :\

robmadole commented 4 years ago

OK, folks. We've got this on the work list for 5.12.0. I'm going to give it another go. No guarantees that I can fix it but we're going to try.

pixeokoen commented 4 years ago

OK, folks. We've got this on the work list for 5.12.0. I'm going to give it another go. No guarantees that I can fix it but we're going to try.

Any ETA on 5.12.0 or is that wishful thinking? :-)

robmadole commented 4 years ago

5.12.0 should go out within the next few weeks. Again, no guarantee that we will be able to fix this issue with that release but it's our goal.

robmadole commented 4 years ago

Alrighty. I think I may have fixed this sucker. Anyone who has the time can you give this a try and let me know?

Font Awesome 5.12.0-1 OTF.zip

qkflies commented 4 years ago

The issue is resolved in my documents, and scrolling through the Insert Symbols dialog, there are no longer any missing icons.

Thanks for your work on the fix, @robmadole!

pixeokoen commented 4 years ago

There is improvement, and I would say it's fixed although 1 thing seems off ...

I attached some screenshots.

fa-screen-regular fa-screen-brands fa-screen-solid

pixeokoen commented 4 years ago

I'm will test this on some other computers tomorrow, when I'm at the office. 😉

robmadole commented 4 years ago

@pixeokoen sweet! thanks for testing and the screenshots! So this is the Free version of Font Awesome so the Regular style is very limited (basically just the icons that make it backward-compatible with version 4). So I think that's correct.

@qkflies thank you for testing!

With two successful results I'm going to tentatively call this one fixed. It was a one line change in the code that took a LONG time to figure out!

pixeokoen commented 4 years ago

@pixeokoen sweet! thanks for testing and the screenshots! So this is the Free version of Font Awesome so the Regular style is very limited (basically just the icons that make it backward-compatible with version 4). So I think that's correct.

Oh, okay, cool. I'm a pro user so wasn't aware. 😎

With two successful results I'm going to tentatively call this one fixed. It was a one line change in the code that took a LONG time to figure out!

Aaah, 1-line-bugs. Them funny ones ... I guess it's fixed indeed! Now I can finally use 1 icon set again for docs and designs! Thank you for all the efforts!

robmadole commented 4 years ago

giphy

Excellent. This will be going out in 5.12.0 then!

rdhar commented 4 years ago

It was a one line change in the code that took a LONG time to figure out!

Go on then, spill!

emottet commented 4 years ago

Hi, I've done some tests too. For me, it works fine on Word through the Insert Symbols dialog. word

But it doesn't work on Power Point throught the Insert Symbols dialog. power-point

Could it just be a cache issue ? For those that have been testing successfully, have you done your tests in Power Point too?

robmadole commented 4 years ago

@rdhar It involved adding more sets to the OS/2 codepages which allow some of the applications on Windows (including Character Map, Word, Wordpad) to see the OpenType font as supporting Unicode.

font.os2_codepages = (-1, -1)

☝️ that was it.

robmadole commented 4 years ago

@emottet I haven't tried PowerPoint yet but I will add it to the list. Thank you for testing!

qkflies commented 4 years ago

@emottet I'm able to replicate what you're seeing, unfortunately.

image image image

pixeokoen commented 4 years ago

@emottet I haven't tried PowerPoint yet but I will add it to the list. Thank you for testing!

So Word is fixed. Even if Powerpoint is not working yet, will the fix be released to the Pro version anytime soon?

robmadole commented 4 years ago

Yes, this will be going out in 5.12.0. We don't have an exact schedule for release but it should be in the next 2 weeks.

robmadole commented 4 years ago

Ok everyone. We have released 5.12.0 and I think I was able to fix the PowerPoint issue as well. Please try the final release out and let me know your results!

pixeokoen commented 4 years ago

Ok everyone. We have released 5.12.0 and I think I was able to fix the PowerPoint issue as well. Please try the final release out and let me know your results!

I've checked FA Pro in Word. Looks great. If anyone can verify Powerpoint, we're all good!

Gehanii commented 4 years ago

Of course, it'd be me with another problem. :(

Starting at char point F900, Word's insert symbol dialog gives a Unicode name of "CJK Compatability Ideograph-####" where the #### matches the char point number. The glyphs render fine in the dialog window, but do not render when inserted in the actual document. I've rebooted once already; I'm going to nuke the fonts outright, reboot, reinstall & see where that gets me. My sneaking suspicion, however, is that it'll still be an issue.

I really hate to be the bearer of bad news after all the work that's gone into trying to fix this issue. :( :( :(

.oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. Geoffrey B. Webb, Limbo Games Press - "A double negative is a no-no." .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo.

On Wed, Dec 11, 2019 at 2:12 PM pixeokoen notifications@github.com wrote:

Ok everyone. We have released 5.12.0 and I think I was able to fix the PowerPoint issue as well. Please try the final release out and let me know your results!

I've checked FA Pro in Word. Looks great. If anyone can verify Powerpoint, we're all good!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FortAwesome/Font-Awesome/issues/14614?email_source=notifications&email_token=AJRWTC3LEXJJFAC5DN2XHTTQYFCT5A5CNFSM4GUXJWH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGUNLKY#issuecomment-564712875, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRWTC5AV543ZFLGDQ7V2UTQYFCT5ANCNFSM4GUXJWHQ .

Gehanii commented 4 years ago

Or now I can't uninstall the fonts. :( Even with elevated rights. :(

.oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. Geoffrey B. Webb, Limbo Games Press - "A double negative is a no-no." .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo.

On Wed, Dec 11, 2019 at 4:25 PM Geoff Webb iphoig@gmail.com wrote:

Of course, it'd be me with another problem. :(

Starting at char point F900, Word's insert symbol dialog gives a Unicode name of "CJK Compatability Ideograph-####" where the #### matches the char point number. The glyphs render fine in the dialog window, but do not render when inserted in the actual document. I've rebooted once already; I'm going to nuke the fonts outright, reboot, reinstall & see where that gets me. My sneaking suspicion, however, is that it'll still be an issue.

I really hate to be the bearer of bad news after all the work that's gone into trying to fix this issue. :( :( :(

.oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. Geoffrey B. Webb, Limbo Games Press - "A double negative is a no-no." .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo.

On Wed, Dec 11, 2019 at 2:12 PM pixeokoen notifications@github.com wrote:

Ok everyone. We have released 5.12.0 and I think I was able to fix the PowerPoint issue as well. Please try the final release out and let me know your results!

I've checked FA Pro in Word. Looks great. If anyone can verify Powerpoint, we're all good!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FortAwesome/Font-Awesome/issues/14614?email_source=notifications&email_token=AJRWTC3LEXJJFAC5DN2XHTTQYFCT5A5CNFSM4GUXJWH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGUNLKY#issuecomment-564712875, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRWTC5AV543ZFLGDQ7V2UTQYFCT5ANCNFSM4GUXJWHQ .

Gehanii commented 4 years ago

The glyphs that won't appear in the Word document itself are being set to the Malgun Gothic font-face & crazily is not able to be changed in the UI. :(

.oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. Geoffrey B. Webb, Limbo Games Press - "A double negative is a no-no." .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo.

On Wed, Dec 11, 2019 at 4:34 PM Geoff Webb iphoig@gmail.com wrote:

Or now I can't uninstall the fonts. :( Even with elevated rights. :(

.oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. Geoffrey B. Webb, Limbo Games Press - "A double negative is a no-no." .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo.

On Wed, Dec 11, 2019 at 4:25 PM Geoff Webb iphoig@gmail.com wrote:

Of course, it'd be me with another problem. :(

Starting at char point F900, Word's insert symbol dialog gives a Unicode name of "CJK Compatability Ideograph-####" where the #### matches the char point number. The glyphs render fine in the dialog window, but do not render when inserted in the actual document. I've rebooted once already; I'm going to nuke the fonts outright, reboot, reinstall & see where that gets me. My sneaking suspicion, however, is that it'll still be an issue.

I really hate to be the bearer of bad news after all the work that's gone into trying to fix this issue. :( :( :(

.oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. Geoffrey B. Webb, Limbo Games Press - "A double negative is a no-no." .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo.

On Wed, Dec 11, 2019 at 2:12 PM pixeokoen notifications@github.com wrote:

Ok everyone. We have released 5.12.0 and I think I was able to fix the PowerPoint issue as well. Please try the final release out and let me know your results!

I've checked FA Pro in Word. Looks great. If anyone can verify Powerpoint, we're all good!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/FortAwesome/Font-Awesome/issues/14614?email_source=notifications&email_token=AJRWTC3LEXJJFAC5DN2XHTTQYFCT5A5CNFSM4GUXJWH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGUNLKY#issuecomment-564712875, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRWTC5AV543ZFLGDQ7V2UTQYFCT5ANCNFSM4GUXJWHQ .

robmadole commented 4 years ago

Ok @Gehanii. Let's get a few more people trying. But that sounds like some deeper Word-related issue to me.

Gehanii commented 4 years ago

I agree. I just tried using those same glyphs in Excel: the same dialog content is used in both applications. Weirdly, the cell as rendered shows the FA glyphs just fine, but the cell content review shows the CJK glyphs. "Thank you, Word..."

I'll try some other applications & see where that gets me.

.oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. Geoffrey B. Webb, Limbo Games Press - "A double negative is a no-no." .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo. .oOo.

On Wed, Dec 11, 2019 at 4:59 PM Rob Madole notifications@github.com wrote:

Ok @Gehanii https://github.com/Gehanii. Let's get a few more people trying. But that sounds like some deeper Word-related issue to me.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/FortAwesome/Font-Awesome/issues/14614?email_source=notifications&email_token=AJRWTC652WY3NL46L2CQSWTQYFWEFA5CNFSM4GUXJWH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGU3UUA#issuecomment-564771408, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRWTCZBT3AHZELROLEYRUDQYFWEFANCNFSM4GUXJWHQ .

emottet commented 4 years ago

Hello @robmadole You made my day! It's working just fine on Power Point! Thank you so much for your time!