#69 ps and psttf devices don't render example 28 correctly

open
Andrew Ross
None
5
2009-12-09
2009-12-07
Alan W. Irwin
No

For both these closely related devices the 3D text is badly rendered (substantial offset problems) for pages 2 and 3, and there is also a small offset problem for page 4 (the "e" in "The" is dropped by half a letter height). These offset problems disappear if you use -drvopt text=0 (which uses the historical well-debugged code path for Hershey fonts). Recently, all 3D text issues for the cairo devices have been fixed so if you follow that modern 3D code path for text positioning with
the ps and psttf devices for text=1, I suspect this current bug would disappear.

Discussion

  • Andrew Ross
    Andrew Ross
    2009-12-07

    • status: open --> closed-fixed
     
  • Andrew Ross
    Andrew Ross
    2009-12-07

    Now fixed in svn by using the same helper function used by e.g. the cairo driver.

     
  • Andrew Ross
    Andrew Ross
    2009-12-09

    Further analysis reveals that the issues are only partly fixed. There as still issues with horizontal justification for ps / psttf (and also other drivers including xwin, but not cairo / qt). I am still investigating.

     
  • Andrew Ross
    Andrew Ross
    2009-12-09

    • status: closed-fixed --> open
     
  • Andrew Ross
    Andrew Ross
    2009-12-11

    A fix is now in place for the core code using Hershey fonts so the xwin driver and ps with -drvopt text=0 work correctly. There is still an issue with 3d text justification in the ps driver text handling code. I suspect it is the same issue (stride is not taken into account), but I've not worked out how to fix this with postscript yet.