View Single Post
Old 01-12-2019, 12:28 PM   #1664
willus
Fuzzball, the purple cat
willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.
 
willus's Avatar
 
Posts: 1,303
Karma: 11087488
Join Date: Jun 2011
Location: California
Device: iPad
Quote:
Originally Posted by abe1 View Post
Command line:
-wrap+ -ppgs -vb -2 -bp m -ocr- -as -col 1 -odpi 330 -dr 1.3 -ws -0.001
A couple of comments on these options:

1. Checking the "Post-process w/Ghostscript" and "Avoid Text Select Overlap" boxes (which result in the -ppgs and -bp m options above, respectively) is really only necessary when native PDF output is selected. Since you also have "Re-flow text" selected, you will not get native PDF output, and these options are of no benefit.

2. The 0.001 value in the "Smart line breaks" numeric entry field (leading to the -ws -0.001 above) is very small for the smart line breaks and would be unlikely to give a good result if actually used (it is only used if the heuristic "smart" algorithm fails to meet a certain decision threshold). I went back and ran your PDF source document from this post through k2pdfopt with both -ws -0.2 and -ws -0.001, and I got an identical result. There was no improvement by using -ws -0.001.

Last edited by willus; 01-12-2019 at 12:43 PM. Reason: Updated #2
willus is offline   Reply With Quote