tagliala
commented
10 years ago I don't know why fs are skipped, but there is an issue I remember: https://github.com/FortAwesome/Font-Awesome/blob/130486b09da19bd7b5ea922643dd1de9f445416d/less/font-awesome.less#L303
I just want to report a small issue I found in FontAwesome: it seems there are gaps in the Unicode character ranges assigned to the FontAwesome glyphs. Example:
.fa-search-plus:before { content: "\f00e"; } .fa-search-minus:before { content: "\f010";
Where is 'foof'? It doesn't exist, so this is such a gap, and there a few of them. When is this an issue? I found it to be an issue when extending FontAwesome with your own additional glyphs. If you use a solution like "Icomoon" to do that, you can set a start char position there, and all icons will get sequential numbering. This way you can keep using the FontAwesome official CSS, whilst also adding your own glyphs. This fantasy does not work, however, since Icomoon correctly numbers sequentially, whilst FontAwesome does not (it has the gaps). The result is a lot of manual editing and reshifting.
I realize it's a small issue probably not affecting many, but for completeness I wanted to share my experience.