Repository navigation
[Feature Request] Option root path #2
Description
Activity
While the Google Fonts Proxy could do this, its not a feature that bower supports. Bower is still going to download the font package to its
bower_componentsfolder (or other configured option). This may be better implemented as a build step in your gulp/grunt/npm scripts.I'm talking about the CSS, this would allow people like myself that use Grunt and bower_concat to have the files references for instance in a vender.min.css at
/fonts/instead of the file expecting it to be in the same directory as the css file.I don't see where bower comes into this? This would just affect the CSS file that's added with the fonts?
Hi @supersaiyen :)
Any news about this issue ? For the moment we can not use your package inside a concatenated css file like said @OmgImAlexis. We have to copy the css file and change the url path :/
I have no intentions of adding this feature, however i'd be happy to accept a pull request if you'd like to implement it!
I'd be nice if there was an optional root path that would be used before the font name.
For example, this
https://google-fonts.azurewebsites.net/googleFonts/openSans?family=Open+Sans&root=/fonts/would add this.src: local('Open Sans'), local('OpenSans'), url('/fonts/iXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf') format('truetype');The first slash would be optional, so adding it would make the font path absolute and not adding it would make it relative.