From e9130c54e8a75339fab9e9b14f37bd8877ccbd88 Mon Sep 17 00:00:00 2001 From: giraffedata Date: Wed, 26 Jan 2011 16:56:38 +0000 Subject: typo fixes from john@johnbradshaw.org git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@1395 9d0c8265-081b-0410-96cb-a4ca84ce46f8 --- pnmnorm.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'pnmnorm.html') diff --git a/pnmnorm.html b/pnmnorm.html index 738987bb..8c025984 100644 --- a/pnmnorm.html +++ b/pnmnorm.html @@ -107,15 +107,15 @@ decimal. Zero is valid and is the same as -bvalue=0 or -wvalue=maxval, respectively.

Because there are whole numbers of pixels at each brightness, -pnmnorm obviously can't guarantee the exact per centage, so it -arranges that at least the per centage of pixels you specify +pnmnorm obviously can't guarantee the exact percentage, so it +arranges that at least the percentage of pixels you specify get remapped as promised.

It is possible for your -bpercent or -wpercent to overlap your -wvalue or -bvalue, respectively. For example, you say -bpercent=20 and -wvalue=100 for an -image in which only 10 per cent of the pixels are darker than 100. -In that case, pnmnorm adjusts the per centile value as +image in which only 10 percent of the pixels are darker than 100. +In that case, pnmnorm adjusts the percentile value as required. In the example, it uses 99 as the black value (like -bvalue=99). @@ -144,7 +144,7 @@ intensity by 4 units now differ by 10, and that might be unsightly.

So that you can put a limit on the amount of expansion without having to examine the image first, there is the -maxexpand option. It specifies the maximum expansion you will tolerate, as an -additional per centage. In the example above, you could say +additional percentage. In the example above, you could say -maxexpand=50 to say you want the range to expand by at most 50%, regardless of your other options. pnmnorm figures out what intensity to stretch to full intensity and what intensity to -- cgit 1.4.1