New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow compilation without generating font files #241

Open
jaydenseric opened this Issue Oct 19, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@jaydenseric
Copy link

jaydenseric commented Oct 19, 2014

I only want Font Custom to generate the custom templates (Sass partials for using the icon font as a direct Base64 embed in the styles) and not the actual font files.

I attempted the following config in fontcustom.yml, but it seems it is is compulsory to specify an output path for the font files:

font_name: icons
no_hash: true
output:
  _font-icons.scss: ../../../styles
  _icon-font.scss: ../../../styles
templates: [_font-icons.scss, _icon-font.scss]

Results in:

error  Output paths (assigned as a hash) should have a :fonts key. Check your options.

It won't do anything until you add:

  fonts: ../

My temporary workaround is to manually delete them every compile. It would be awesome if Font Custom would only generate files assigned output paths in the config.

For reference, Base64 output is a pretty new Font Custom feature: #131.

jaydenseric added a commit to jaydenseric/Barebones that referenced this issue Jan 3, 2015

Bug fixes for the previous font icon changes. Icon font files are Git…
… ignored because Font Custom forces their creation, even though we are using base64 to embed it directly in the CSS (see FontCustom/fontcustom#241).
@jaydenseric

This comment has been minimized.

Copy link

jaydenseric commented Jan 25, 2015

Related: #213.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment