You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I recognized is, that if I switch between the old and the new one. It would be great if we find a way that each icon has a fixed unicode number. Otherwise the users will see another icon when they update to a new version. I think that´s impossible with fontello. I will try with fontforge. Maybe there is a solution for that. And I think it´s cool if the filename is versioned like the icon realease 1.1 and so on.
The text was updated successfully, but these errors were encountered:
Ok, I understood the problem: on Fontello I've re-upload all icons with the computer's alphabetical order.
This generates the remapping of unicode membership...
Will solve simply adding icons instead of maintains the order.
Also I think that may join (major) icons with congenial character, for example:
Character
Icon
Preview
y or a or v
accept
x
cancel
c
copy
C
cut
e
controls eject
<
controls play back
>
controls play
«
controls rewind
»
controls fast forward
...and so on...
* Please note that previews are generated directly by the Generator ;)
No problem for font release in filename and in metadata.
I think it´s not possible to give each icon a logic key. Now it´s in the unicode area "Private Use Area". I think for the font it´s better to append the new icons at the end of the old one´s like you suggested before "Will solve simply adding icons instead of maintains the order." But I don´t know if that´s possible.
What I recognized is, that if I switch between the old and the new one. It would be great if we find a way that each icon has a fixed unicode number. Otherwise the users will see another icon when they update to a new version. I think that´s impossible with fontello. I will try with fontforge. Maybe there is a solution for that. And I think it´s cool if the filename is versioned like the icon realease 1.1 and so on.
The text was updated successfully, but these errors were encountered: