Rod

> exposed a bug For us too I think!

Tested on todays picosvg and latest noto-emoji; offenders list has changed a bit. ``` # create /tmp/try_pico.sh: #!/bin/bash picosvg $1 > /dev/null 2>&1 || { echo "FAIL $1"; exit 1;...

The Noto Svg files with image in them are fixed in https://github.com/googlefonts/noto-emoji/commit/24a33c4970f806d8eb8bfb12573ccb58e43dea83

After updating to latest noto-emoji I have only two failures: ``` FAIL ./emoji_u1f6cd.svg BadElement: /svg[0]/mask FAIL ./emoji_u1f54d.svg /svg[0]/pattern ``` For use of mask and pattern respectively.

@RoelN do you have good (picosvg-valid) versions of emoji_u1f6cd, emoji_u1f54d by any chance?

> @rsheeter Sure, please see your email! Apparently you've been ahead of me for ages. I should have guessed, ty :)

Is it tolerable if some scenarios are in a different font? - that's what I've done in #55 for now.

> we have less of a reference if we don't have SVG source images? Agreed but there are cases you can't express in svg (sweep/conical gradient) and cases we won't...

@drott is probably best able to comment.

The spec (more correctly, proposed spec) update needs to land and then we upgrade FontTools, nanoemoji, possibly picosvg, FreeType, Skia and compile a demofont here (FreeType and Skia aren't required...