From be53c19faa6b3cea13b923976af67b800078ee3a Mon Sep 17 00:00:00 2001 From: giraffedata Date: Sun, 23 Jul 2023 23:14:33 +0000 Subject: miscellaneous update git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@4568 9d0c8265-081b-0410-96cb-a4ca84ce46f8 --- g3topbm.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/g3topbm.html b/g3topbm.html index 1c0f438d..6ead645a 100644 --- a/g3topbm.html +++ b/g3topbm.html @@ -132,8 +132,8 @@ lines turn into one.

Without this option, g3topbm faithfully renders the document as coded, so the output PBM image simply contains that long line. This is an -especially problematic corruption because it makes the entire out image about -twice as wide as it is supposed to be. But with -correctlong, +especially problematic corruption because it makes the entire output image +about twice as wide as it is supposed to be. But with -correctlong, g3topbm truncates that line so the overall effect of the input corruption is that a line is missing rather than that the image is twice as wide as it is supposed to be. @@ -143,7 +143,7 @@ all the lines (which would all be the same length in an uncorrupted G3 image) and considers the line length that occurs the most to be the intended image width. It truncates every line that is longer than that. -

The program warns you when corruption has causes the input image to have +

The program warns you when corruption has caused the input image to have lines of more than one length, whether you specify -correctlong or not.

Note that there is no point to specifying -correctlong if you also -- cgit 1.4.1