Mercurial > hg > octave-nkf
changeset 8481:00df69d7e698
[docs] capitalize Octave consistently
author | Brian Gough <bjg@gnu.org> |
---|---|
date | Tue, 13 Jan 2009 00:25:40 -0500 |
parents | 8ae26422a6ce |
children | ab51abf62698 |
files | doc/interpreter/eval.txi doc/interpreter/install.txi doc/interpreter/testfun.txi doc/interpreter/var.txi scripts/testfun/demo.m scripts/testfun/test.m |
diffstat | 6 files changed, 7 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/interpreter/eval.txi +++ b/doc/interpreter/eval.txi @@ -171,7 +171,7 @@ which evaluates @samp{code} in the caller's context and checks that the error message it produces matches the given pattern. Other examples such as @code{save} and @code{load} -are written in C++ where all octave variables +are written in C++ where all Octave variables are in the @samp{caller} context and @code{evalin} is not needed. @DOCSTRING(evalin)
--- a/doc/interpreter/install.txi +++ b/doc/interpreter/install.txi @@ -215,7 +215,7 @@ @item Once you have successfully compiled Octave, run @samp{make install}. -This will install a copy of octave, its libraries, and its documentation +This will install a copy of Octave, its libraries, and its documentation in the destination directory. As distributed, Octave is installed in the following directories. In the table below, @var{prefix} defaults to @file{/usr/local}, @var{version} stands for the current version number
--- a/doc/interpreter/testfun.txi +++ b/doc/interpreter/testfun.txi @@ -36,7 +36,7 @@ @code{test} scans the named script file looking for lines which start with @code{%!}. The prefix is stripped off and the rest of the -line is processed through the octave interpreter. If the code +line is processed through the Octave interpreter. If the code generates an error, then the test is said to fail. Since @code{eval()} will stop at the first error it encounters, you must @@ -285,7 +285,7 @@ but then the code will have to be on the load path and the user will have to remember to type test('name.cc'). Conversely, you -can separate the tests from normal octave script files by putting +can separate the tests from normal Octave script files by putting them in plain files with no extension rather than in script files. @c DO I WANT TO INCLUDE THE EDITOR SPECIFIC STATEMENT BELOW??? @c Don't forget to tell emacs that the plain text file you are using
--- a/doc/interpreter/var.txi +++ b/doc/interpreter/var.txi @@ -226,7 +226,7 @@ @end example The behavior of persistent variables is equivalent to the behavior of -static variables in C. The command @code{static} in octave is also +static variables in C. The command @code{static} in Octave is also recognized and is equivalent to @code{persistent}. Like global variables, a persistent variable may only be initialized once.
--- a/scripts/testfun/demo.m +++ b/scripts/testfun/demo.m @@ -25,7 +25,7 @@ ## from the usual script code, all lines are prefixed by @code{%!}. Each ## example is introduced by the keyword 'demo' flush left to the prefix, ## with no intervening spaces. The remainder of the example can contain -## arbitrary octave code. For example: +## arbitrary Octave code. For example: ## ## @example ## %!demo
--- a/scripts/testfun/test.m +++ b/scripts/testfun/test.m @@ -47,7 +47,7 @@ ## ## The argument @var{fid} can be used to allow batch processing. Errors ## can be written to the already open file defined by @var{fid}, and -## hopefully when octave crashes this file will tell you what was happening +## hopefully when Octave crashes this file will tell you what was happening ## when it did. You can use @code{stdout} if you want to see the results as ## they happen. You can also give a file name rather than an @var{fid}, in ## which case the contents of the file will be replaced with the log from