Materialdesign: Glyphs "apps" and "truck" have issues

Created on 2 Aug 2018  路  7Comments  路  Source: Templarian/MaterialDesign

The glyphs "apps" and "truck" seem to have issues, I can't convert them with grunt-webfont/fontforge to a ttf, fontforge just hangs.

Upon searching for the reason I found out that the SVGs have contours that aren't closed.
auswahl_232
auswahl_233

Closing them in Inkscape fixed that for me.
I'm not quite sure if that is the correct approach, but if it is: do you want a pull request for those files?

Question Webfont

Most helpful comment

Guys, I think I'm going to update @mdi/util with a helper function to close paths. /cc @macx

Reopening this issue so we can track the progress. Eventually I want to add a NPM package called @mdi/font-custom that handles the entire flow of creating a custom webfont that will make use of these updates.

All 7 comments

Closing as not an issue. This is part of our SVG optimization step to cut down on point count.

I use the grunt-webfont with node without the fontforge dependency. Might look into that instead.

You might be able to automate this with a relatively easy regex. Basically we move to (M) instead of closing path points. I think adding Z before each of the M might close the paths?

Not 100% sure though.

That should close each of the paths.

Guys, I think I'm going to update @mdi/util with a helper function to close paths. /cc @macx

Reopening this issue so we can track the progress. Eventually I want to add a NPM package called @mdi/font-custom that handles the entire flow of creating a custom webfont that will make use of these updates.

@Templarian Wohow, great news. Keep on updating.

https://github.com/Templarian/MaterialDesign-Webfont-Build

Lets try and work on this together. Submit Issues and PR's above. I've added the basics to generate a directory called icons that contains "fixed" paths.

Basically run npm run buildIcons && npm run _your script_ in a new command. Looking for PRs. I'll help making sure the SVG data is compatible. The current buildIcons command should handle most icons, but there may be edge cases.

This is not something we are interested in doing. Part of the optimization process is to remove unneeded points and paths. This is even more important now as we cross 4000 unique icons. Thank you for your suggestion.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

emanf picture emanf  路  3Comments

Templarian picture Templarian  路  3Comments

jonnyborg picture jonnyborg  路  3Comments

EdricChan03 picture EdricChan03  路  3Comments

adambiggs picture adambiggs  路  3Comments