Menu
▾
▴
[Plplot-cvs] SF.net SVN: plplot:[12521] trunk/doc/docbook/src
|
From: <ai...@us...> - 2013-09-24 05:21:21
|
Revision: 12521
http://sourceforge.net/p/plplot/code/12521
Author: airwin
Date: 2013-09-24 05:21:15 +0000 (Tue, 24 Sep 2013)
Log Message:
-----------
A large number of spelling fixes generated by "aspell check <filename>".
Modified Paths:
--------------
trunk/doc/docbook/src/ada.xml
trunk/doc/docbook/src/advanced.xml
trunk/doc/docbook/src/api-c.xml
trunk/doc/docbook/src/api-compat.xml
trunk/doc/docbook/src/api.xml
trunk/doc/docbook/src/bibliography.xml
trunk/doc/docbook/src/c.xml
trunk/doc/docbook/src/cplus.xml
trunk/doc/docbook/src/deploying.xml
trunk/doc/docbook/src/drivers.xml
trunk/doc/docbook/src/intro.xml
trunk/doc/docbook/src/libraries.xml
trunk/doc/docbook/src/ocaml.xml
trunk/doc/docbook/src/simple.xml
trunk/doc/docbook/src/tcl.xml
trunk/doc/docbook/src/wish.xml
Modified: trunk/doc/docbook/src/ada.xml
===================================================================
--- trunk/doc/docbook/src/ada.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/ada.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -100,7 +100,7 @@
<para>Many of the comments from the C source header file (similar in
purpose to an Ada specification file) have been retained in the thin
- binding, even when they are no longer sensical. These might be pruned at
+ binding, even when they are no longer make sense. These might be pruned at
some point to facilitate reading the Ada source.</para>
<para>Also included in the thin binding are some other declarations
@@ -229,7 +229,7 @@
<para>An important part of the Ada bindings is the examples, some 30 of
which demonstrate how to use many of the features of the PLplot package.
- These examples also serve as a testbed for the bindings in Ada and other
+ These examples also serve as a test bed for the bindings in Ada and other
languages by checking the Postscript files that are generated by each
example against those generated by the C versions. These examples have
been completely re-written in Ada (but retain a C flavor in the names that
@@ -326,11 +326,11 @@
requiring the user program to <literal>with</literal>
<literal>Ada.Numerics.Long_Real_Arrays</literal> simply to gain access
to these types and in the process require linking to the BLAS and LAPACK
- numerics libraries.</para>
+ numerical libraries.</para>
<para>For users who wish to either attain compatibility with Ada 2005
Annex G.3 or to access its features which actually depend on BLAS and
- LAPACK, there are two routes. One is to build PLpot normally and then to
+ LAPACK, there are two routes. One is to build PLplot normally and then to
edit <literal>PLplot_Auxiliary.ads</literal> as is indicated in that
file. This is a very simple process requiring commenting two lines and
uncommenting three lines. Then recompile only the Ada bindings and use
@@ -338,7 +338,7 @@
to type-convert the <literal>Real_Vector</literal> and
<literal>Real_Matrix</literal> objects in the user program so that they
are compatible with the declarations of Annex G.3 when accessing the
- numerics functionality in that annex. (In GNAT, the relevant file is
+ numerical functionality in that annex. (In GNAT, the relevant file is
<literal>a-nlrear.ads</literal>.)</para>
<para>This policy was changed in SVN version 11153. Before this, the
@@ -369,8 +369,8 @@
<para>Pragma Warnings (Off, "some text") and Pragma Warnings (On, "some
text") are used in the bindings to suppress warnings about a particular
- method used to intereface with C code. These pragmas are also used in
- Ada Exaamples 21 to suppress a particular warning. Pragma Warnings is a
+ method used to interface with C code. These pragmas are also used in
+ Ada Examples 21 to suppress a particular warning. Pragma Warnings is a
GNAT extension. Non-GNAT usage could simply remove these pragmas with
the resulting warnings ignored as they are benign.</para>
@@ -473,7 +473,7 @@
<literal>Draw_On_Black</literal>. Each of these manipulates color
map 0 by swapping black and white so that e.g.with
<literal>Draw_On_White</literal>, formerly white lines on a black
- background autotmatically become black lines on a white
+ background automatically become black lines on a white
background.</para>
</sect4>
</sect3>
@@ -490,7 +490,7 @@
<title>Multiplot_Pairs</title>
<para>Plot up to five <emphasis>x-y</emphasis> pairs with easy
- labeling, coloring, line width and styles, justification, and
+ labelling, coloring, line width and styles, justification, and
zooming.</para>
</sect4>
@@ -498,7 +498,7 @@
<title>Simple_Plot</title>
<para>Plot up to five <emphasis>y</emphasis>'s against a single
- <emphasis>x</emphasis> with easy labeling and automatic line colors
+ <emphasis>x</emphasis> with easy labelling and automatic line colors
and styles.</para>
</sect4>
@@ -527,7 +527,7 @@
<title>Simple_Plot_Pairs</title>
<para>Plot up to five <emphasis>x</emphasis>-<emphasis>y</emphasis>
- pairs with easy labeling and automatic line colors and
+ pairs with easy labelling and automatic line colors and
styles.</para>
</sect4>
@@ -566,7 +566,7 @@
<para>PLplot provides extensive manipulation and control of two
separate color maps, color map 0 and color map 1. The Ada binding
makes basic manipulations easier and also adds facilities for making
- snapshots of color map 0 so that any state of the map can easlily be
+ snapshots of color map 0 so that any state of the map can easily be
restored later. An initial snapshot is taken when the package is
initialized so that the default color settings can always be restored
after having been changed.</para>
@@ -803,7 +803,7 @@
<para>The custom label function <literal>Set_Custom_Label</literal>
(<literal>plslabelfunc</literal> in the traditional binding) can be
- called with null arguments to revert to using the default labeling
+ called with null arguments to revert to using the default labelling
scheme. Alternately, an Ada-only procedure with no arguments,
<literal>Use_Default_Labels</literal>, is provided. See Ada example 19
(<literal>x19a.adb</literal> or <literal>xthick19a.adb</literal>) for a
@@ -814,7 +814,7 @@
(<literal>plstransform</literal> in the traditional binding) can be
called with null arguments to clear any previous custom coordinate
transforms that the user has set, thus reverting to the default
- coordinate transform. Alternately, an Ada-only procdure with no
+ coordinate transform. Alternately, an Ada-only procedure with no
arguments, <literal>Clear_Custom_Coordinate_Transform</literal>, is
provided. See Ada example 19 (<literal>x19a.adb</literal> or
<literal>xthick19a.adb</literal>) for a usage example.</para>
@@ -887,7 +887,7 @@
<para>As discussed in Section 6.1, the bindings are made to work with
Ada 95 and Ada 2005, but special steps need to be taken in order to
- access the numerics capabilities of Ada 2005 to the extent that vectors
+ access the numerical capabilities of Ada 2005 to the extent that vectors
and arrays of the type defined in the Ada Reference Manual Annex G.3 are
required to be passed to PLplot routines.</para>
</sect2>
@@ -906,7 +906,7 @@
and <literal>PLplot_Auxiliary.adb</literal>. These files are currently
used to provide a few convenience subprograms that are used in the
examples. However, they are also associated with the above-mentioned
- facility to easily accommodate acessing the G.3 Annex vector-matrix
+ facility to easily accommodate accessing the G.3 Annex vector-matrix
manipulation facilities. If not for the desire for this easy "switching"
ability, the <literal>PLplot_Auxiliary</literal> package could be
removed from the <literal>with</literal> parts of the other binding
Modified: trunk/doc/docbook/src/advanced.xml
===================================================================
--- trunk/doc/docbook/src/advanced.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/advanced.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -664,7 +664,7 @@
</para>
<para>
- Additional startup routines &plstar; and &plstart; are available but
+ Additional start up routines &plstar; and &plstart; are available but
these are simply front-ends to &plinit;, and should be avoided. It
is preferable to call &plinit; directly, along with the appropriate
setup calls, for the greater amount of control this provides (see the
@@ -791,13 +791,13 @@
</sect2>
<sect2>
- <title>Initialise FreeType</title>
+ <title>Initialize FreeType</title>
- <para>Next, we have to initialise the FreeType library. For the
+ <para>Next, we have to initialize the FreeType library. For the
<filename>gd.c</filename> driver this is done via two separate functions due
- to the order that dependent information is initialised in the driver.</para>
+ to the order that dependent information is initialized in the driver.</para>
- <para>The "level 1" initialisation of FreeType does two things: 1) calls
+ <para>The "level 1" initialization of FreeType does two things: 1) calls
<literal>plD_FreeType_init(pls)</literal>, which in turn allocates memory to
the pls->FT structure; and 2) stores the location of the call back routine.
</para>
@@ -817,7 +817,7 @@
</programlisting>
</para>
- <para>This initialisation routine is called at the end of
+ <para>This initialization routine is called at the end of
<literal>plD_init_png_Dev(PLStream *pls)</literal> in the
<filename>gd.c</filename> driver:</para>
@@ -845,7 +845,7 @@
smoothing. Since there is nothing in PLStream to track smoothing, we have to
set the FT->smooth_text flag as well at this time.</para>
- <para>The "level 2" initialisation function initialises everything else
+ <para>The "level 2" initialization function initializes everything else
required for using the FreeType library but has to be called after the
screen resolution and dpi have been set. Therefore, it is called at the end
of <literal>plD_init_png()</literal>, where it looks like:
@@ -902,7 +902,7 @@
<para>Some coordinate systems have zero on the bottom, others have zero on
the top. FreeType does it one way, and most everything else does it the
- other. To make sure everything is working ok, we have to "flip" the
+ other. To make sure everything is working OK, we have to "flip" the
coordinates, and to do this we need to know how big in the Y dimension the
page is, and whether we have to invert the page or leave it alone.</para>
@@ -1416,7 +1416,7 @@
current color (as opposed to the background color) at any point in the
plot by selecting any of the colors from either color map 0 or 1 using
calls to &plcol0; or &plcol1;. When the current color is changed all
- subsequent drawing actions will utilise the new color until it is
+ subsequent drawing actions will utilize the new color until it is
changed again.
</para>
@@ -1479,7 +1479,7 @@
<para> There is a one-to-one correspondence between RGB and HLS color
spaces. RGB space is characterized by three 8-bit unsigned integers
corresponding to the intensity of the red, green, and blue colors. Thus,
- in hexidecimal notation with the 3 bytes concatanated together the RGB
+ in hexadecimal notation with the 3 bytes concatenated together the RGB
values of FF0000, FFFF00, 00FF00, 00FFFF, 0000FF, FF00FF, 000000, and
FFFFFF correspond to red, yellow, green, cyan, blue, magenta, black, and
white. </para>
@@ -1504,7 +1504,7 @@
<para> Here are some C-code fragments which use &plscmap1l; to set the
map1 color palette. This first example illustrates how to set up a
- gray-scale pallette using linear interpolation in RGB space.
+ gray-scale palette using linear interpolation in RGB space.
<programlisting> i[0] = 0.;
i[1] = 1.;
@@ -1537,7 +1537,7 @@
</para>
<para> This final example using &plscmap1l; illustrates how the default
- map1 color pallette is set with just 4 control points (taken from
+ map1 color palette is set with just 4 control points (taken from
<filename>src/plctrl.c</filename>).
<programlisting>/*--------------------------------------------------------------------------*\
@@ -1565,7 +1565,7 @@
i[3] = 1; /* right boundary */
/* For center control points, pick black or white, whichever is closer to bg */
- /* Be carefult to pick just short of top or bottom else hue info is lost */
+ /* Be careful to pick just short of top or bottom else hue info is lost */
if (plsc->cmap0 != NULL)
vertex = ((float) plsc->cmap0[0].r +
@@ -1607,7 +1607,7 @@
&plscmap1; so it is the programmer's responsibility to make sure that
the colors vary smoothly. Here is an example of the method taken from
<filename>examples/c/x08c.c</filename> which sets (yet again) the
- gray-scale color pallette.
+ gray-scale color palette.
<programlisting> for (i=0;i<n_col;i++)
rr[i] = gg[i] = bb[i] = i*256/n_col;
@@ -2455,11 +2455,11 @@
</para>
<para>
- Labeling a three-dimensional or mesh plot is somewhat more
+ Labelling a three-dimensional or mesh plot is somewhat more
complicated than a two dimensional plot due to the need for skewing
the characters in the label so that they are parallel to the
coordinate axes. The routine &plbox3; thus combines the functions of
- box drawing and labeling.
+ box drawing and labelling.
</para>
</sect1>
@@ -2778,7 +2778,7 @@
plot and typically identifying certain colors with certain numerical
values using an axis). &pllegend; is useful for visually annotating
most two-dimensional plots. See standard examples 4 and 26 for some
- examples. &plcolorbar; is especially useful for annotating continous
+ examples. &plcolorbar; is especially useful for annotating continuous
shade plots generated by &plshades;. See standard example 16 for an
example.
</para>
Modified: trunk/doc/docbook/src/api-c.xml
===================================================================
--- trunk/doc/docbook/src/api-c.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/api-c.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -40,7 +40,7 @@
<title>The Specialized C API for PLplot</title>
<para>
- The purpose of this chapter is to document the PLPlot C functions that are
+ The purpose of this chapter is to document the PLplot C functions that are
currently not part of the common API,
either because they are C/C++ specific utility
functions (e.g. &plAlloc2dGrid;, &plFree2dGrid;) or because they are not
@@ -636,7 +636,7 @@
<para>
Resets the internal command line options table to the default
- builtin value. Any user options added with &plMergeOpts; will be
+ built in value. Any user options added with &plMergeOpts; will be
cleared. See &plparseopts; for details of how to parse these
options in a program.
</para>
@@ -952,7 +952,7 @@
<sect1 id="pltr1" renderas="sect3">
<title>
<function>pltr1</function>: Linear interpolation for grid to world
- mapping using singly dimensioned coord arrays
+ mapping using singly dimensioned coordinate arrays
</title>
<para>
@@ -972,7 +972,7 @@
<para>
Linear interpolation for grid to world mapping using singly
- dimensioned coord arrays.
+ dimensioned coordinate arrays.
This routine can be used both for &plcont; and &plshade;.
See also <xref linkend="contour-plots-c"/> and
<xref linkend="shade-plots-c"/>.
@@ -1052,7 +1052,7 @@
<sect1 id="pltr2" renderas="sect3">
<title>
<function>pltr2</function>: Linear interpolation for grid to world
- mapping using doubly dimensioned coord arrays (column
+ mapping using doubly dimensioned coordinate arrays (column
dominant, as per normal C 2d arrays)
</title>
@@ -1073,7 +1073,7 @@
<para>
Linear interpolation for grid to world mapping using doubly
- dimensioned coord arrays (column dominant, as per normal C 2d arrays).
+ dimensioned coordinate arrays (column dominant, as per normal C 2d arrays).
This routine can be used both for &plcont; and &plshade;.
See also <xref linkend="contour-plots-c"/> and
<xref linkend="shade-plots-c"/>.
Modified: trunk/doc/docbook/src/api-compat.xml
===================================================================
--- trunk/doc/docbook/src/api-compat.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/api-compat.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -91,7 +91,7 @@
<para>
Since PLplot is developed by so many people, the task of checking for
- backwards compatiblity of the library is very hard. As for the 5.3.1
+ backwards compatibility of the library is very hard. As for the 5.3.1
release, we do not have any rigorous regression test for check
whether the library is really backwards compatible.
</para>
@@ -104,7 +104,7 @@
<para>
Check if there are any changes in
<filename>plplot.h</filename>. If no prototype is changed,
- then the chances are high that no backwards compatibilities
+ then the chances are high that no backwards incompatibilities
have been introduced. If new functions has been added, then
the library soname will be kept, although the soversion
strings in <filename>cmake/module/plplot_version.cmake</filename>
Modified: trunk/doc/docbook/src/api.xml
===================================================================
--- trunk/doc/docbook/src/api.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/api.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -52,8 +52,8 @@
</para>
<para>
- What follows is a list of all common API functions of the current
- CVS HEAD with their arguments except for obsolete/deprecated API
+ What follows is a list of all common API functions of the latest
+ PLplot version with their arguments except for obsolete/deprecated API
functions which are listed in <xref linkend="API-OBSOLETE"/>. The
following information is provided for each function:
<orderedlist>
@@ -632,9 +632,9 @@
</listitem>
<listitem>
<para>
- <literal>o</literal>: Use custom labeling function to
- generate axis label text. The custom labeling function
- can be defined with the plslabelfuncplslabelfunc; command.
+ <literal>o</literal>: Use custom labelling function to
+ generate axis label text. The custom labelling function
+ can be defined with the &plslabelfunc; command.
</para>
</listitem>
<listitem>
@@ -1072,9 +1072,9 @@
</listitem>
<listitem>
<para>
- <literal>o</literal>: Use custom labeling function to
- generate axis label text. The custom labeling function
- can be defined with the plslabelfuncplslabelfunc; command.
+ <literal>o</literal>: Use custom labelling function to
+ generate axis label text. The custom labelling function
+ can be defined with the &plslabelfunc; command.
</para>
</listitem>
<listitem>
@@ -1290,9 +1290,9 @@
</listitem>
<listitem>
<para>
- <literal>o</literal>: Use custom labeling function to
- generate axis label text. The custom labeling function
- can be defined with the plslabelfuncplslabelfunc; command.
+ <literal>o</literal>: Use custom labelling function to
+ generate axis label text. The custom labelling function
+ can be defined with the &plslabelfunc; command.
</para>
</listitem>
<listitem>
@@ -1472,9 +1472,9 @@
</listitem>
<listitem>
<para>
- <literal>o</literal>: Use custom labeling function to
- generate axis label text. The custom labeling function
- can be defined with the plslabelfuncplslabelfunc; command.
+ <literal>o</literal>: Use custom labelling function to
+ generate axis label text. The custom labelling function
+ can be defined with the &plslabelfunc; command.
</para>
</listitem>
<listitem>
@@ -1676,7 +1676,7 @@
and possibly more than one window (set of world coordinates) per
viewport, <literal><parameter>window</parameter></literal>
and the corresponding output world coordinates
- corresponds to the last window created that fulfils the criterion
+ corresponds to the last window created that fulfills the criterion
that the relative device coordinates are inside it. Finally, in
all cases where the input relative device coordinates are not
inside any viewport/window, then
@@ -6557,7 +6557,7 @@
</term>
<listitem>
<para>
- Plot coordinates to strecth the image data to. idata[0][0]
+ Plot coordinates to stretch the image data to. idata[0][0]
corresponds to (xmin, ymin) and idata[nx - 1][ny - 1] corresponds
to (xmax, ymax).
</para>
@@ -8207,7 +8207,7 @@
<para>
<literal><parameter>opt</parameter>=MAG_COLOR</literal>: Each line
in the mesh is colored according to the z value being plotted. The
- color is used from the current colormap 1.
+ color is used from the current color map 1.
</para>
</listitem>
<listitem>
@@ -13434,8 +13434,8 @@
<listitem>
<para>
This is the custom label function. In order to reset to the
- default labeling, set this to <literal>NULL</literal>.
- The labeling function parameters are, in order:
+ default labelling, set this to <literal>NULL</literal>.
+ The labelling function parameters are, in order:
<variablelist>
<varlistentry>
<term><parameter>axis</parameter></term>
@@ -13452,7 +13452,7 @@
<term><parameter>value</parameter></term>
<listitem>
<para>
- This is the value along the axis which is being labeled.
+ This is the value along the axis which is being labelled.
</para>
</listitem>
</varlistentry>
@@ -14325,7 +14325,7 @@
desired output device must be supplied as an argument. The device
keywords are the same as those printed out by &plstar;. If the
requested device is not available, or if the input string is empty or
- begins with ``?'', the prompted startup of &plstar; is used. This
+ begins with ``?'', the prompted start up of &plstar; is used. This
routine also divides the output device into
<literal><parameter>nx</parameter></literal> by
<literal><parameter>ny</parameter></literal> subpages, each of which
@@ -14343,7 +14343,7 @@
<para>
Device name (keyword) of the required output device. If NULL
or if the first character is a ``?'', the normal (prompted)
- startup is used.
+ start up is used.
</para>
</listitem>
</varlistentry>
@@ -14433,7 +14433,7 @@
<listitem>
<para>
Pointer to a function that defines a transformation from the
- input (x, y) coordinate to a new plot world coordiante.
+ input (x, y) coordinate to a new plot world coordinate.
</para>
</listitem>
</varlistentry>
@@ -14668,7 +14668,7 @@
<sect1 id="plstripa" renderas="sect3">
<title>
- <function>plstripa</function>: Add a point to a stripchart
+ <function>plstripa</function>: Add a point to a strip chart
</title>
<para>
@@ -14686,7 +14686,7 @@
</para>
<para>
- Add a point to a given pen of a given stripchart.
+ Add a point to a given pen of a given strip chart.
There is no need for all pens to have the same number of
points or to be equally sampled in the x coordinate.
Allocates memory and rescales as
@@ -14701,7 +14701,7 @@
</term>
<listitem>
<para>
- Identification number (set up in &plstripc;) of the stripchart.
+ Identification number (set up in &plstripc;) of the strip chart.
</para>
</listitem>
</varlistentry>
@@ -14752,7 +14752,7 @@
<sect1 id="plstripc" renderas="sect3">
<title>
- <function>plstripc</function>: Create a 4-pen stripchart
+ <function>plstripc</function>: Create a 4-pen strip chart
</title>
<para>
@@ -14786,7 +14786,7 @@
</para>
<para>
- Create a 4-pen stripchart, to be used afterwards by &plstripa;
+ Create a 4-pen strip chart, to be used afterwards by &plstripa;
</para>
<variablelist>
@@ -14797,7 +14797,7 @@
</term>
<listitem>
<para>
- Identification number of stripchart to use on &plstripa; and &plstripd;.
+ Identification number of strip chart to use on &plstripa; and &plstripd;.
</para>
</listitem>
</varlistentry>
@@ -15047,7 +15047,7 @@
<sect1 id="plstripd" renderas="sect3">
<title>
<function>plstripd</function>: Deletes and releases memory used by a
- stripchart
+ strip chart
</title>
<para>
@@ -15062,7 +15062,7 @@
</para>
<para>
- Deletes and releases memory used by a stripchart.
+ Deletes and releases memory used by a strip chart.
</para>
<variablelist>
@@ -15073,7 +15073,7 @@
</term>
<listitem>
<para>
- Identification number of stripchart to delete.
+ Identification number of strip chart to delete.
</para>
</listitem>
</varlistentry>
Modified: trunk/doc/docbook/src/bibliography.xml
===================================================================
--- trunk/doc/docbook/src/bibliography.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/bibliography.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -1,6 +1,6 @@
<!-- -*- mode: nxml -*- -->
<!--
- bilbiograpy.xml: "Bibliography" chapter
+ bibliography.xml: "Bibliography" chapter
Copyright (C) 1994 Geoffrey Furnish and Maurice LeBrun
Copyright (C) 1999, 2000, 2001, 2002, 2003 Alan W. Irwin and Rafael Laboissiere
Modified: trunk/doc/docbook/src/c.xml
===================================================================
--- trunk/doc/docbook/src/c.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/c.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -118,11 +118,11 @@
<para>
The one additional complicating factor concerns the use of stub routines to
interface with Fortran (see the following section for more explanation). On
- some systems, the Fortran and C namespaces are set up to clobber each other.
+ some systems, the Fortran and C name spaces are set up to clobber each other.
More reasonable (from our viewpoint) is to agree on a standard map between
- namespaces, such as the appending of an underscore to Fortran routine names
+ name spaces, such as the appending of an underscore to Fortran routine names
as is common on many Unix-like systems. The only case where the shared
- Fortran/C namespaces do any good is when passing a pointer to a like data
+ Fortran/C name spaces do any good is when passing a pointer to a like data
type, which represents only a small fraction of the cases that need to
be handled (which includes constant values passed on the stack, strings, and
two-dimensional arrays).
Modified: trunk/doc/docbook/src/cplus.xml
===================================================================
--- trunk/doc/docbook/src/cplus.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/cplus.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -190,7 +190,7 @@
<para>
The <literal>plstream</literal> class will provide an abstract interface to the
2-d drawing functions. Instead of forcing the C++ user to organize
- data in one of a small set of generally braindead data layouts with
+ data in one of a small set of generally brain dead data layouts with
poor memory management properties, potentially forcing the C++ user to
not use a superior method, or to copy data computed in one layout
format to another for plotting (with consequent bug production), the
Modified: trunk/doc/docbook/src/deploying.xml
===================================================================
--- trunk/doc/docbook/src/deploying.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/deploying.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -54,7 +54,7 @@
environment that you use, but that is in general only an option if your
user is comfortable with making programs themselves. A more common
situation is that your user just wants the executable programs and
- wants to get using them rightaway. We will focus on this particular
+ wants to get using them right away. We will focus on this particular
solution, as there are a few non-trivial issues.
</para>
@@ -306,7 +306,7 @@
</para>
<para>
- To summarise the case where you don't have a deb or rpm option, and
+ To summarize the case where you don't have a deb or rpm option, and
you must use inconsistent install locations on your users' machines:
<itemizedlist>
<listitem>
@@ -369,7 +369,7 @@
<envar>LD_LIBRARY_PATH</envar> and equivalents, can be set within
the program (by using a small configuration file or by determining the
position of the files relative to the program's location). They just
- have be set before PLplot is initialised.
+ have be set before PLplot is initialized.
</para>
</chapter>
Modified: trunk/doc/docbook/src/drivers.xml
===================================================================
--- trunk/doc/docbook/src/drivers.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/drivers.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -59,7 +59,7 @@
<para>
Plots are displayed one page at a time. The pager is advanced by
- pressing the Enter key, and may only be advanced in the foreward
+ pressing the Enter key, and may only be advanced in the forward
direction.
</para>
@@ -206,7 +206,7 @@
The available driver options are:
<itemizedlist>
<listitem><para>
- optimise: Optimise PNG palette when possible
+ optimize: Optimize PNG palette when possible
</para></listitem>
<listitem><para>
def_black15: Define idx 15 as black. If the background is
@@ -241,7 +241,7 @@
is based on the libharu library see:
<ulink url="http://libharu.sourceforge.net/">
http://libharu.sourceforge.net/</ulink>.
- At present only the hershey fonts are used and there is no support for
+ At present only the Hershey fonts are used and there is no support for
pdf or ttf fonts. Compression of the pdf output is not enabled and the
paper size can't be chosen. All these issues will be addressed in
later releases.
Modified: trunk/doc/docbook/src/intro.xml
===================================================================
--- trunk/doc/docbook/src/intro.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/intro.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -74,7 +74,7 @@
package. Sze Tan writes:
<blockquote>
<para>
- I'm rather amazed how far PLPLOT has traveled given its origins
+ I'm rather amazed how far PLPLOT has travelled given its origins
etc. I first used PGPLOT on the Starlink VAX computers while I was
a graduate student at the Mullard Radio Astronomy Observatory in
Cambridge from 1983-1987. At the beginning of 1986, I was to give a
@@ -86,7 +86,7 @@
able to draw a line or a dot on the screen in order to do arbitrary
graphics. The application programmer's interface was made as
similar as possible to PGPLOT so that I could easily port my
- programs from the VAX to the PC. The kernel of PLPLOT was modeled
+ programs from the VAX to the PC. The kernel of PLPLOT was modelled
on PGPLOT but the code is not derived from it.
</para>
</blockquote>
@@ -127,7 +127,7 @@
several new routines to enhance usage from Fortran and design of a
portable C to Fortran interface. Additional support was added for
coordinate mappings in contour plots and some bugs fixed. New
- labeling options were added. The font handling code was made more
+ labelling options were added. The font handling code was made more
flexible and portable. A portable PLplot metafile driver and
renderer was developed, allowing one to create a generic graphics
file and do the actual rendering later (even on a different
@@ -161,7 +161,7 @@
<para>
We welcome suggestions on how to improve this code, especially in
the form of user-contributed enhancements or bug fixes. If PLplot
- is used in any published papers, please include an acknowledgment
+ is used in any published papers, please include an acknowledgement
or citation of our work, which will help us to continue improving
PLplot. Please direct all communication to the general PLplot
mailing list, plp...@li....
@@ -175,7 +175,7 @@
the PLplot is by electronic transmission over the Internet. We
encourage others to make it available to users without Internet
access. PLplot is a SourceForge project and may be obtained by
- the usual SourceForge file release and anonymous cvs access that is made
+ the usual SourceForge file release and anonymous svn repository access that is made
available from links at
<ulink url="http://sourceforge.net/projects/plplot">http://sourceforge.net/projects/plplot</ulink>.
</para>
@@ -296,7 +296,7 @@
<sect2 id="additional-copyrights">
<title>Additional Copyrights</title>
<para>
- The startup code used in argument handling
+ The start up code used in argument handling
(<filename>utils/plrender.c</filename> and
<filename>src/plargs.c</filename>) is partially derived from
<filename>xterm.c</filename> of the X11R5 distribution, and its
Modified: trunk/doc/docbook/src/libraries.xml
===================================================================
--- trunk/doc/docbook/src/libraries.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/libraries.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -183,7 +183,7 @@
these limitations are not acceptable for plotting of scientific time
series and are addressed by the qsastime library which was originally
donated under the LGPL to the PLplot project in early 2009 by Anthony
- J. Allen of the QSAS team and substantially modifed after that by a
+ J. Allen of the QSAS team and substantially modified after that by a
PLplot developer, Alan W. Irwin (e.g., to add leap-second
functionality).
</para>
Modified: trunk/doc/docbook/src/ocaml.xml
===================================================================
--- trunk/doc/docbook/src/ocaml.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/ocaml.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -147,7 +147,7 @@
<para>
An important part of the OCaml bindings is the examples, some 31 of
which demonstrate how to use many of the features of the PLplot package.
- These examples also serve as a testbed for the bindings in OCaml and
+ These examples also serve as a test bed for the bindings in OCaml and
other languages by checking the Postscript files that are generated by
each example against those generated by the C versions. These examples
have been completely re-written in OCaml (but retain a C flavor in their
@@ -167,7 +167,7 @@
<title>Obtaining the OCaml compiler</title>
<para>
You will need the OCaml compiler in order to build and use the OCaml
- PLplot bindings. OCaml includes both a bytecode compiler (ocamlc) and
+ PLplot bindings. OCaml includes both a byte code compiler (ocamlc) and
a native code compiler (ocamlopt). Both of these are supported by
PLplot.
</para>
@@ -199,7 +199,7 @@
<ulink url="http://projects.camlcity.org/projects/findlib.html">
findlib
</ulink>
- and its associated tools (ie., ocamlfind) are installed in in your
+ and its associated tools (i.e., ocamlfind) are installed in in your
<literal>$PATH</literal>.
</para>
<para>
Modified: trunk/doc/docbook/src/simple.xml
===================================================================
--- trunk/doc/docbook/src/simple.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/simple.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -232,7 +232,7 @@
<listitem>
<para>
- <parameter>axis</parameter> = 0: Draw box, labeled with
+ <parameter>axis</parameter> = 0: Draw box, labelled with
coordinate values around edge.
</para>
</listitem>
@@ -304,15 +304,15 @@
</para>
<para>
- For greater control over the size of the plots, axis labeling and
+ For greater control over the size of the plots, axis labelling and
tick intervals, more complex graphs should make use of the functions
&plvpor;, &plvasp;, &plvpas;, &plwind;, &plbox;, and routines for
- manipulating axis labeling &plgxax; through &plszax;.
+ manipulating axis labelling &plgxax; through &plszax;.
</para>
</sect1>
<sect1 id="labelling">
- <title>Labeling the Graph</title>
+ <title>Labelling the Graph</title>
<para>
The function &pllab; may be called after &plenv; to write labels on
Modified: trunk/doc/docbook/src/tcl.xml
===================================================================
--- trunk/doc/docbook/src/tcl.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/tcl.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -860,7 +860,7 @@
</para>
<para>
- So, the point is, do your heavy numerics in a compiled language, and
+ So, the point is, do your heavy numerical calculations in a compiled language, and
feel free to use Tcl for the plotting, if you want to. You can of
course mix it up so that some plotting is done from Tcl and some from
a compiled language.
Modified: trunk/doc/docbook/src/wish.xml
===================================================================
--- trunk/doc/docbook/src/wish.xml 2013-09-23 22:07:57 UTC (rev 12520)
+++ trunk/doc/docbook/src/wish.xml 2013-09-24 05:21:15 UTC (rev 12521)
@@ -112,7 +112,7 @@
Having done this, you have essentially created a shell. That is, your
program can now execute shell scripts in the Tcl language. Tcl
provides support for basic control flow, variable substitution file
- i/o and subroutines. In addition to the builtin Tcl commands, you can
+ i/o and subroutines. In addition to the built in Tcl commands, you can
define your own subroutines as Tcl procedures which effectively
become new keywords.
</para>
@@ -480,10 +480,10 @@
/*
- * Specify a user-specific startup file to invoke if the
- * application is run interactively. Typically the startup
+ * Specify a user-specific start up file to invoke if the
+ * application is run interactively. Typically the start up
* file is "~/.apprc" where "app" is the name of the application.
- * If this line is deleted then no user-specific startup file
+ * If this line is deleted then no user-specific start up file
* will be run under any conditions.
*/
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
