This is essentially very close to "pass-previous-stitch-over" but can have a
slightly different meaning. It's possible for the slipped st to not be the
second to last st on the previous needle. Also, many patterns use "psso" (pass
slipped st over) as a functional equivalent to "pass-previous-stitch-over"
which only confounds the issue.
Ultimately, to do this right, the engine would have to track which stitch the
last stitch slipped was and pass it over. There are issues possibly with
creating the validated XML from this information since "pass slipped st" isn't
itself a discrete operation (it relies on previous state of the engine, so that
would somehow have to be codified into the result... maybe
<pass-previous-stitch-over slipped="true"/>?)
Original issue reported on code.google.com by fiddlerpianist@gmail.com on 9 Jan 2011 at 5:47
Original issue reported on code.google.com by
fiddlerpianist@gmail.com
on 9 Jan 2011 at 5:47