Christoph Päper

I don’t speak ~~Parseltongue~~ Python.

`font-feature-settings` is a low-level property. It’s there for authors to shoot themselves in the foot with. Many do. Let them. For higher-level properties I would agree.

So what would be less complex and not available are: - number of ancestor levels (`:root>*>`…, mentioned in #4940) - number of attributes - number of attributes of a specific...

If this feature was about _image creation_, it should not be limited to a single layer, i.e. it would require nesting or additive sources. ~~~~ css @image --composite { @layer...

Does this issue implicitly include Google’s standardized alternative `CBDT`/`CBLC` to Apple’s proprietary `SBIX`?

Meanwhile, SBIX has been standardized as well. (Opentype format version 1.8, 2016.)

`.fea` files maybe, which can be reused if glyph names are the same.

Since this would need only a [very limited subset of Adobe’s `.fea` syntax](https://www.adobe.com/devnet/opentype/afdko/topic_feature_file_syntax.html#5.d) (which Fontforge also supports), it could probably be done in the YAML as well, so the tool...

The place to fix this seems to be [`codepoint_from_filepath()` in util.py](https://github.com/eosrei/scfbuild/blob/master/scfbuild/util.py#L23). It currently only supports file names that are either a single hexadecimal code point or a string of multiple...

I see there are two branches `windows10` and `windows10_simple` from late 2015 which actually have the files. Why did neither make it into the master branch yet?