Hi, On Sat, Aug 14, 2021 at 09:05:45PM +0200, Hans Hagen wrote:
that's because since then we check for the cycle (otherwise artifacts)
it probably relates to these extra points (the 'standard' is somewhat fuzzy in that respect also because some fonts have them and some don't so it's the usual wait till we run into something issue)
As far as I understand the spec the phantom points shouldn't influence this since the next and previous points are only looked up in the current contour and the phantom point are not on any contour, so they can never appear as next or previous point anyway. That doesn't seem to be implemented though.
we can check for bounds
for i=1,nofpoints do local d1, d2, d3 = find(i) local p2 = points[i] if d2 then xv[i] = xvalues[d2] yv[i] = yvalues[d2] else local n1 = dpoints[d1] local n3 = dpoints[d3] if n1 > nofpoints then n1 = nofpoints end if n3 > nofpoints then n3 = nofpoints end
no crash then (the resulting shapes look good enough to me, assumign that the weird f is intended)
Thanks, with this change ConTeXt seems to give the expected output for this font. (Yes, the weird f is intentional. Evn though IMO it's not siginificantly weirder than the other glyphs in that font) Best, Marcel