Behdad Esfahbod
Behdad Esfahbod
Looking at those, blur and drop-shadow look special / harder. The rest look possibly simple implementations through the belnding we already have.
> Why not just cry uncle and allow for the embedding of WGSL shaders to specify the material of a fill or stroke? Because we also have to implement what...
Correct... We can possibly redefine rgba value `#FFFFFF00`, which is one of the 2^24 different representations of fully-transparent color, to mean "foreground".
I'm not convinced this is worth pursuing. The sharing happens only if the same paint is also used...
> I'm not convinced this is worth pursuing. The sharing happens only if the same paint is also used... Okay maybe it is useful, for font-wide effects...
Using GlyphID16 65535 for this works, since that glyph is inaccessible in current font technology. (max glyphid is 65534, because maxp.numGlyphs can at most be 65535).
> > inaccessible in current font technology > > since a change in the semantics of GlyphID would require a COLRv2 anyway, we might as well bundle that up with...
Alternatively it can be a separate PaintSelf with no data.
I implemented this in FontTools. See https://github.com/fonttools/fonttools/pull/3244#issuecomment-1666672082
> To get this effect (each glyph painting a translated copy of its own source glyph three times) Where can I get this?