|
Post by voleman on Mar 3, 2012 16:02:59 GMT -5
I have a project for which I would like to be able to print various symbols into cells in Excel. I was thinking the easiest way would be to edit a font like WebDings. I downloaded the free version of Type lite, but am having trouble doing that. When I try to open WebDings, I get a screen that shows characters in the font, but the font itself doesn't seem to be available for editing. The list of available fonts in the floating window to the right don't include WebDings. The manual doesn't seem to explain how to edit existing fonts. What am I doing wrong?
|
|
|
Post by Allan Murray on Mar 3, 2012 22:24:32 GMT -5
Webdings are a special type of font called a 'symbol font'. The characters in a symbol font are mapped to unicode F000 to F0FF.
With the mapping window set to 'CodePages': instead of selecting 1252 latin 1, select Symbol Character Set, then scroll down to find the characters.
When you save the font, make sure that the active check box is ticked for Symbol Character set.
|
|
|
Post by demusss on Mar 13, 2012 9:35:45 GMT -5
I'm trying to do something similar as in creating my own set of symbols in a font.
I create the glyph and map it to a character within the 'Symbol Character Set', tick the active box and save the font as a ttf.
When I reload the font the glyph is no longer mapped to the character!
If I do not tick the active box then save the font and reload the glyph is still mapped.
According to the user manual the active box needs to be ticked to indicate that the range is being used.
Why do the glyphs dissapear? thanks
|
|
|
Post by Allan Murray on Mar 16, 2012 4:31:33 GMT -5
You have identified an issue when creating (new) symbol fonts. I have now rectified this and you can download an updated version (3.1.016).
You need to be careful when dealing with symbol fonts - they can be quirky. I recommend that you check the following when creating a new, or editing an old symbol font:
- make sure that Symbol Character Set is active (CodePages) - make sure that all other CodePages are NOT active (eg 1252 Latin 1) - make sure that E000 Private Use Area (Unicode Scripts) is active - when creating a new font, unmap glyph 3 (space) from unicode 0020, and map it to unicode F020 (important).
In the next release I will be implementing some automatic checks to make dealing with symbol fonts easier.
|
|
|
Post by Allan Murray on Apr 20, 2012 2:54:27 GMT -5
The above operations are now automatic for symbol fonts in the newly released Type 3.2. You will still need to map space to F020 when creating a new symbol font though.
|
|