Simon Cozens
Simon Cozens
I wrote the demos. :-) I haven't been able to compile a WASM version of the WASM runtime, and so I haven't worked out how best to implement this.
I don't think this is possible, sadly. We would need a WASM-compiled harfbuzz containing its own internal WASM machine.
I'm not sure but check what LaTeX does, because that uses default values to plain TeX and I may well have copied that.
> (on things you might have checked on your own, right?) Sure, if I wanted to be the one doing the work, but I was being asked a question here....
Sorry, this dropped off my radar but I think I encountered it myself at some point and fixed it.
Also `googlefonts/metadata/undeclared_fonts` is redundant with `googlefonts/metadata/filenames`, since both check whether there are files present which are unlisted in the METADATA.pb.
There's precedent for using alternative implementations of an operation: see the (now badly-named) `hbsubset` operation which can be switched between `hb-subset` and `pyftsubset`. But that's a bit easier to handle...
See notes on above PR.
I'm not clear about this. I mean, you're probably right, but there's nothing actually in the UFO spec which says this attribute is required. (The UFO spec is a bit...
> hex is a required attribute in the UFO spec. No, it isn't, as the spec is currently written. > hex does not have a defined default, nor is it...