Commit 8cafd175 authored by Rashad Kanavath's avatar Rashad Kanavath
Browse files

ENH: apply spelling.patch from DebianGIS

This is a big one without much harm. It fixes incorrect spelling
and grammer when packaging OTB 5.0.0 and 5.2.0 for Debian.
Most of these changes are done by developers at DebianGIS.
For more info, I include the original patch header below.
Description: Fix some spelling errors to silence lintian
enabling  to concentrate on the real problem.
Author: Andreas Tille <tille@debian.org>
Author: Rashad Kanavath <rashad.kanavath@c-s.fr>
Author: Bas Couwenberg <sebastic@xs4all.nl>
Last-Update: 2015-12-22
parent 39c99797
......@@ -17,7 +17,7 @@ of Health. ITK is partially derived from VTK and VXL, hence some code is
copyrighted accordingly (see VTKCopyright.txt and VXLCopyright.txt).
The copyright of most of the files in the "Utilities" subdirectory is held by
third parties who allow to distribute this material under a license compatible
third parties who allow distributing this material under a license compatible
with the one used by ITK. Please read the content of the subdirectories for
specific details on those third-party licenses. You will also find details in
the README.txt file under the "Copyright" subdirectory.
......
......@@ -151,7 +151,7 @@ int main( int argc, char* argv[])
//
// Now we can define the mathematical expression to perform on the layers (b1, b2, b3, b4).
// The filter takes advantage of the parsing capabilities of the muParser library and
// allows to set the expression as on a digital calculator.
// allows setting the expression as on a digital calculator.
//
// The expression below returns 255 if the ratio $(NIR-RED)/(NIR+RED)$ is greater than 0.4 and 0 if not.
//
......
......@@ -51,7 +51,7 @@
// something accepting the syntax \code{foo()}. This can be
// implemented using classical C/C++ functions, but it is preferable
// to implement it using C++ functors. These are classical C++ classes
// which overload the \code{()} operator. This allows to use them with
// which overload the \code{()} operator. This allows using them with
// the same syntax as C/C++ functions.
//
// Since change detectors operate on neighborhoods, the functor
......
......@@ -32,8 +32,8 @@
// This example illustrates the class
// \doxygen{otb}{MultivariateAlterationChangeDetectorImageFilter},
// which implements the Multivariate Alteration Change Detector
// algorithm \cite{nielsen2007regularized}. This algorihtm allows to
// perform change detection from a pair multi-band images, including
// algorithm \cite{nielsen2007regularized}. This algorihtm allows
// performing change detection from a pair multi-band images, including
// images with different number of bands or modalities. Its output is
// a a multi-band image of change maps, each one being unccorrelated
// with the remaining. The number of bands of the output image is the
......
......@@ -135,8 +135,8 @@ int main(int itkNotUsed(argc), char * argv[])
//
// Other useful methods are:
// \begin{itemize}
// \item \code{SetNthElement()} and \code{GetNthElement()} allow to
// randomly access any element of the list.
// \item \code{SetNthElement()} and \code{GetNthElement()} allow
// randomly accessing any element of the list.
// \item \code{Front()} to access to the first element of the list.
// \item \code{Erase()} to remove an element.
// \end{itemize}
......
......@@ -40,7 +40,7 @@
// However, the \doxygen{itk}{Vector} is a fixed size array and it
// assumes that the number of channels of the image is known at
// compile time. Therefore, we prefer to use the
// \doxygen{otb}{VectorImage} class which allows to choose the number
// \doxygen{otb}{VectorImage} class which allows choosing the number
// of channels of the image at runtime. The pixels will be of type
// \doxygen{itk}{VariableLengthVector}.
//
......@@ -91,7 +91,7 @@ int main(int, char *[])
image->SetRegions(region);
// Software Guide : BeginLatex
// Since the pixel dimensionality is choosen at runtime, one has to
// Since the pixel dimensionality is chosen at runtime, one has to
// pass this parameter to the image before memory allocation.
// Software Guide : EndLatex
......
......@@ -25,7 +25,7 @@
// This example illustrates how a point set can be parameterized to manage a
// particular pixel type. It is quite common to associate vector values with
// points for producing geometric representations or storing
// multi-band informations. The following code shows
// multi-band information. The following code shows
// how vector values can be used as pixel type on the PointSet class. The
// \doxygen{itk}{Vector} class is used here as the pixel type. This class is
// appropriate for representing the relative position between two points. It
......
......@@ -26,7 +26,7 @@
// Software Guide : BeginLatex
//
// This example illustrates the use of the \doxygen{otb}{ImageToPathListAlignFilter}.
// This filter allows to extract meaninful alignments. Alignments
// This filter allows extracting meaninful alignments. Alignments
// (that is edges and lines) are detected using the {\em Gestalt}
// approach proposed by Desolneux et al. \cite{desolneux}. In this
// context, an event is
......
......@@ -180,7 +180,7 @@ int main(int argc, char * argv[])
// Software Guide : BeginLatex
//
// The methods \code{SetLengthLine()} and \code{SetWidthLine()}
// allow to set the minimum length and the typical witdh of the
// allow setting the minimum length and the typical witdh of the
// lines which are to be detected.
//
// \index{otb::AssymetricFusionOfDetector!SetWidthLine()}
......
......@@ -185,7 +185,7 @@ int main(int argc, char * argv[])
// Software Guide : BeginLatex
//
// The methods \code{SetLengthLine()} and \code{SetWidthLine()}
// allow to set the minimum length and the typical witdh of the
// allow setting the minimum length and the typical witdh of the
// lines which are to be detected.
//
// \index{otb::LineCorrelationDetector!SetWidthLine()}
......
......@@ -194,7 +194,7 @@ int main(int argc, char * argv[])
// Software Guide : BeginLatex
//
// The methods \code{SetLengthLine()} and \code{SetWidthLine()}
// allow to set the minimum length and the typical witdh of the
// allow setting the minimum length and the typical witdh of the
// lines which are to be detected.
//
//
......
......@@ -191,7 +191,7 @@ int main(int argc, char * argv[])
// Software Guide : BeginLatex
//
// The methods \code{SetLengthLine()} and \code{SetWidthLine()}
// allow to set the minimum length and the typical witdh of the
// allow setting the minimum length and the typical witdh of the
// lines which are to be detected.
//
//
......
......@@ -184,7 +184,7 @@ int main(int argc, char * argv[])
// Software Guide : BeginLatex
//
// The methods \code{SetLengthLine()} and \code{SetWidthLine()}
// allow to set the minimum length and the typical witdh of the
// allow setting the minimum length and the typical witdh of the
// lines which are to be detected.
//
// \index{otb::LineRatioDetector!SetWidthLine()}
......
......@@ -24,7 +24,7 @@
// Software Guide : BeginLatex
//
// The \doxygen{otb}{VectorDataToMapFilter} allows to perform
// The \doxygen{otb}{VectorDataToMapFilter} allows performing
// rasterization of a given vector data as a binary mask. This example
// will demonstrate how to use this filter to perform rasterization of
// the SRTM water body masks available here:
......
......@@ -68,9 +68,9 @@ if(argc!=8)
// Software Guide : BeginLatex
//
// It allows to configure a directory containing DEM tiles (DTED or SRTM
// It allows configuring a directory containing DEM tiles (DTED or SRTM
// supported) using the \code{OpenDEMDirectory()} method. The \code{OpenGeoidFile()} method
// allows to input a geoid file as well. Last, a default height above ellipsoid
// allows inputting a geoid file as well. Last, a default height above ellipsoid
// can be set using the \code{SetDefaultHeightAboveEllipsoid()} method.
//
// Software Guide : EndLatex
......
......@@ -36,7 +36,7 @@
// OTB is using GDAL to support HDF. HDF4 and HDF5 supports in Gdal is
// not activated by default. You need to download the HDF run-time
// libraries and compile Gdal by adding the support of these formats. You can
// find more informations here : \url{http://trac.osgeo.org/gdal/wiki/HDF}
// find more information here : \url{http://trac.osgeo.org/gdal/wiki/HDF}
//
//
// The first step toward the use of these filters is to include the proper header files.
......@@ -87,9 +87,9 @@ int main(int itkNotUsed(argc), char * argv[])
// Software Guide : BeginLatex
//
// You can access to subdatasets' informations available in the HDF file using
// You can access to subdatasets' information available in the HDF file using
// the \code{GetSubDatasetInfo} method of \doxygen{otb}{GDALImageIO}.
// It allows to store HDF subdatasets names and descriptions in vector of string.
// It allows storing HDF subdatasets names and descriptions in vector of string.
// You can find below how to print the name and the decription
// of all the subdatasets.
//
......
......@@ -93,8 +93,8 @@ int main(int argc, char * argv[])
//
// The ExtractROI type is instantiated using
// the input and output pixel types. Using the pixel types as
// template parameters instead of the image types allows to
// restrict the use of this class to \doxygen{otb}{Image}s which
// template parameters instead of the image types allows
// restricting the use of this class to \doxygen{otb}{Image}s which
// are used with scalar pixel types. See section
// \ref{sec:ExtractROI} for the extraction of ROIs on
// \doxygen{otb}{VectorImage}s. A filter object is created with the
......
......@@ -30,7 +30,7 @@
// and MapFile products.
// Note that the \doxygen{otb}{KmzProductWriter} and the
// \doxygen{otb}{MapFileProductWriter} can only process inputs with a
// non empty geographical informations.
// non empty geographical information.
//
// The first step toward the use of these filters is to include the
// proper header files: the one for the rpc sensor estimation filter and
......@@ -113,7 +113,7 @@ int main(int argc, char* argv[])
// or its keywordlist is updated. In general, a dozen of GCPs are
// needed to estimate an accurate sensor model. The points are added
// via the method AddGCP(PointType2D, PointType3D). The outpput image
// obtained have the needed meta-data informations for the rest of the
// obtained have the needed meta-data information for the rest of the
// process.
//
// Software Guide : EndLatex
......
......@@ -178,7 +178,7 @@ int main(int itkNotUsed(argc), char* argv[])
// \subdoxygen{itk}{Statistics}{ListSample} as input and estimates the label of each
// input sample using the model. Finally, the
// \doxygen{otb}{ImageClassificationModel} inherits from the
// \doxygen{itk}{ImageToImageFilter} and allows to classify pixels in the
// \doxygen{itk}{ImageToImageFilter} and allows classifying pixels in the
// input image by predicting their labels using a model.
//
// Software Guide : EndLatex
......
......@@ -78,7 +78,7 @@ int main(int argc, char* argv[])
// Software Guide : BeginLatex
// The filters \doxygen{otb}{HooverMatrixFilter} and \doxygen{otb}{HooverInstanceFilter}
// are designed to handle \doxygen{itk}{LabelMap} images, made with \doxygen{otb}{AttributesMapLabelObject}.
// This type of label object allows to store generic attributes. Each region can store
// This type of label object allows storing generic attributes. Each region can store
// a set of attributes: in this case, Hoover instances and metrics will be stored.
// Software Guide : EndLatex
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment