GNOME.org
 

[nemiver/mallard-docs: 6/28] Cleaning tab/space and line wrapping

commit f5ec9f9ce5dd1e0d6f58a6d551c20bee1e82b1ea
Author: Baptiste Mille-Mathias <baptiste millemathias gmail com>
Date:   Mon Apr 29 19:30:21 2013 +0200

    Cleaning tab/space and line wrapping

 help/C/contact.page                   |   32 +++++++++-------
 help/C/debug-core-file.page           |   31 ++++++++--------
 help/C/debug-remote-target.page       |   32 +++++++++--------
 help/C/debug-running-program.page     |   26 ++++++++-----
 help/C/interface.page                 |    7 ++--
 help/C/launch-a-program-to-debug.page |   63 +++++++++++++++++---------------
 help/C/report-bug.page                |   30 ++++++++--------
 help/C/what-is-nemiver.page           |   29 ++++++++-------
 8 files changed, 134 insertions(+), 116 deletions(-)
---
diff --git a/help/C/contact.page b/help/C/contact.page
index 989dc48..f84c4c0 100644
--- a/help/C/contact.page
+++ b/help/C/contact.page
@@ -1,19 +1,23 @@
 <page xmlns="http://projectmallard.org/1.0/";
-       type="topic"
-       id="support">
+    type="topic"
+    id="support">
 
-       <info>
-       <link type="guide" xref="index#support"/>
-       </info>
+    <info>
+    <link type="guide" xref="index#support"/>
+    </info>
 
-       <title>Contact</title>
+    <title>Contact</title>
 
-       <p>In any case you have question or need support, you can contact users and developers of 
<app>Nemiver</app> on the following channels:</p>
-       <list>
-               <item><p>email: <app>Nemiver</app> has a <link href="mailto:nemiver-list gnome 
org">mailing-list</link>, where you can ask question.
-               You might want to check the mailing-list <link 
href="http://mail.gnome.org/archives/nemiver-list";>archives</link> before sending a mail.</p></item>
-               <item><p>IRC: Channel <link href="irc://irc.gimp.org/#c++">C++</link> on server
-               <sys>irc.gimpnet.org</sys>. While this channel is not dedicated to <app>Nemiver</app>,
-               the developers are often connected there.</p></item>
-       </list>
+    <p>In any case you have question or need support, you can contact users and
+    developers of <app>Nemiver</app> on the following channels:</p>
+    <list>
+        <item><p>email: <app>Nemiver</app> has a <link
+        href="mailto:nemiver-list gnome org">mailing-list</link>, where you can
+        ask question.  You might want to check the mailing-list <link
+        href="http://mail.gnome.org/archives/nemiver-list";>archives</link>
+        before sending a mail.</p></item>
+        <item><p>IRC: Channel <link href="irc://irc.gimp.org/#c++">C++</link> on server
+        <sys>irc.gimpnet.org</sys>. While this channel is not dedicated to <app>Nemiver</app>,
+        the developers are often connected there.</p></item>
+    </list>
 </page>
diff --git a/help/C/debug-core-file.page b/help/C/debug-core-file.page
index 607203e..1d9ab39 100644
--- a/help/C/debug-core-file.page
+++ b/help/C/debug-core-file.page
@@ -3,24 +3,25 @@
       id="debug-core-file">
 
       <info>
-               <link type="guide" xref="index#overview"/>
+        <link type="guide" xref="index#overview"/>
       </info>
 
     <title>Debug a program using a core file</title>
 
-       <p>To debug a core file, choose <guiseq><gui>File</gui>, <gui>Load Core File…</gui></guiseq>, then a 
new window appears:</p>
-       <list>
-               <item><p><gui>Core File</gui>, choose the core file you want to debug.</p></item>
-               <item><p><gui>Executable</gui>, choose the executable file that generate the 
-               core file. It should be the same exact version.</p></item>
-       </list>
+    <p>To debug a core file, choose <guiseq><gui>File</gui>, <gui>Load Core
+    File…</gui></guiseq>, then a new window appears:</p> <list>
+    <item><p><gui>Core File</gui>, choose the core file you want to
+    debug.</p></item> <item><p><gui>Executable</gui>, choose the executable file
+    that generate the core file. It should be the same exact version.</p></item>
+    </list>
 
-       <section id="what-is-core-file">
-               <title>What is a core file</title>
-               
-               <p>A core file is a file that contains a detail description of a program when
-               it crashed. It's useful to do a post-mortem analysis after a crash in order 
-               to reproduce it and correct the underlaying problem that introduced the 
-               crash.</p>
-       </section>
+    <section id="what-is-core-file">
+        <title>What is a core file</title>
+
+        <p>A core file is a file that contains a detail description of a program
+        when it crashed. It's useful to do a post-mortem analysis after a crash
+        in order to reproduce it and correct the underlaying problem that
+        introduced the 
+        crash.</p>
+    </section>
 </page>
diff --git a/help/C/debug-remote-target.page b/help/C/debug-remote-target.page
index ffb3448..cb4ed36 100644
--- a/help/C/debug-remote-target.page
+++ b/help/C/debug-remote-target.page
@@ -3,25 +3,27 @@
       id="debug-remote-target">
 
       <info>
-       <link type="guide" xref="index#overview"/>
+        <link type="guide" xref="index#overview"/>
       </info>
 
     <title>Debug a remote target</title>
 
-    <p><app>Nemiver</app> can be used program that run either on a remote machine running gdbserver or a 
device plugged to your local machine.</p>
+    <p><app>Nemiver</app> can be used program that run either on a remote
+    machine running gdbserver or a device plugged to your local machine.</p>
 
-       <p>To debug such program, choose <guiseq><gui>File</gui>, <gui>Connect to Remote 
Target…</gui></guiseq>, then a new window appears:</p>
-               <list>
-                       <item><p><gui>Executable to Load</gui></p></item>
-                       <item><p><gui>Shared Libraries Location</gui></p></item>
-                       <item><p><gui>Remote Debugging Server</gui></p>
-                       <list>
-                               <item><p>TCP/IP Connection</p></item>
-                               <item><p>Serial Line Connection</p></item>
-                       </list>
-                       </item>
-               </list>
-       
-       <p>choose <gui>OK</gui> to start the debugging session.</p>
+    <p>To debug such program, choose <guiseq><gui>File</gui>, <gui>Connect to
+    Remote Target…</gui></guiseq>, then a new window appears:</p>
+        <list>
+            <item><p><gui>Executable to Load</gui></p></item>
+            <item><p><gui>Shared Libraries Location</gui></p></item>
+            <item><p><gui>Remote Debugging Server</gui></p>
+            <list>
+                <item><p>TCP/IP Connection</p></item>
+                <item><p>Serial Line Connection</p></item>
+            </list>
+            </item>
+        </list>
+
+    <p>choose <gui>OK</gui> to start the debugging session.</p>
 
 </page>
diff --git a/help/C/debug-running-program.page b/help/C/debug-running-program.page
index 59bdfde..4db4e6a 100644
--- a/help/C/debug-running-program.page
+++ b/help/C/debug-running-program.page
@@ -3,21 +3,27 @@
       id="debug-running-program">
 
       <info>
-               <link type="guide" xref="index#overview"/>
+        <link type="guide" xref="index#overview"/>
       </info>
 
     <title>Debug a running program</title>
 
-       <section id="interface">
-               <title>From <app>Nemiver</app> interface</title>
+    <section id="interface">
+        <title>From <app>Nemiver</app> interface</title>
 
-               <p>To debug a program which is currently running, choose <guiseq><gui>File</gui>, <gui>Attach 
to Running Program…</gui></guiseq>, then select the program you want to debug in the list, and choose 
<gui>OK</gui>. You can narrow the list of programs by entering part of the target program you look for.</p>
-       </section>
+        <p>To debug a program which is currently running, choose
+        <guiseq><gui>File</gui>, <gui>Attach to Running Program…</gui></guiseq>,
+        then select the program you want to debug in the list, and choose
+        <gui>OK</gui>. You can narrow the list of programs by entering part of
+        the target program you look for.</p>
+    </section>
 
-       <section id="command-line">
-               <title>From command-line</title>
-               <p>From a terminal, you can start directly a debugging session, type 
-               <cmd>nemiver --attach</cmd><var>program_name</var> where <var>program_name</var> is the 
program you want to debug. <var>program_name</var> can also be the Process ID of the program.</p>
-       </section>
+    <section id="command-line">
+        <title>From command-line</title>
+        <p>From a terminal, you can start directly a debugging session, type
+        <cmd>nemiver --attach</cmd><var>program_name</var> where
+        <var>program_name</var> is the program you want to debug.
+        <var>program_name</var> can also be the Process ID of the program.</p>
+    </section>
 
 </page>
diff --git a/help/C/interface.page b/help/C/interface.page
index 49aa62a..8553e30 100644
--- a/help/C/interface.page
+++ b/help/C/interface.page
@@ -10,9 +10,10 @@
   <title>Interface</title>
 
   <figure>
-       <title>The Main Interface</title>
-       <desc>The main interface of Nemiver, with the menu on top, below the source code view, and at the 
bottom the toolbox.</desc>
-       <media type="image" mime="image/png" src="figures/main-interface.png"></media>
+    <title>The Main Interface</title>
+    <desc>The main interface of Nemiver, with the menu on top, below the source
+    code view, and at the bottom the toolbox.</desc> <media type="image"
+    mime="image/png" src="figures/main-interface.png"></media>
   </figure>
 
 </page>
diff --git a/help/C/launch-a-program-to-debug.page b/help/C/launch-a-program-to-debug.page
index 7c4e553..29f9ea9 100644
--- a/help/C/launch-a-program-to-debug.page
+++ b/help/C/launch-a-program-to-debug.page
@@ -1,36 +1,39 @@
 <page xmlns="http://projectmallard.org/1.0/";
-       type="topic"
-       id="launch-a-program-to-debug">
-       
-       <info>
-               <link type="guide" xref="index#overview"/>
-       </info>
+    type="topic"
+    id="launch-a-program-to-debug">
+    
+    <info>
+        <link type="guide" xref="index#overview"/>
+    </info>
 
-       <title>Launch a program to debug</title>
+    <title>Launch a program to debug</title>
 
-       <section id="interface">
-               <title>From <app>Nemiver</app> interface</title>
-       
-               <p>Choose <guiseq><gui>File</gui><gui>Load Executable…</gui></guiseq>, a new window
-               opens:</p> 
-               <list>
-                       <item><p><gui>Program</gui> choose the program installed on your machine to 
launch.</p></item>
-                       <item><p><gui>Arguments</gui>, you can enter optional arguments you want to pass to 
the program to debug.</p></item>
-                       <item><p><gui>Working Directory</gui>, the place from where the program will 
start.</p></item>
-                       <item><p><gui>Environment Variables</gui>, optionnal variables that may affect the 
program to debug to.</p></item>
-               </list>
-               <p>Once set, choose <gui>Execute</gui> to start the debugging session.</p>
-       </section>
+    <section id="interface">
+        <title>From <app>Nemiver</app> interface</title>
 
-       <section id="command-line">
-               <title>From command-line</title>
-               <p>It is possible to launch a debugging session from a terminal,
-               <cmd>nemiver</cmd><var>program</var> where <var>program</var> can be
-               the name of the binary of a program or a full path to a program.</p>
+        <p>Choose <guiseq><gui>File</gui><gui>Load Executable…</gui></guiseq>, a new window
+        opens:</p> 
+        <list>
+            <item><p><gui>Program</gui> choose the program installed on your
+            machine to launch.</p></item> <item><p><gui>Arguments</gui>, you can
+            enter optional arguments you want to pass to the program to
+            debug.</p></item> <item><p><gui>Working Directory</gui>, the place
+            from where the program will start.</p></item>
+            <item><p><gui>Environment Variables</gui>, optionnal variables that
+            may affect the program to debug to.</p></item>
+        </list>
+        <p>Once set, choose <gui>Execute</gui> to start the debugging session.</p>
+    </section>
 
-               <p>Should you need to pass arguments to the program to debug,
-               note you have to enclose the program and the arguments between
-               quotes, <cmd>nemiver</cmd>"<var>program --arg1 --arg2</var>".
-               </p>
-       </section>
+    <section id="command-line">
+        <title>From command-line</title>
+        <p>It is possible to launch a debugging session from a terminal,
+        <cmd>nemiver</cmd><var>program</var> where <var>program</var> can be
+        the name of the binary of a program or a full path to a program.</p>
+
+        <p>Should you need to pass arguments to the program to debug,
+        note you have to enclose the program and the arguments between
+        quotes, <cmd>nemiver</cmd>"<var>program --arg1 --arg2</var>".
+        </p>
+    </section>
 </page>
diff --git a/help/C/report-bug.page b/help/C/report-bug.page
index 7834852..43313e7 100644
--- a/help/C/report-bug.page
+++ b/help/C/report-bug.page
@@ -1,20 +1,20 @@
 <page xmlns="http://projectmallard.org/1.0/";
-       type="topic"
-       id="bugs">
+    type="topic"
+    id="bugs">
 
-       <info>
-               <link type="guide" xref="index#support"/>
-       </info>
+    <info>
+        <link type="guide" xref="index#support"/>
+    </info>
 
-       <title>Report a bug</title>
+    <title>Report a bug</title>
 
-       <p>Should you detect a problem, you should report it to in <link
-       href="https://bugzilla.gnome.org/enter_bug.cgi?product=nemiver";>bug tracker
-       application</link>. Alongside the details about to trigger the bug you 
-       encountered, you'll need to provide some information such as:</p>
-       <list>
-               <item><p>the distribution you are running on.</p></item>
-               <item><p>the version of Nemiver.</p></item>
-               <item><p>the version of GDB</p></item>
-       </list>
+    <p>Should you detect a problem, you should report it to in <link
+    href="https://bugzilla.gnome.org/enter_bug.cgi?product=nemiver";>bug tracker
+    application</link>. Alongside the details about to trigger the bug you 
+    encountered, you'll need to provide some information such as:</p>
+    <list>
+        <item><p>the distribution you are running on.</p></item>
+        <item><p>the version of Nemiver.</p></item>
+        <item><p>the version of GDB</p></item>
+    </list>
 </page>
diff --git a/help/C/what-is-nemiver.page b/help/C/what-is-nemiver.page
index 792d5a0..ce521c1 100644
--- a/help/C/what-is-nemiver.page
+++ b/help/C/what-is-nemiver.page
@@ -1,16 +1,17 @@
 <page xmlns="http://projectmallard.org/1.0/";
-       type="topic"
-       id="what-is-nemiver">
-       
-       <info>
-               <link type="guide" xref="index#introduction"/>
-       </info>
-       
-       <title>What is Nemiver</title>
-       <p><app>Nemiver</app> is a graphical debugger built on top of GNOME 
-       technologies, an application that help to analyze bugs and weird behaviors
-       in a program.</p>
-       <p>Nemiver uses underneath <link href="http://www.gnu.org/software/gdb/";>GDB</link>
-       (the GNU debugger), as debugging engine, so as consequence Nemiver can 
-       debug C and C++ programs.</p>
+    type="topic"
+    id="what-is-nemiver">
+
+    <info>
+        <link type="guide" xref="index#introduction"/>
+    </info>
+
+    <title>What is Nemiver</title>
+    <p><app>Nemiver</app> is a graphical debugger built on top of GNOME 
+    technologies, an application that help to analyze bugs and weird behaviors
+    in a program.</p>
+
+    <p>Nemiver uses underneath <link href="http://www.gnu.org/software/gdb/";>
+    GDB</link> (the GNU debugger), as debugging engine, so as consequence 
+    Nemiver can debug C and C++ programs.</p>
 </page>
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]