-
1. Re: FontAwesome appears as question marks in FrameMaker 12. I installed the font in the Windows/Fonts folder. Do I need to do something else to get it to work in FM?
Error7103 Nov 11, 2014 10:14 AM (in response to Stephanie.Marris)In FM, what appears in File > Utilities > Character Palette
for FontAwesome?
-
3. Re: FontAwesome appears as question marks in FrameMaker 12. I installed the font in the Windows/Fonts folder. Do I need to do something else to get it to work in FM?
Error7103 Nov 11, 2014 11:27 AM (in response to Stephanie.Marris)Well, if it's any consolation, it does the ????? thing (complete with bad font metrics for the question marks) in FM9, too.
I'm tempted to blame the font, but it could also be that FM is confused by things that shouldn't be where they are. You'll notice that some of the glyphs aren't given descriptive names in Character Palette.
For example, code points U+0000 through U+001F. Those are supposed to be the C0 Controls in Unicode, and not displayable glyphs.
http://www.unicode.org/charts/PDF/U0000.pdfDitto for U+0080 through U+009F, which are the C1 Controls:
http://www.unicode.org/charts/PDF/U0080.pdfThe glyphs at these code points should either be in standard Unicode positions (where the glyph is covered by Unicode, such as that left pointing triangle at U+0011, which might have been the same thing as defined by Unicode at U+25C0 or 23F4) or in some Private Use area.
Ask for your money back .
-
4. Re: FontAwesome appears as question marks in FrameMaker 12. I installed the font in the Windows/Fonts folder. Do I need to do something else to get it to work in FM?
Stephanie.Marris Nov 11, 2014 11:40 AM (in response to Error7103)Thanks for your reply, Error7103! I appreciate your time.
It appears this way in FM11, too
I hope this can be resolved. This is the font our UX team wants us to use.
-
5. Re: FontAwesome appears as question marks in FrameMaker 12. I installed the font in the Windows/Fonts folder. Do I need to do something else to get it to work in FM?
Error7103 Nov 11, 2014 12:15 PM (in response to Stephanie.Marris)> It appears this way in FM11, too
It seems to work in LibreOffice Writer, but in MS WordPad it has defective font metrics, and the very name of the font is blank in the font menu.
In Win7 Character Map, the characters illegally occupying the C0 Controls range aren't shown at all. Some of the C1s are shown, but most are blank.
FM's "?" behavior, by the way, is what in other apps is a square box. You can find lots of discussion about FontAwesome and square boxes.
Have your team test this typeface in a variety of apps, operating systems and browsers. Be sure to have them try some of the icons in the Unicode C0 and C1 Controls areas.
Entirely apart from what appear to be at least two other problems with this font, putting glyphs in C0/C1 is a big mistake in my view, and one that may prove difficult to undo (as in: moving those glyphs elsewhere in a later release), if people are adopting and deploying this font where it seems to work.
This is not FontAwesome. It's FontFail.



