Before learning that the first 4 characters spaces have to be empty when creating new symbols, I filled them with symbols that I created. I then removed them, put a rectangle in the first .notdef and now I can’t see any of my symbols. Any insight as to why this is happening?
I am not experienced in building Symbol fonts so the following may not be that helpful.
I have had problems dealing with Symbol fonts when the platforms/ mapping/ naming is messed. I haven’t had a problem where eventually I couldn’t shoot enough “alternatives” at it to get it to work. Often it will just get tired and repair itself!! Check a known-working symbol font for clues. (That’s not much help!)
The first 4 glyphs are not empty (4 tends to be a space) so check other fonts you own to see what is included. You could revert to the original of this font also.
It is possible that’s not why “now I can’t see any of my symbols”. There are so many places where you may not see them:
–I assume they show on the main FCP window – if not, sorry they’re gone.
–The chars may not be mapped correctly. What steps did you use to move your symbols: added a glyph, cut/paste the character, and name it (“Properties”)? Without a character being assigned a definition it can’t be referenced or seen.
–If the symbols don’t show on Font/Test (F5) that’s possible that the characters are not included in the sample text. At one level, you can type the symbol to have it show there. (Read the manual for how to do specials).
– If they are properly named, you could create a test font where you copy and paste your curves over some other working character, the “dollar sign” perhaps. Then it would be shown in place of that character. That would show the mapping, or key strokes, as the problem and not your curves.
If you installed the font in Windows Fonts and can’t see it in an application it’s either you or the application! I think you have to be more specific if that’s where your problem lies.
Good luck.
Thanks for the info.
It turns out that problem was my mapping. Under format/mapping I changed some of the values that the symbols were mapped to and this fixed the problem. The best way to find a correct mapping is to look at a windows font.
Hope this helps anyone who needs it!!