|
View:
New views
1 Messages
—
Rating Filter:
Alert me
|
|
|
Some more spelling fixesHello,
Please consider the enclosed spelling fixes to the help texts and to the manual. With best regards, Olli # HG changeset patch # User ojs@localhost # Date 1214510709 -10800 # Node ID 30cafefacf8361620d8cbb08c51c71d0c249f1c1 # Parent f1a1f6dd7fac4a6d98932571657d19bbd7b3dc0a Spelling fixes. diff -r f1a1f6dd7fac -r 30cafefacf83 doc/ChangeLog --- a/doc/ChangeLog Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/ChangeLog Thu Jun 26 23:05:09 2008 +0300 @@ -1,3 +1,11 @@ 2008-05-20 David Bateman <dbateman@fre +2008-06-26 Olli Saarela <Olli.Saarela@...> + + * faq/Octave-FAQ.texi, interpreter/basics.txi, interpreter/container.txi, + interpreter/dynamic.txi, interpreter/errors.txi, interpreter/install.txi, + interpreter/matrix.txi, interpreter/nonlin.txi, interpreter/numbers.txi, + interpreter/package.txi, interpreter/plot.txi, interpreter/sparse.txi, + interpreter/tips.txi: Spelling fixes. + 2008-05-20 David Bateman <dbateman@...> * interpreter/debug.txi: Uodate documentation for multiline diff -r f1a1f6dd7fac -r 30cafefacf83 doc/faq/Octave-FAQ.texi --- a/doc/faq/Octave-FAQ.texi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/faq/Octave-FAQ.texi Thu Jun 26 23:05:09 2008 +0300 @@ -975,7 +975,7 @@ are touched are restored. You can do som @sc{Matlab}, however rethrow and lasterror are only available in Octave 2.9.10 and later. Note that using @code{try}/@code{catch} combined with @samp{rethrow -(lasterror ())} can not guarentee that global variables will be +(lasterror ())} can not guarantee that global variables will be correctly reset, as it won't catch user interrupts with Ctrl-C. For example diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/basics.txi --- a/doc/interpreter/basics.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/basics.txi Thu Jun 26 23:05:09 2008 +0300 @@ -296,7 +296,7 @@ command in the @file{~/.octaverc} file w command in the @file{~/.octaverc} file will affect the directory that Octave searches for the file @file{.octaverc}. -If you start Octave in your home directory, commands from from the file +If you start Octave in your home directory, commands from the file @file{~/.octaverc} will only be executed once. @end table diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/container.txi --- a/doc/interpreter/container.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/container.txi Thu Jun 26 23:05:09 2008 +0300 @@ -678,7 +678,7 @@ strings, @code{strcmp}, @code{strcmpi}, @subsection Processing Data in Cell Arrays Data that is stored in a cell array can be processed in several ways -depending on the actual data. The most simple way to process that data +depending on the actual data. The simplest way to process that data is to iterate through it using one or more @code{for} loops. The same idea can be implemented easier through the use of the @code{cellfun} function that calls a user specified function on all elements of a cell @@ -717,7 +717,7 @@ example @noindent where @code{@var{i}, @var{j}} is equally a comma separated list. Comma separated lists can not be directly manipulated by the user. However, -both structures are cell arrays can be converted into comma +both structures and cell arrays can be converted into comma separated lists, which makes them useful to keep the input arguments and return values of functions organized. Another example of where a comma separated list can be used is in the creation of a new array. If all the diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/dynamic.txi --- a/doc/interpreter/dynamic.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/dynamic.txi Thu Jun 26 23:05:09 2008 +0300 @@ -457,7 +457,7 @@ structdemo (x, "b") @end example The commented code above demonstrates how to iterate over all of the -fields of the structure, where as the following code demonstrates finding +fields of the structure, whereas the following code demonstrates finding a particular field in a more concise manner. As can be seen the @code{contents} method of the @code{Octave_map} class @@ -535,7 +535,7 @@ The use of @code{numel} should therefore The use of @code{numel} should therefore be avoided useless it is known it won't overflow. -Extreme care must be take with the elem method and the "()" operator, +Extreme care must be taken with the elem method and the "()" operator, which perform basically the same function. The reason is that if a sparse object is non-const, then Octave will assume that a request for a zero element in a sparse matrix is in fact a request @@ -1008,7 +1008,7 @@ checking needed to ensure that Octave be checking needed to ensure that Octave behaves well. The minimum requirement, as previously discussed, is to check the number -of input arguments before using them to avoid referencing a non existent +of input arguments before using them to avoid referencing a nonexistent argument. However, it some case this might not be sufficient as the underlying code imposes further constraints. For example an external function call might be undefined if the input arguments are not @@ -1041,8 +1041,8 @@ paramdemo ([1, 2, NaN, Inf]) Another important feature of Octave is its ability to react to the user typing @kbd{Control-C} even during calculations. This ability is based on the -C++ exception handler, where memory allocated by the C++ new/delete -methods are automatically released when the exception is treated. When +C++ exception handler, where memory blocks allocated by the C++ operator +@code{new} are automatically released when the exception is treated. When writing an oct-file, to allow Octave to treat the user typing @kbd{Control-C}, the @code{OCTAVE_QUIT} macro is supplied. For example @@ -1586,7 +1586,7 @@ mex-files is given by the file @file{mys It is also possible call other Octave functions from within a mex-file using @code{mexCallMATLAB}. An example of the use of -@code{mexCallMATLAB} can be see in the example below +@code{mexCallMATLAB} can be seen in the example below @longexamplefile{myfeval.c} diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/errors.txi --- a/doc/interpreter/errors.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/errors.txi Thu Jun 26 23:05:09 2008 +0300 @@ -237,7 +237,7 @@ It is however possible to access the las It is however possible to access the last warning as a string using the @code{lastwarn} function. -It is also possible to assign an identification string a a warning. +It is also possible to assign an identification string to a warning. If a warning has such an ID the user can enable and disable this warning as will be described in the next section. To assign an ID to a warning, simply call @code{warning} with two string arguments, where the first diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/install.txi --- a/doc/interpreter/install.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/install.txi Thu Jun 26 23:05:09 2008 +0300 @@ -66,7 +66,7 @@ Look for Octave sources in the directory @item --enable-bounds-check Enable bounds checking for indexing operators in the internal array classes. This option is primarily used for debugging Octave. Building -Octave with this option has a negative impact on performace and is not +Octave with this option has a negative impact on performance and is not recommended for general use. @item --enable-64 diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/matrix.txi --- a/doc/interpreter/matrix.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/matrix.txi Thu Jun 26 23:05:09 2008 +0300 @@ -223,7 +223,7 @@ single element of a random sequence. single element of a random sequence. The @code{rand} and @code{randn} functions use Fortran code from -@sc{Ranlib}, a library of fortran routines for random number generation, +@sc{Ranlib}, a library of Fortran routines for random number generation, compiled by Barry W. Brown and James Lovato of the Department of Biomathematics at The University of Texas, M.D. Anderson Cancer Center, Houston, TX 77030. diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/nonlin.txi --- a/doc/interpreter/nonlin.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/nonlin.txi Thu Jun 26 23:05:09 2008 +0300 @@ -40,7 +40,7 @@ using the function @code{fsolve}, which using the function @code{fsolve}, which is based on the @sc{Minpack} subroutine @code{hybrd}. This is an iterative technique so a starting point will have to be provided. This also has the consequence that -convergence is not guarantied even if a solution exists. +convergence is not guaranteed even if a solution exists. @DOCSTRING(fsolve) diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/numbers.txi --- a/doc/interpreter/numbers.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/numbers.txi Thu Jun 26 23:05:09 2008 +0300 @@ -535,7 +535,7 @@ operators. @DOCSTRING(bitxor) -The bitwise 'not' operator is unary operator that performs a logial +The bitwise 'not' operator is unary operator that performs a logical negation of each of the bits of the value. For this to make sense, the mask against which the value is negated must be defined. Octave's bitwise 'not' operator is @code{bitcmp}. diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/package.txi --- a/doc/interpreter/package.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/package.txi Thu Jun 26 23:05:09 2008 +0300 @@ -429,7 +429,7 @@ toolbox >> Toolbox name toolbox >> Toolbox name @end example -@item Lines beginning with an alphabetical character indicates a new +@item Lines beginning with an alphabetical character indicate a new category of functions. @item Lines starting with a white space character indicate that the diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/plot.txi --- a/doc/interpreter/plot.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/plot.txi Thu Jun 26 23:05:09 2008 +0300 @@ -131,7 +131,7 @@ contour plots from three dimensional dat @DOCSTRING(contourc) The @code{errorbar}, @code{semilogxerr}, @code{semilogyerr}, and -@code{loglogerr} functions produces plots with error bar markers. For +@code{loglogerr} functions produce plots with error bar markers. For example, @example diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/sparse.txi --- a/doc/interpreter/sparse.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/sparse.txi Thu Jun 26 23:05:09 2008 +0300 @@ -79,7 +79,7 @@ for sparse matrix computation", 1994, for sparse matrix computation", 1994, @url{http://www-users.cs.umn.edu/~saad/software/SPARSKIT/paper.ps}}. With full matrices, knowledge of the point of an element of the matrix -within the matrix is implied by its position in the computers memory. +within the matrix is implied by its position in computer's memory. However, this is not the case for sparse matrices, and so the positions of the non-zero elements of the matrix must equally be stored. @@ -91,7 +91,7 @@ The storage technique used within Octave The storage technique used within Octave is the compressed column format. In this format the position of each element in a row and the data are stored as previously. However, if we assume that all elements -in the same column are stored adjacent in the computers memory, then +in the same column are stored adjacent in computer's memory, then we only need to store information on the number of non-zero elements in each column, rather than their positions. Thus assuming that the matrix has more non-zero elements than there are columns in the @@ -555,8 +555,8 @@ Note that the @code{sparse_auto_mutate} @subsubsection Mathematical Considerations The attempt has been made to make sparse matrices behave in exactly the -same manner as there full counterparts. However, there are certain differences -and especially differences with other products sparse implementations. +same manner as their full counterparts. However, there are certain differences +and especially differences with other product's sparse implementations. Firstly, the "./" and ".^" operators must be used with care. Consider what the examples @@ -1109,7 +1109,7 @@ value in the z-axis for each simplex ver @ifset HAVE_COLAMD @float Figure,fig:femmodel @image{grid,8cm} -@caption{Example finite element model the showing triangular elements. +@caption{Example finite element model showing triangular elements. The height of each vertex corresponds to the solution value.} @end float @end ifset diff -r f1a1f6dd7fac -r 30cafefacf83 doc/interpreter/tips.txi --- a/doc/interpreter/tips.txi Fri Jun 20 23:38:44 2008 +0200 +++ b/doc/interpreter/tips.txi Thu Jun 26 23:05:09 2008 +0300 @@ -500,7 +500,7 @@ Help text in Texinfo format. Many complete examples of Texinfo documentation can be taken from the help strings for the Octave functions themselves. A relatively complete -example of which is the @code{nchoosek} function. The Texinfo +example of this is the @code{nchoosek} function. The Texinfo documentation string of @code{nchoosek} is @example diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/ChangeLog --- a/scripts/ChangeLog Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/ChangeLog Thu Jun 26 23:05:09 2008 +0300 @@ -1,3 +1,11 @@ 2008-06-11 John W. Eaton <jwe@... +2008-06-26 Olli Saarela <Olli.Saarela@...> + + * control/base/pzmap.m, control/hinf/wgt1o.m, control/system/sysdup.m, + general/accumarray.m, general/rotdim, general/sortrows.m, + general/structfun.m, miscellaneous/warning_ids.m, polynomial/pchip.m, + plot/area.m, plot/pie.m, plot/surface.m, strings/strtrunc.m: + Spelling fixes. + 2008-06-11 John W. Eaton <jwe@...> * set/ismember.m: Fix fail tests. diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/control/base/pzmap.m --- a/scripts/control/base/pzmap.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/control/base/pzmap.m Thu Jun 26 23:05:09 2008 +0300 @@ -32,7 +32,7 @@ ## @item pol ## @item zer ## if omitted, the poles and zeros are plotted on the screen. -## otherwise, @var{pol} and @var{zer} are returned as the +## Otherwise, @var{pol} and @var{zer} are returned as the ## system poles and zeros (see @command{sys2zp} for a preferable function call). ## @end table ## @end deftypefn diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/control/hinf/wgt1o.m --- a/scripts/control/hinf/wgt1o.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/control/hinf/wgt1o.m Thu Jun 26 23:05:09 2008 +0300 @@ -20,7 +20,7 @@ ## @deftypefn {Function File} {@var{W} =} wgt1o (@var{vl}, @var{vh}, @var{fc}) ## State space description of a first order weighting function. ## -## Weighting function are needed by the +## Weighting functions are needed by the ## @iftex ## @tex ## $ { \cal H }_2 / { \cal H }_\infty $ diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/control/system/sysdup.m --- a/scripts/control/system/sysdup.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/control/system/sysdup.m Thu Jun 26 23:05:09 2008 +0300 @@ -28,7 +28,7 @@ ## @item out_idx ## @itemx in_idx ## indices or names of desired signals (see @code{sigidx}). -## duplicates are made of @code{y(out_idx(ii))} and @code{u(in_idx(ii))}. +## Duplicates are made of @code{y(out_idx(ii))} and @code{u(in_idx(ii))}. ## @end table ## ## @strong{Output} diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/general/accumarray.m --- a/scripts/general/accumarray.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/general/accumarray.m Thu Jun 26 23:05:09 2008 +0300 @@ -35,7 +35,7 @@ ## column vector and returns a scalar. The result of the function should not ## depend on the order of the subscripts. ## -## The elements of the returned array that have no subscripts assoicated with +## The elements of the returned array that have no subscripts associated with ## them are set to zero. Defining @var{fillval} to some other value allows ## these values to be defined. ## diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/general/interp3.m --- a/scripts/general/interp3.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/general/interp3.m Thu Jun 26 23:05:09 2008 +0300 @@ -24,7 +24,7 @@ ## @deftypefnx {Function File} {@var{vi} =} interp3 (@dots{}, @var{method}) ## @deftypefnx {Function File} {@var{vi} =} interp3 (@dots{}, @var{method}, @var{extrapval}) ## -## Perform 3-dimensional interpolation. Each element of then 3-dimensional +## Perform 3-dimensional interpolation. Each element of the 3-dimensional ## array @var{v} represents a value at a location given by the parameters ## @var{x}, @var{y}, and @var{z}. The parameters @var{x}, @var{x}, and ## @var{z} are either 3-dimensional arrays of the same size as the array diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/general/rotdim.m --- a/scripts/general/rotdim.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/general/rotdim.m Thu Jun 26 23:05:09 2008 +0300 @@ -24,7 +24,7 @@ ## The third argument is also optional and defines the plane of the ## rotation. As such @var{plane} is a two element vector containing two ## different valid dimensions of the matrix. If @var{plane} is not given -## Then the first two non-singleton dimensions are used. +## then the first two non-singleton dimensions are used. ## ## Negative values of @var{n} rotate the matrix in a clockwise direction. ## For example, diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/general/sortrows.m --- a/scripts/general/sortrows.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/general/sortrows.m Thu Jun 26 23:05:09 2008 +0300 @@ -20,9 +20,9 @@ ## @deftypefn {Function File} {} sortrows (@var{a}, @var{c}) ## Sort the rows of the matrix @var{a} according to the order of the ## columns specified in @var{c}. If @var{c} is omitted, a -## lexicographical sort is used. By default ascending order is used -## however if elements of @var{c} are negative then the corrosponding -## column is sorted in descending order. +## lexicographical sort is used. By default ascending order is used. +## However, if elements of @var{c} are negative then the corresponding +## columns are sorted in descending order. ## @end deftypefn ## Author: Daniel Calvelo, Paul Kienzle diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/general/structfun.m --- a/scripts/general/structfun.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/general/structfun.m Thu Jun 26 23:05:09 2008 +0300 @@ -35,7 +35,7 @@ ## ## If the param 'UniformOutput' is set to true (the default), then the function ## must return either a single element which will be concatenated into the -## return value. If 'UniformOutput is false, the outputs placed in a structure +## return value. If 'UniformOutput' is false, the outputs are placed in a structure ## with the same fieldnames as the input structure. ## ## @example diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/miscellaneous/warning_ids.m --- a/scripts/miscellaneous/warning_ids.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/miscellaneous/warning_ids.m Thu Jun 26 23:05:09 2008 +0300 @@ -202,7 +202,7 @@ ## automatically in literal matrices. ## ## @item Octave:single-quote-string -## Print warning if a signle quote character is used to introduce a +## Print warning if a single quote character is used to introduce a ## string constant. ## ## @item Octave:str-to-num diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/plot/area.m --- a/scripts/plot/area.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/plot/area.m Thu Jun 26 23:05:09 2008 +0300 @@ -23,7 +23,7 @@ ## @deftypefnx {Function File} {} area (@var{y}, @dots{}) ## @deftypefnx {Function File} {} area (@var{h}, @dots{}) ## @deftypefnx {Function File} {@var{h} =} area (@dots{}) -## Area plot of cummulative sum of the columns of @var{y}. This shows the +## Area plot of cumulative sum of the columns of @var{y}. This shows the ## contributions of a value to a sum, and is functionally similar to ## @code{plot (@var{x}, cumsum (@var{y}, 2))}, except that the area under ## the curve is shaded. diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/plot/pie.m --- a/scripts/plot/pie.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/plot/pie.m Thu Jun 26 23:05:09 2008 +0300 @@ -24,7 +24,7 @@ ## @deftypefnx {Function File} {@var{h} =} pie (@dots{}); ## Produce a pie chart. ## -## Called with a single vector arrgument, produces a pie chart of the +## Called with a single vector argument, produces a pie chart of the ## elements in @var{x}, with the size of the slice determined by percentage ## size of the values of @var{x}. ## diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/plot/surface.m --- a/scripts/plot/surface.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/plot/surface.m Thu Jun 26 23:05:09 2008 +0300 @@ -33,7 +33,7 @@ ## @var{z} correspond to different @var{y} values. If @var{x} and @var{y} ## are missing, they are constructed from size of the matrix @var{z}. ## -## Any additional properties passed are assigned the the surface.. +## Any additional properties passed are assigned to the surface. ## @seealso{surf, mesh, patch, line} ## @end deftypefn diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/polynomial/pchip.m --- a/scripts/polynomial/pchip.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/polynomial/pchip.m Thu Jun 26 23:05:09 2008 +0300 @@ -26,7 +26,7 @@ ## specific points. ## ## The variable @var{x} must be a strictly monotonic vector (either -## increasing or decreasing). While @var{y} can be either a vector or +## increasing or decreasing), while @var{y} can be either a vector or ## array. In the case where @var{y} is a vector, it must have a length ## of @var{n}. If @var{y} is an array, then the size of @var{y} must ## have the form diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/strings/strtrunc.m --- a/scripts/strings/strtrunc.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/strings/strtrunc.m Thu Jun 26 23:05:09 2008 +0300 @@ -19,7 +19,7 @@ ## -*- texinfo -*- ## @deftypefn {Function File} {} strtrunc (@var{s}, @var{n}) ## Truncate the character string @var{s} to length @var{n}. If @var{s} -## is a char matrix, then the number of columns are adjusted. +## is a char matrix, then the number of columns is adjusted. ## ## If @var{s} is a cell array of strings, then the operation is performed ## on its members and the new cell array is returned. diff -r f1a1f6dd7fac -r 30cafefacf83 scripts/testfun/assert.m --- a/scripts/testfun/assert.m Fri Jun 20 23:38:44 2008 +0200 +++ b/scripts/testfun/assert.m Thu Jun 26 23:05:09 2008 +0300 @@ -42,9 +42,9 @@ ## ## @item assert(@var{observed}, @var{expected}, @var{tol}) ## Accept a tolerance when comparing numbers. -## If @var{tol} is possitive use it as an absolute tolerance, will produce an error if +## If @var{tol} is positive use it as an absolute tolerance; will produce an error if ## @code{abs(@var{observed} - @var{expected}) > abs(@var{tol})}. -## If @var{tol} is negative use it as a relative tolerance, will produce an error if +## If @var{tol} is negative use it as a relative tolerance; will produce an error if ## @code{abs(@var{observed} - @var{expected}) > abs(@var{tol} * @var{expected})}. ## If @var{expected} is zero @var{tol} will always be used as an absolute tolerance. ## @end table diff -r f1a1f6dd7fac -r 30cafefacf83 src/ChangeLog --- a/src/ChangeLog Fri Jun 20 23:38:44 2008 +0200 +++ b/src/ChangeLog Thu Jun 26 23:05:09 2008 +0300 @@ -1,3 +1,9 @@ 2008-06-23 Jaroslav Hajek <highegg@gmai +2008-06-26 Olli Saarela <Olli.Saarela@...> + + * octave.cc, bitfcns.cc, load-path.cc, variables.cc, + DLD-FUNCTIONS/fftw.cc, DLD-FUNCTIONS/matrix_type.cc, + DLD-FUNCTIONS/rand.cc: Spelling fixes. + 2008-06-23 Jaroslav Hajek <highegg@...> * genprops.awk (emit_source): Avoid gensub for portability. diff -r f1a1f6dd7fac -r 30cafefacf83 src/DLD-FUNCTIONS/fftw.cc --- a/src/DLD-FUNCTIONS/fftw.cc Fri Jun 20 23:38:44 2008 +0200 +++ b/src/DLD-FUNCTIONS/fftw.cc Thu Jun 26 23:05:09 2008 +0300 @@ -60,7 +60,7 @@ fftw ('dwisdom', @var{wisdom})\n\ \n\ If @var{wisdom} is an empty matrix, then the wisdom used is cleared.\n\ \n\ -During the calculation of fourier transforms further wisdom is generated.\n\ +During the calculation of Fourier transforms further wisdom is generated.\n\ The fashion in which this wisdom is generated is equally controlled by\n\ the @dfn{fftw} function. There are five different manners in which the\n\ wisdom can be treated, these being\n\ @@ -71,7 +71,7 @@ calculating a particular is performed, a calculating a particular is performed, and a simple heuristic is used\n\ to pick a (probably sub-optimal) plan. The advantage of this method is\n\ that there is little or no overhead in the generation of the plan, which\n\ -is appropriate for a fourier transform that will be calculated once.\n\ +is appropriate for a Fourier transform that will be calculated once.\n\ \n\ @item 'measure'\n\ In this case a range of algorithms to perform the transform is considered\n\ diff -r f1a1f6dd7fac -r 30cafefacf83 src/DLD-FUNCTIONS/matrix_type.cc --- a/src/DLD-FUNCTIONS/matrix_type.cc Fri Jun 20 23:38:44 2008 +0200 +++ b/src/DLD-FUNCTIONS/matrix_type.cc Thu Jun 26 23:05:09 2008 +0300 @@ -99,7 +99,7 @@ matrix type.\n\ matrix type.\n\ \n\ Also the test for positive definiteness is a low cost test for a hermitian\n\ -matrix with a real positive diagonal. This does not guarentee that the matrix\n\ +matrix with a real positive diagonal. This does not guarantee that the matrix\n\ is positive definite, but only that it is a probable candidate. When such a\n\ matrix is factorized, a Cholesky factorization is first attempted, and if\n\ that fails the matrix is then treated with an LU factorization. Once the\n\ diff -r f1a1f6dd7fac -r 30cafefacf83 src/DLD-FUNCTIONS/rand.cc --- a/src/DLD-FUNCTIONS/rand.cc Fri Jun 20 23:38:44 2008 +0200 +++ b/src/DLD-FUNCTIONS/rand.cc Thu Jun 26 23:05:09 2008 +0300 @@ -341,7 +341,7 @@ available, otherwise from cpu time, wall available, otherwise from cpu time, wall clock time and the current\n\ fraction of a second.\n\ \n\ -To compute the psuedo-random sequence, @code{rand} uses the Mersenne\n\ +To compute the pseudo-random sequence, @code{rand} uses the Mersenne\n\ Twister with a period of 2^19937-1 (See M. Matsumoto and T. Nishimura,\n\ ``Mersenne Twister: A 623-dimensionally\n\ equidistributed uniform pseudorandom number generator'', ACM Trans. on\n\ @@ -884,7 +884,7 @@ Stadlober E., et al., WinRand source cod @item For matrix @var{l} > 10, use patchwork rejection method.\n\ Stadlober E., et al., WinRand source code, available via FTP, or\n\ H. Zechner, 'Efficient sampling from continuous and discrete\n\ -unimodal distributions', Doctoral Dissertaion, 156pp., Technical\n\ +unimodal distributions', Doctoral Dissertation, 156pp., Technical\n\ University Graz, Austria, 1994.\n\ @item For @var{l} > 1e8, use normal approximation.\n\ L. Montanet, et al., 'Review of Particle Properties', Physical Review\n\ diff -r f1a1f6dd7fac -r 30cafefacf83 src/bitfcns.cc --- a/src/bitfcns.cc Fri Jun 20 23:38:44 2008 +0200 +++ b/src/bitfcns.cc Thu Jun 26 23:05:09 2008 +0300 @@ -409,8 +409,8 @@ DEFUN (bitshift, args, , @deftypefn {Built-in Function} {} bitshift (@var{a}, @var{k})\n\ @deftypefnx {Built-in Function} {} bitshift (@var{a}, @var{k}, @var{n})\n\ Return a @var{k} bit shift of @var{n}- digit unsigned\n\ -integers in @var{a}. A positive @var{k} leads to a left shift.\n\ -A negative value to a right shift. If @var{n} is omitted it defaults\n\ +integers in @var{a}. A positive @var{k} leads to a left shift,\n\ +and a negative value to a right shift. If @var{n} is omitted it defaults\n\ to log2(bitmax)+1.\n\ @var{n} must be in range [1,log2(bitmax)+1] usually [1,33]\n\ \n\ @@ -513,7 +513,7 @@ DEFUN (bitmax, args, , "-*- texinfo -*-\n\ @deftypefn {Built-in Function} {} bitmax ()\n\ Return the largest integer that can be represented as a floating point\n\ -value. On IEEE-754 compatiable systems, @code{bitmax} is @code{2^53 - 1}.\n\ +value. On IEEE-754 compatible systems, @code{bitmax} is @code{2^53 - 1}.\n\ @end deftypefn") { octave_value retval; diff -r f1a1f6dd7fac -r 30cafefacf83 src/load-path.cc --- a/src/load-path.cc Fri Jun 20 23:38:44 2008 +0200 +++ b/src/load-path.cc Thu Jun 26 23:05:09 2008 +0300 @@ -1640,7 +1640,7 @@ DEFUN (genpath, args, , DEFUN (genpath, args, , "-*- texinfo -*-\n\ @deftypefn {Built-in Function} {} genpath (@var{dir})\n\ -Return a path constructed from @var{dir} and all its subdiretories.\n\ +Return a path constructed from @var{dir} and all its subdirectories.\n\ @end deftypefn") { octave_value retval; diff -r f1a1f6dd7fac -r 30cafefacf83 src/octave.cc --- a/src/octave.cc Fri Jun 20 23:38:44 2008 +0200 +++ b/src/octave.cc Thu Jun 26 23:05:09 2008 +0300 @@ -913,7 +913,7 @@ DEFUN (program_name, args, , DEFUN (program_name, args, , "-*- texinfo -*-\n\ @deftypefn {Built-in Function} {} program_name ()\n\ -Return the last component of of the value returned by\n\ +Return the last component of the value returned by\n\ @code{program_invocation_name}.\n\ @seealso{program_invocation_name}\n\ @end deftypefn") diff -r f1a1f6dd7fac -r 30cafefacf83 src/variables.cc --- a/src/variables.cc Fri Jun 20 23:38:44 2008 +0200 +++ b/src/variables.cc Thu Jun 26 23:05:09 2008 +0300 @@ -2282,7 +2282,7 @@ Clears the variables that don't match th Clears the variables that don't match the following pattern.\n\ \n\ @item -functions, -f\n\ -Clears the function names and the built-in symbols names.\n\ +Clears the function names and the built-in symbol names.\n\ @item -global, -g\n\ Clears the global symbol names.\n\ @item -variables, -v\n\ @@ -2291,7 +2291,7 @@ The arguments are treated as regular exp The arguments are treated as regular expressions as any variables that\n\ match will be cleared.\n\ @end table\n\ -With the execption of @code{exclusive}, all long options can be used \n\ +With the exception of @code{exclusive}, all long options can be used \n\ without the dash as well.\n\ @end deffn") { _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave |
| Free Forum Powered by Nabble | Forum Help |