From Newsgroup: comp.lang.postscript
On Thursday, June 4, 2020 at 5:15:48 AM UTC-5, jdaw1 wrote:
As a marker, this is still wanted. But only if it works with total reliability, even on the nasty paths made by charpath, whether the font be a Helvetica, a Garamond, or a Blackletter monstrosity.
The path forward appears to me to be in that Bezier curve classification
paper. My code has all the infrastructure to run through the path,
gather lots of context points for each curve, calculate vectors and
normals and offsets of the control points. But it's missing some
heuristics to detect problem curves and deal with them, probably by
chopping into 2 simpler curves.
But if we can analyze the curve and detect whether there's a cusp
in the middle and *where* on the curve it is, then we can chop the
curve into two easier pieces and a few recursive steps should yield
an offset curve with better fine tracking. ... Or maybe better not
to chop and find an intersection between offsets of the two vectors.
I'm not sure which track will yield better results.
--- Synchronet 3.21d-Linux NewsLink 1.2