Mercurial > octave-nkf
changeset 14897:8e2a6fc55787
doc: Use 'grayscale' rather than 'gray-scale' in documentation.
* image.txi, cmunique.m, imshow.m: Use 'grayscale' rather than 'gray-scale' in
documentation.
| author | Rik <rik@octave.org> |
|---|---|
| date | Fri, 20 Jul 2012 12:26:31 -0700 |
| parents | 0ba7be7fed1c |
| children | f8bb15f6a19b |
| files | doc/interpreter/image.txi scripts/image/cmunique.m scripts/image/imshow.m |
| diffstat | 3 files changed, 5 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/interpreter/image.txi Fri Jul 20 12:22:48 2012 -0700 +++ b/doc/interpreter/image.txi Fri Jul 20 12:26:31 2012 -0700 @@ -93,15 +93,15 @@ @node Representing Images @section Representing Images -In general Octave supports four different kinds of images, gray-scale -images, RGB images, binary images, and indexed images. A gray-scale +In general Octave supports four different kinds of images, grayscale +images, RGB images, binary images, and indexed images. A grayscale image is represented with an M-by-N matrix in which each element corresponds to the intensity of a pixel. An RGB image is represented with an M-by-N-by-3 array where each 3-vector corresponds to the red, green, and blue intensities of each pixel. -The actual meaning of the value of a pixel in a gray-scale or RGB +The actual meaning of the value of a pixel in a grayscale or RGB image depends on the class of the matrix. If the matrix is of class @code{double} pixel intensities are between 0 and 1, if it is of class @code{uint8} intensities are between 0 and 255, and if it is of class
--- a/scripts/image/cmunique.m Fri Jul 20 12:22:48 2012 -0700 +++ b/scripts/image/cmunique.m Fri Jul 20 12:26:31 2012 -0700 @@ -34,7 +34,7 @@ ## In the worst case the new map could have as many rows as the number of ## pixels in the original image. ## -## When the input is a greyscale image @var{I}, the output colormap will +## When the input is a grayscale image @var{I}, the output colormap will ## contain one entry for every unique intensity value in the original image. ## In the worst case the new map could have as many rows as the number of ## pixels in the original image.
--- a/scripts/image/imshow.m Fri Jul 20 12:22:48 2012 -0700 +++ b/scripts/image/imshow.m Fri Jul 20 12:26:31 2012 -0700 @@ -25,7 +25,7 @@ ## @deftypefnx {Function File} {} imshow (@dots{}, @var{string_param1}, @var{value1}, @dots{}) ## @deftypefnx {Function File} {@var{h} =} imshow (@dots{}) ## Display the image @var{im}, where @var{im} can be a 2-dimensional -## (gray-scale image) or a 3-dimensional (RGB image) matrix. +## (grayscale image) or a 3-dimensional (RGB image) matrix. ## ## If @var{limits} is a 2-element vector @code{[@var{low}, @var{high}]}, ## the image is shown using a display range between @var{low} and