It seems something has changed since version 9.0.0 and I assume that I might be incorrect, but I can't continue my unicode name pattern from where it was previously used?
My current folder containing my SVG icons was setup to start from unicode pattern 0xEA01 and their current unicode name stretches from eA01 to eAC2, but if I add any new icons to that folder and run my Gulp script again, the svgicons2svgfont script crashes and complains that the unicode name is already in use?
In a previous version of icon-font, you could add new icons to you library with already existing icons and the new icons would get a unicode name based on the largest name pattern in the folder of icons?
In that way, you could keep the old CSS mapping, even if the font was updated with new icons.
Not sure when that stop working or if anything is changed in the way you need to write required attributes for the process, so please update me.
It seems something has changed since version 9.0.0 and I assume that I might be incorrect, but I can't continue my unicode name pattern from where it was previously used?
My current folder containing my SVG icons was setup to start from unicode pattern 0xEA01 and their current unicode name stretches from eA01 to eAC2, but if I add any new icons to that folder and run my Gulp script again, the svgicons2svgfont script crashes and complains that the unicode name is already in use?
In a previous version of icon-font, you could add new icons to you library with already existing icons and the new icons would get a unicode name based on the largest name pattern in the folder of icons?
In that way, you could keep the old CSS mapping, even if the font was updated with new icons.
Not sure when that stop working or if anything is changed in the way you need to write required attributes for the process, so please update me.