Open tessus opened 6 years ago
Inside the OTF font file, every glyph has a name.
In FontAwesome 4 these names are highly inconsistant.
Sometimes they are the real icon names with -
replaced by _
like fighter_jet
, sometimes the names are derived from the Unicode codepoint like uniF2A0
(phone-volume
) and some names are derived form the slot number in the font file: _620
is the 620th icon defined in the file.
@zauguin thanks a lot for the answer. I guess in this case I will have to look at the otf file for ForkAwesome and adjust the mapping accordingly.
@tessus I do not think this is really necessary for ForkAwesome, their icon names are much more regular and you can just parse the YAML file to create the necessary macros.
@zauguin good to know. this shouldn't be too hard then. cheers.
I can't figure out where the keys in the pdftex mapping are coming from: e.g.:
"_620" : "percent", #f295
The percent symbol/icon is unicode point f295, but what has _620 to do with that?