version 3.0.0 ，when i run ：ttf2woff fontello.ttf fontello.woff，console error "arr.readUint16BE is not a function"。version 2.0.0 is ok

(*) Probably, that can be moved to separate library.

Currently we use deflate from Imaya's zlib.js, but it seems that speed can be improved. Note, we need deflate with headers (see zlib spec), not raw deflate. Alternate ports to investigate:

• https://github.com/gildas-lormeau/zip.js/tree/master/WebContent - fastest, needs small change to to support Arrays too (now requires Uint8Array)
• http://www.onicos.com/staff/iz/amuse/javascript/expert/
• https://github.com/dankogai/js-deflate

Keep in mind, that all libs are ports of outdated zlib code. Need refresh.

Hello !!! first forgive my poor english

Windows 7

i find some svg files which is from more then one vectorgraph cant change to woff files.

it`s my test project https://github.com/xxholly32/startNodejs/tree/gh-pages/demo/iconfont-svg-demo

i get svg form icomoon by three pic demo.(icomoon.svg)

and a single svg(single.svg) ande use gulp-iconfont to change ttf files

here is the trouble

E:\ideaworkspace\startNodejs\demo\iconfont-svg-demo\www\fonts>ttf2woff icomoon.t
tf icomoon.woff

C:\Users\xiangxiao3\AppData\Roaming\npm\node_modules\ttf2woff\index.js:168
        throw 'Checksum error in ' + tableEntry.Tag.toString();
        ^
Checksum error in glyf

E:\ideaworkspace\startNodejs\demo\iconfont-svg-demo\www\fonts>ttf2woff single.tt
f single.woff

E:\ideaworkspace\startNodejs\demo\iconfont-svg-demo\www\fonts>

maybe is not a question
i am not learn svg deeply
my purpose is that change icomoon.svg to woff file.

ty !!!

When I use the module locally, it works just fine, but once I deploy to server, this error pops up
The array is the same in both working and crashing environment, and yet, it crashes on server

I may do it if you want.

version 1.2.0 will cause TypeError: undefined is not a function\n at ttf2woff in index.js:198:39. Because Uint8Array does not have slice function

the latest version in the repository fixes this, so can you update package version?

ttf2woff hwxh.ttf hwxh.woff

/usr/local/lib/node_modules/ttf2woff/index.js:160
throw 'Checksum error in ' + tableEntry.Tag;
^
Checksum error in name

how

ttf2woff -f myText.txt fontello.ttf fontello.woff

cat myText.txt
测试

so
fontello.woff only have ‘测试’

Hi, trying to convert the attach font:

$ ttf2woff f.ttf f.woff

/usr/local/lib/node_modules/ttf2woff/index.js:161
        throw 'Checksum error in ' + String.fromCharCode.apply(null, tableEntry.Tag);
        ^
Checksum error in cmap

(had to gzip to attach)

The file can be opened fine with GNOME font viewer on linux.
f.ttf.gz

Our company mirrors npm registry to closed environment using Sonatype Nexus and some tricky replication. Replication requires package folder inside tgz archive to work properly.

Looks like something went wrong during preparation of version 1.3.0: instead of package folder it has fontello-ttf2woff-8e0d929 folder inside — so Nexus can't parse it properly. Could you please update npm package?

Examples:
http://registry.npmjs.org/ttf2woff/-/ttf2woff-1.2.0.tgz — package in archive root,
http://registry.npmjs.org/ttf2woff/-/ttf2woff-1.3.0.tgz — archive with issue

Hi,
does this provide a way to convert a SVG color font to a WOFF/WOFF2 COLR font?

I am converting myRiadPro.ttf to woff file , It is converting but after when i adding this font in html then font not picking by browser . I got a console warning
CSS:
@font-face {
font-family: 'Myriad Pro';
src: url('../fonts/myRiadPro.woff') format('woff');
}
Error on Browser

Failed to decode downloaded font: http://site-url/myriadpro-regular.woff
(index):1 OTS parsing error: wrong font version for PostScript glyph data

woff mimeType is also set in IIS.

can woff convert to ttf ??

The fonts converted by fontfacegen are slightly smaller (~2kb for a 30kb file, which roughly corresponds to ~7%) than generated by ttf2woff. Does the tool perform more optimization or is there an ttf2woff option that could yield smaller files?

Any plan on supporting woff2 format, either here or in a separate project ?

Please support WOFF 2.0.

...or document more prominently if in fact it is already supported.

(see ananthakumaran/webify#8 for context)

In ttf2woff/index.js at line 203 you seem to be unsure whether the padding should be done with zero bytes. Here is the relavant part from the woff spec (only in v1.0, missing in v2.0):

Except for padding with a maximum of three null bytes in places where 4-byte alignment of a table length or block offset is specified

There you have it: Using 0 bytes for the padding is correct, you can remove the question mark in the comment.