dhis2-devs team mailing list archive

[noreply@xxxxxxxxxxxxx]

------------------------------------------------------------
revno: 377
committer: Jason P. Pickering <jason.p.pickering@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Tue 2011-08-09 22:20:27 +0200
message:
  Fixed some line break issues with PDF output in the documentation guide.
modified:
  src/docbkx/en/dhis2_documentation_guide.xml


--
lp:~dhis2-documenters/dhis2/dhis2-docbook-docs
https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs

Your team DHIS 2 developers is subscribed to branch lp:~dhis2-documenters/dhis2/dhis2-docbook-docs.
To unsubscribe from this branch go to https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs/+edit-subscription

=== modified file 'src/docbkx/en/dhis2_documentation_guide.xml'
--- src/docbkx/en/dhis2_documentation_guide.xml	2011-07-24 10:30:05 +0000
+++ src/docbkx/en/dhis2_documentation_guide.xml	2011-08-09 20:20:27 +0000
@@ -1,6 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- This document was created with Syntext Serna Free. --><!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"; [
-<!ENTITY br ''>]>
+<!-- This document was created with Syntext Serna Free. --><!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"; []>
 <chapter>
   <chapterinfo>
     <title>DHIS 2 Documentation Guide</title>
@@ -99,14 +98,14 @@
     <title>Using images</title>
     <para>Screen shots are very useful for providing information to users on how particular actions
 should be performed. DocBook has no intrinsic mechanisms to know exactly how an image should be rendered in the final document. Therefore, it is necessary to provide instructions through element attributes. The following XML code fragment demonstrates how an image can be specified to occupy 80% of the available page width. For screen shots in landscape format, this seems to be an appropriate amount. You may need to experiment a bit to obtain a proper width for your image. Alternatively, you can edit the resolution of the image itself, in order to obtain a proper size during rendering. </para>
-    <literallayout>&lt;screenshot&gt;
- &lt;screeninfo&gt;DHIS2 Login screen&lt;/screeninfo&gt; 
-  &lt;mediaobject&gt; 
+    <programlisting>&lt;screenshot&gt;
+ &lt;screeninfo&gt;DHIS2 Login screen&lt;/screeninfo&gt;
+  &lt;mediaobject&gt;
    &lt;imageobject&gt; 
-    &lt;imagedata fileref=&quot;dhis2_login_screen.jpg&quot; format=&quot;JPG&quot; width=&quot;80%&quot;/&gt; 
-   &lt;/imageobject&gt; 
+    &lt;imagedata fileref=&quot;dhis2_login_screen.jpg&quot; format=&quot;JPG&quot; width=&quot;80%&quot;/&gt;
+   &lt;/imageobject&gt;
   &lt;/mediaobject&gt; 
-&lt;/screenshot&gt;</literallayout>
+&lt;/screenshot&gt;</programlisting>
     <para>For other images, depending on their size, a different value may be necessary. If you do
 not specify a width for you image, and its intrinsic size is larger than the available screen width, the image may overflow in certain document types with a fixed width, such as PDF. </para>
   </section>
@@ -117,21 +116,22 @@
     <para>Should you wish to link several articles together into a book, DocBook provides a
 mechanism to assign an id to a section. In the example below, a section has been assigned an id. This id must be unique within the document. </para>
     <para>
-<literallayout>  &lt;section id=&quot;mod2_1&quot;&gt;
-&lt;title&gt;Getting started with DHIS2&lt;/title&gt; ....</literallayout> </para>
+<programlisting>  &lt;section id=&quot;mod2_1&quot;&gt;
+&lt;title&gt;Getting started with DHIS2&lt;/title&gt; ....</programlisting> </para>
     <para>In order to include an article into a book, an Xinclude statement must be used. The
 following example shows how. </para>
     <para>
-<literallayout>&lt;chapter&gt;
+<programlisting>&lt;chapter&gt;
 &lt;title&gt;Getting started with DHIS2&lt;/title&gt; 
-&lt;xi:include xmlns:xi=&quot;http://www.w3.org/2001/XInclude&quot; href=&quot;dhis2_user_man_mod2.xml&quot; xpointer=&quot;mod2_1&quot; encoding=&quot;UTF-8&quot;/&gt;
-... </literallayout>
+&lt;xi:include xmlns:xi=&quot;http://www.w3.org/2001/XInclude&quot; href=&quot;dhis2_user_man_mod2.xml&quot;
+ xpointer=&quot;mod2_1&quot; encoding=&quot;UTF-8&quot;/&gt;
+... </programlisting>
 </para>
     <para>Note that the file name and id have been assigned in the parent document, referring to the
 actual file (href) and particular fragment of the child document that should be referenced in the parent document (xpointer). </para>
     <para>Including chapters in a book is very simple. The example below illustrates how: </para>
-    <para><literallayout>&lt;xi:include xmlns:xi=&quot;http://www.w3.org/2001/XInclude&quot; href=&quot;dhis2_user_man_
-mod1.xml&quot; encoding=&quot;UTF-8&quot;/&gt; </literallayout>
+    <para><programlisting>&lt;xi:include xmlns:xi=&quot;http://www.w3.org/2001/XInclude&quot; href=&quot;dhis2_user_man_
+mod1.xml&quot; encoding=&quot;UTF-8&quot;/&gt; </programlisting>
 </para>
     <para>In this case, there is no need to explicitly reference a part of the document, unless you
 only want to include a portion of the chapter. If you want to use a section of the chapter, you can assign an id to that section, and then reference that section through an xpointer. </para>