Comment 73 for bug 1662531

Hi, as this tangentially affects me I think I have a proposal that may be better (at least for Print Win32 Vector). I've been working the last few days to enhance it and add support for all the elements that were previously not handled as indicated in the first post.

I even have better support for line caps, joins, and miter limit and more. This would negate the need for a prepare_print_win32_vector.py once I fix the issues outlined below. You can view the changes here: https://bitbucket.org/AMcBain/print-win32-vector-plus/

I was planning to submit it back for merging once I fixed that project's issues 1, 2, and 3 but hopefully also 6. (tl;dc: 1 -> fix polyline support, 2 -> fix start/end gap with closed shapes <rect> (no rx or ry) and <polygon>, 3 -> let users choose cut stroke width cutoff value), 6 -> turn text into a path before printing) This ticket gives me ideas on how to do 6 at least.

I contacted a few of the people related to laser cutting and Print Win32 Vector here on Launchpad to see if I could get other testers and input. Myself I've tested these changes with an Epilog Mini 24 to good success.