Skip to content
This repository has been archived by the owner on May 29, 2020. It is now read-only.

.eot files not generated #367

Open
julkue opened this issue Jul 11, 2017 · 4 comments
Open

.eot files not generated #367

julkue opened this issue Jul 11, 2017 · 4 comments

Comments

@julkue
Copy link

julkue commented Jul 11, 2017

.eot files aren't generated for me. However, there are correctly added to @font-face. This is my configuration:

    webfont: {
      icons: {
        src: './src/icons/*.svg',
        dest: './public/compiled/fonts',
        destCss: './src/components/_common/',
        options: {
          syntax: 'bootstrap',
          engine: 'fontforge',
          stylesheets: ['scss'],
          htmlDemo: false,
          relativeFontPath: '/compiled/fonts/',
          types: ['eot', 'woff2', 'woff', 'ttf', 'svg'],
          order: ['eot', 'woff2', 'woff', 'ttf', 'svg'],
          template: './config/icon-template.config.css'
        }
      }
    },

It doesn't metter if I remove types ad order or not.

@syarul
Copy link

syarul commented Jul 26, 2017

I think this related to #356 issue, which avoid generating eot files. You might want to use previous version if you need the eot

@acuntex
Copy link

acuntex commented Aug 15, 2017

Still not working in 1.7.1.

@syarul
Copy link

syarul commented Aug 16, 2017

the node engine has no issue generating the .eot, might as well use that.

@lqez
Copy link

lqez commented Dec 10, 2018

#356 should be rollbacked. Invoking join method with bytes and non-bytes string causes problem.
TypeError: sequence item 0: expected str instance, bytes found

Since Python 3, bytestring / bytes should be handled differently and Python 2.7 does not care about b notation. Thus, b''.join(...bytes...) was right.

I successfully built eot files with b''.join(...bytes...).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants