Author: sgranjoux
Date: Sun Feb 10 15:46:46 2008
New Revision: 3624
URL: http://svn.gnome.org/viewvc/anjuta?rev=3624&view=rev
Log:
* manuals/anjuta-manual/C/interface.xml,
manuals/anjuta-manual/C/introduction.xml,
manuals/anjuta-manual/C/preferences.xml,
manuals/anjuta-manual/C/fileoperations.xml,
manuals/anjuta-manual/C/projects.xml:
Fix spelling errors, including bug #515204, #515172, #515117
and #513892
Modified:
trunk/ChangeLog
trunk/manuals/anjuta-manual/C/fileoperations.xml
trunk/manuals/anjuta-manual/C/interface.xml
trunk/manuals/anjuta-manual/C/introduction.xml
trunk/manuals/anjuta-manual/C/preferences.xml
trunk/manuals/anjuta-manual/C/projects.xml
Modified: trunk/manuals/anjuta-manual/C/fileoperations.xml
==============================================================================
--- trunk/manuals/anjuta-manual/C/fileoperations.xml (original)
+++ trunk/manuals/anjuta-manual/C/fileoperations.xml Sun Feb 10 15:46:46 2008
@@ -26,7 +26,7 @@
<sect2 id="file-wizard">
<title>File Wizard</title>
<para>
- A wizard can also be used to create a new file.To create a new file,
choose
+ A wizard can also be used to create a new file. To create a new file,
choose
<menuchoice><guisubmenu>File</guisubmenu><guisubmenu>New</guisubmenu>
<guimenuitem>File</guimenuitem></menuchoice> from the menubar.
This will open the New File Wizard dialog. Select the file type. Enter
the File name.
@@ -43,7 +43,7 @@
</figure>
</para>
<para>
- <application>Anjuta</application> occatinally also creates new files
during some
+ <application>Anjuta</application> occasionally also creates new files
during some
operations. For example, some CVS operations, such as diff, file log,
file status
etc, create new files and add the output there. These could be saved
in real file
just like normal new files.
@@ -165,7 +165,7 @@
For selecting multiple files at once,
select a file in the dialog and press CTRL once. This will bring the
file selection
dialog in multiple-select mode and multiple files could be selected
from the list.
- Multiple file select mode is simlar to single file select mode,
except that the file
+ Multiple file select mode is similar to single file select mode,
except that the file
operation (for which the file selection was being done) will be
performed for all
the selected files.
<figure id="open-file-multiple">
@@ -177,10 +177,10 @@
</figure>
</para>
<para>
- The <emphasis>Show Hidden</emphasis>, if switched on (Click right),
will make the hidden
+ The <emphasis>Show Hidden Files</emphasis>, if switched on (Click
right), will make the hidden
files (files starting with "."; visible in the file list. Depress it
to make
- them hide. <application>Anjuta</application> fileselection dialog
also has inbuild
- file type filter. Select the appropiate file type filter in the
dialog and the file
+ them hide. <application>Anjuta</application> file selection dialog
also has inbuilt
+ file type filter. Select the appropriate file type filter in the
dialog and the file
list will be limited to the files of the selected type only.
</para>
</listitem>
@@ -264,7 +264,7 @@
and all of them may not be available when you first start
<application>anjuta</application>.
They are Line numbers margin, Markers margin and Code fold margin.
By default (that is, when you run <application>anjuta</application> for
the first time) only
- the code fold margin witll be visible. The rest could be made visible
from
+ the code fold margin will be visible. The rest could be made visible
from
<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu></menuchoice>.
<figure id="editor-margins">
<title>Editor Margins</title>
@@ -288,7 +288,7 @@
<guimenuitem>Markers Margin</guimenuitem></menuchoice>. This margin
displays graphical icons
to mark the given line. The markers which will be displayed in this
margin are Bookmark marker
(rectangular blue colored icon), Breakpoint marker (circular red
colored) and Line indicator
- (pointed arrow yellow colored). Bookmark marker is used to indicate
bookmaked lines which could
+ (pointed arrow yellow colored). Bookmark marker is used to indicate
bookmarked lines which could
be toggled from
<menuchoice><guimenu>Goto</guimenu><guisubmenu>Bookmark</guisubmenu><guimenuitem>
Toggle Bookmark</guimenuitem></menuchoice>
with the cursor placed in that line. The breakpoint marker is used
in debugger to mark the
@@ -297,7 +297,7 @@
navigating the bookmarks and during single stepping in debugger.
</para>
<para>
- <emphasis>Code folding margin</emphasis> is where the folding tree is
visisble. Clicking
+ <emphasis>Code folding margin</emphasis> is where the folding tree is
visible. Clicking
on these folding tree nodes will fold or unfold the code blocks. An
underline will also
be drawn below the folded line to make it more obvious that a block of
code has been
folded below the line. For more details on code folding, see the
section <emphasis>Code Folding</emphasis>
@@ -309,13 +309,13 @@
If the marker margin is not visible, the markers will be displayed by
changing the
background color of the line. For example, if there a breakpoint
marker is set in
a line and the marker margin is not visible, that line will be
displayed with red
- background. Similarly, for bookmark marker and line indicatior
marker, the background
+ background. Similarly, for bookmark marker and line indication
marker, the background
color of the line will be sky blue and yellow, respectively. If you
do not like this
(perhaps due to some contrasting themes), enable the
<emphasis>Markers Margins</emphasis>
from
<menuchoice><guimenu>View</guimenu><guisubmenu>Editor</guisubmenu>
<guimenuitem>Markers Margin</guimenuitem></menuchoice>.
<figure id="editor-markers">
- <title>Editor markes when markers margin is invisible</title>
+ <title>Editor markers when markers margin is invisible</title>
<screenshot>
<screeninfo>The Tags toolbar</screeninfo>
<graphic fileref="figures/editor_markers.png" format="PNG"
srccredit="naba"></graphic>
@@ -332,7 +332,7 @@
visible or invisible by toggling the menu items in
<menuchoice><guimenu>View</guimenu>
<guisubmenu>Editor</guisubmenu></menuchoice>. Indentation guides are the
small dotted lines
drawn to connect the matching braces in the source code. When the cursor
is over one such
- maching braces, the dotted indentation guide is highlighted to give a
visual region of the
+ matching braces, the dotted indentation guide is highlighted to give a
visual region of the
indentation.
</para>
<figure id="editor-guides">
@@ -372,7 +372,7 @@
</para>
<note>
<para>
- Please note that code folding and editor guides are only avalible in
+ Please note that code folding and editor guides are only available in
the scintilla based editor.
</para>
</note>
@@ -398,14 +398,14 @@
All C and C++ source and header files can be browsed using the tags in the
files.
All of the open C and C++ source and header files are scanned for
available tags
(a "tag" refers to a function definition, structure, macro, etc.).
Please note that
- Tag and Symbol is used synonymously in this manual, except when refering
to Tags
+ Tag and Symbol is used synonymously in this manual, except when referring
to Tags
browser and Symbol browser, which two different interfaces.
</para>
<orderedlist>
<listitem>
<para><emphasis>Tags Browser:</emphasis> Tags browser is available on
the
Browser toolbar. It shows a list of tags available in the currently
active
- file (souce file). If there is no tags (or sysmbols) available in the
file,
+ file (source file). If there is no tags (or symbols) available in the
file,
the tags list will be invisible and a "No Tags" will be displayed
instead. The tags
in this list are shown along with the line numbers where they are found.
If there are
multiple symbols with the same name, they will be shown with different
line numbers.
@@ -418,7 +418,7 @@
</figure>
<tip><title>Function symbols</title>
<para>Function prototype and definition, if present in the same file,
can be usually
- distinguished from the corrosponding line numbers. Prototypes usually
comes before the
+ distinguished from the corresponding line numbers. Prototypes usually
comes before the
definition, so they are likely to have smaller line numbers.
</para>
</tip>
@@ -495,7 +495,7 @@
</para>
<para>
If the "Basic Search" option is selected in the Setting window,
- the search direction can be choosen from the Expression window.
+ the search direction can be chosen from the Expression window.
</para>
<figure id="search-expr-basic">
<title>Basic Search Text dialog</title>
@@ -561,7 +561,7 @@
</para>
<para>
According to the previous selections (Search in, Search direction ...),
- some actions coul be unavailable.
+ some actions could be unavailable.
</para>
<figure id="search-target-action">
<title>Search Target Action choice</title>
@@ -597,7 +597,7 @@
The user has the possibility of saving the setting of his search
options.
</para>
<para>
- Item highlighted in red is the active item. Item by defaultt is the
search
+ Item highlighted in red is the active item. Item by default is the
search
setting which is loaded at Anjuta launching.
</para>
<figure id="search-setting-fig">
@@ -617,10 +617,9 @@
Print preview could be taken by selecting
<menuchoice><guisubmenu>File</guisubmenu><guimenuitem>Print
Preview</guimenuitem></menuchoice>.
It will render the current file and present a preview of the print.
Source codes which
- are hilighted in the editor are also highlighted similarly in the
print (or preview). Addtional
+ are highlighted in the editor are also highlighted similarly in the
print (or preview). Additional
options are available to print with the line numbers, wrapped lines
and/or headers in the
- Editor printing preferences from
<menuchoice><guisubmenu>Settings</guisubmenu><guimenuitem>Preferences.
- </guimenuitem></menuchoice>
+ <guilabel>Printing</guilabel> tab of your editor plugin preferences.
<figure>
<title>Print preview of a C file</title>
<screenshot>
Modified: trunk/manuals/anjuta-manual/C/interface.xml
==============================================================================
--- trunk/manuals/anjuta-manual/C/interface.xml (original)
+++ trunk/manuals/anjuta-manual/C/interface.xml Sun Feb 10 15:46:46 2008
@@ -36,7 +36,7 @@
<para>
Shortcut keys are available for many of the menu options. All of the
shortcut
keys are shown alongside the corresponding menu items. A useful
reference to
- the shortcut keys which are not directly attachted with the menu is
also available
+ the shortcut keys which are not directly attached with the menu is also
available
in the next section. Some useful shortcuts are listed here.
</para>
@@ -70,7 +70,7 @@
</listitem>
<listitem>
<para>
- <emphasis>More shortcus:</emphasis> Look for the shortcut keys
displayed on right side
+ <emphasis>More shortcuts:</emphasis> Look for the shortcut keys
displayed on right side
of the menu item labels. They could also be changed as explained in
the tip below.
</para>
</listitem>
@@ -121,13 +121,13 @@
The <interface>Files window</interface> shows a file tree. If no
project is open, the file
tree usually points to the file system root but you can change it in
the preferences. If a project is
open it shows all files inside the project. Double clicking opens a
file in the appropriate application
- as configured in the gnome mime preferences. Richt click opens a
popup-menu which gives you
+ as configured in the gnome mime preferences. Right click opens a
popup-menu which gives you
choices how to open the file.
</para>
</listitem>
<listitem>
<para>
- The <interface>Symbols window</interface> shows shows a tree of
availible symbols in the project
+ The <interface>Symbols window</interface> shows shows a tree of
available symbols in the project
generated from ctags parser. Double clicking opens an editor window
with the corresponding file
and line.
</para>
Modified: trunk/manuals/anjuta-manual/C/introduction.xml
==============================================================================
--- trunk/manuals/anjuta-manual/C/introduction.xml (original)
+++ trunk/manuals/anjuta-manual/C/introduction.xml Sun Feb 10 15:46:46 2008
@@ -14,12 +14,12 @@
<para>
Anjuta DevStudio has been designed to be simple to operate yet powerful
enough
- to fullfil all your programming needs. Many features have evolved since the
+ to fulfill all your programming needs. Many features have evolved since the
early days and several very attractive ones added. Our focus is on delivering
power and usability at the same time without overloading your senses and
making your software development a pleasurable process. We will always be
busy getting you one of the best IDE experiences by straighting up all
- the neat features and stablizing it. We hope you will have a good time
+ the neat features and stabilizing it. We hope you will have a good time
using Anjuta. If not, please help us make it better by reporting bugs and
suggestions. Here are some of the things you will find in Anjuta.
</para>
Modified: trunk/manuals/anjuta-manual/C/preferences.xml
==============================================================================
--- trunk/manuals/anjuta-manual/C/preferences.xml (original)
+++ trunk/manuals/anjuta-manual/C/preferences.xml Sun Feb 10 15:46:46 2008
@@ -14,7 +14,7 @@
<emphasis>Project Directory</emphasis> is the path where you plan to put
all your projects.
Application wizard creates new projects in this directory only. The
default project directory
is ~/Projects and generally, this is just fine for most people. Also,
when Open project is
- activated, this is the base directory where the file selectior will
start.
+ activated, this is the base directory where the file selection will
start.
</para>
</listitem>
<listitem><para>
Modified: trunk/manuals/anjuta-manual/C/projects.xml
==============================================================================
--- trunk/manuals/anjuta-manual/C/projects.xml (original)
+++ trunk/manuals/anjuta-manual/C/projects.xml Sun Feb 10 15:46:46 2008
@@ -12,7 +12,7 @@
<para>
The neat thing is that it does not store any project information beyond what
- is already available in project struture. That is, there is no separate
+ is already available in project structure. That is, there is no separate
project data maintained by Anjuta and all project processing are done
directly within the project structure. This allows the project to be
maintained or developed outside Anjuta without having to so-called
@@ -54,7 +54,7 @@
<para>
On the next pages, enter all necessary
details for your project. You can change these settings later also, but
- it is advicable to put them right in first run to maintain the project's
+ it is advisable to put them right in first run to maintain the project's
integrity.
White spaces or any non-alphanumeric characters, except
underscore (_) and dash (-), are not allowed in many of the entry boxes
@@ -92,7 +92,7 @@
<title>Importing Projects</title>
<para>
The import project feature is used to import an already existing project
and convert it into
- <application>anjuta</application> projcect. Activate the import project
wizard from
+ <application>anjuta</application> project. Activate the import project
wizard from
<menuchoice><guimenu>File</guimenu><guimenu>New</guimenu>
<guimenuitem>Project from existing sources</guimenuitem></menuchoice>
and follow instructions dictated by the wizard. Once the project is
imported, it could be
@@ -130,13 +130,13 @@
<emphasis>Project mode</emphasis>. There are three panes in the
project window. The
first is the project pane and lists the project files organized in file
types. The second
is the symbol browser, which has already been discussed in section
<emphasis>Symbol
- Browser and tags Brwoser</emphasis>. The third pane is the file view of
the project and
+ Browser and tags Browser</emphasis>. The third pane is the file view of
the project and
is more or less similar to a mini file-manager. In file view, all the
files present
in the project tree is visible. Right clicking on these files will pop up
the file
operation submenu.
</para>
<para>
- If the project is also a CVS tree, then corresponing file revision
numbers are also
+ If the project is also a CVS tree, then corresponding file revision
numbers are also
listing on the right of file names in the file view pane.
</para>
</sect2>
@@ -154,16 +154,16 @@
<para>
<interface>Project View</interface> lists the project in standard
<ulink type="info"
url="info:automake"><application>automake</application></ulink>
- heirarchy organized
+ hierarchy organized
into groups of targets. <emphasis>Groups</emphasis> correspond to
directories in your project and <emphasis>targets</emphasis>
correspond to normal <application>automake</application> targets (not to be
confused
with make targets). <interface>Project View</interface> actually
has two parts; one part
- (lower one) shows complete project heirarchy and the other part (upper one)
+ (lower one) shows complete project hierarchy and the other part (upper one)
lists important targets directly. Important targets constitute executable
and library targets -- making them very accessible in from the view.
- This is particularly useful in big projects where the heirarchy
+ This is particularly useful in big projects where the hierarchy
could be deep and hard to navigate from the tree alone. Targets are, in
turn, composed of source files.
</para>
@@ -216,13 +216,13 @@
Many command-line tools are available to maintain and manage a project,
and each tool has its own specific rules and capabilities.
<application>Anjuta</application> tries to automate most of the common
- operations using plugins. However, you might occationally still need
+ operations using plugins. However, you might occasionally still need
to do them manually.
</para>
<para>
It is possible to make use of other tools or hand edit the project
- files simulaneously. It doesn't matter if the project is loaded in
+ files simultaneously. It doesn't matter if the project is loaded in
<application>Anjuta</application> or not. <application>Anjuta</application>
would update itself with any external changes made to project.
</para>
@@ -430,12 +430,12 @@
<guimenuitem>Add Source File</guimenuitem></menuchoice>.
From the dialog, select the target to which the file should be added and
the file itself. You can add multiple files at once. To do that, select
- multiple files from the fileselection dialog using either SHIFT or CONTROL
+ multiple files from the file selection dialog using either SHIFT or CONTROL
key. Then click <guibutton>Add</guibutton> button to finally add the
files in project.
</para>
<para>
- By default, current editor file would be preselected for addtion in the
+ By default, current editor file would be preselected for addition in the
dialog. Other convenient way to add a file is to select it in
<interface>File Manager</interface> and choosing
<guimenuitem>Add to project</guimenuitem> from the
@@ -580,7 +580,7 @@
</para>
<para>
External package dependencies are grouped into
<emphasis>modules</emphasis>,
- so that their combined build flags can be conviniently added to different
+ so that their combined build flags can be conveniently added to different
targets. <emphasis>Modules</emphasis> are just arbitrary names given to
group the packages and can be named anything (only alphanumeric and _ are
allowed in module name). Usually, they follow the name of
@@ -646,7 +646,7 @@
<emphasis>Group Properties</emphasis> set to a group applies to all
the targets under it. So any compiler or linker flags set there would
be automatically be part of all the targets in it (in addition the
- targets individual properties). Folowing flags are available in group
+ targets individual properties). Following flags are available in group
properties.
<itemizedlist>
@@ -657,7 +657,7 @@
You need to provide the full include options of the compiler
here, e.g. -I/usr/include/blah. The include paths will be use
to find the include files in your source files. You can also
- add other sort of compiler flags here, but they are prefered
+ add other sort of compiler flags here, but they are preferred
to be set in their respective compiler flags properties
(see below).
</para>
@@ -708,7 +708,7 @@
<emphasis>Target Properties</emphasis> set to a target applies to that
target. So any compiler or linker flags set there would
be just part of it (in addition the its group properties).
- Folowing flags are available in target properties.
+ Following flags are available in target properties.
<itemizedlist>
<listitem>
_______________________________________________
SVN-commits-list mailing list (read only)
http://mail.gnome.org/mailman/listinfo/svn-commits-list
Want to limit the commits to a few modules? Go to above URL, log in to edit
your options and select the modules ('topics') you want.
Module maintainer? It is possible to set the reply-to to your development
mailing list. Email [EMAIL PROTECTED] if interested.
