Fix handling of paths not starting with move to
Fix handling of paths not starting with move to

The call for rMoveTo() should be before _nextPoint() otherwise the move
to will be relative to the current point which is wrong. After fixing
this, the check for self.firstMarkingOpSeen becomes redundant,
potentially adding a duplicate move to (0, 0) point.

khaledhosny/psautohint,khaledhosny/psautohint