Bug 691646

Summary: Wrong rendering of 16-01.ps
Product: Ghostscript Reporter: Alex Cherepanov <alex>
Component: TextAssignee: Chris Liddell (chrisl) <chris.liddell>
Status: RESOLVED FIXED    
Severity: normal    
Priority: P4    
Version: master   
Hardware: PC   
OS: Windows NT   
Customer: Word Size: ---

Description Alex Cherepanov 2010-09-27 01:02:24 UTC
Test file 16-01.ps is rendered incorrectly by all versions of gs but there
are significant differences between versions.
v. 7.20 and earlier
  correctly uses eofill on the self-intersecting path but applies
  eofill to the contours that should be drawn separately,
  position of "~197" is correct.
v.7.21 to 8.71 uses fill on the self-intersecting path. The effect 
  on different contours is masked.
  position of "~197" is correct.
v.9.00 and later is similar to 8.71 but position of "~197" is incorrect.

PDF file generated by v. 900 and HEAD looks correct in Acrobat.
v. 9.00 and HEAD strokes all characters instead of filling,
position of "~197" is correct.
HEAD with the upcoming CFF patch renders PDF file similar to v.8.71
with correct position of "~197".
Comment 1 Ken Sharp 2010-09-27 06:59:08 UTC
I'm assuming the change in version 9 is down to the use of FreeType, and the use of fill/eofill seems to be more of a font rendering issue than 'text' as such and so I'm assigning this to Chris. If it turns out to be something else feel free to punt it back.
Comment 2 Chris Liddell (chrisl) 2019-10-17 11:09:00 UTC
This seems to be working as expected now. I'm not going to trawl through nine years of changes to find where it was fixed.